Console

Console (index)

Console documentation hub.

Overview

The Zof Console is the web-based control plane for autonomous reliability infrastructure. Engineering organizations use it to connect applications, ingest requirements, govern test generation, orchestrate AI testing agents, execute validation at scale, analyze failures, and communicate reliability posture to stakeholders.

Console documentation in this section covers navigation, operational landing experiences, project and application management, specifications, the test library, runs, and reports. Each topic maps to a primary Console area, Home, Operate, Quality, Automation, Governance, or Platform, so teams can adopt workflows aligned to their role.

Use this index as your map. Start with Console overview and navigation if you are new to the product; jump directly to projects, runs, or reports when you are executing an established runbook.

Who should read this

  • Platform operators, QA leads, SREs, release managers, and administrators responsible for day-to-day reliability operations in the Console.

Prerequisites

  • An active Zof organization with Console access for your user account
  • At least one assigned role that includes the Console areas you plan to use
  • Familiarity with Zof key concepts: projects, applications, runs, and test health

When to use this workflow

  • Onboarding new team members to Zof terminology and workflows
  • Authoring internal runbooks aligned with Console labels
  • Designing CI/CD or webhook integrations against documented behavior

Step-by-step procedure

Confirm access

Verify organization membership and role permissions in Admin Center.

Confirm API key or SSO session is scoped to the correct tenant.

Apply this guidance

Follow Console navigation paths and API examples in this document.

Use staging project and environment IDs for first-time integration tests.

Verify outcomes

Check Operate → Runs, Quality areas, or API responses for expected results.

Update team runbooks when your stack requires environment-specific variations.

Key concepts

Organization scope
All Zof Console and API operations are isolated to your authenticated tenant.
Governed execution
Agent output and remediation follow policy packs with human approval when configured.

Best practices

  • Validate changes in staging before applying release gates to production.
  • Include run IDs and timestamps when escalating issues to support or auditors.
  • Align internal runbook terminology with Zof Console UI labels for clarity.

Was this page helpful?

01The operational surface

One surface for posture, operations, and what needs attention next.

The Zof home is not a marketing dashboard. It is the operational surface engineering, QA, and SRE teams use every day, quality posture, in-flight runs, coverage by module, and the actions a leader should look at next.

OPERATIONAL KPIs

  • Runs
  • Coverage
  • Risk

Live across every environment you ship to.

WORK SPINE

  • Specs
  • Tests
  • Schedules

From specification to scheduled regression.

GUARDRAILS

  • RBAC
  • SSO
  • audit

Every action attributable to a named human.

STAGING · LIVE/home
Zof AI home command center showing 12 runs at 94% pass, 3 open critical issues, 84% coverage, four module traceability bars, the specification pipeline, upcoming schedules, and recommended next actions with an active-runs sidebar.
Home view · Checkout Service · Staging · captured live from the product.
  • 01 · RUNS · 24H

    94% pass

    12 runs across staging

  • 02 · COVERAGE

    84%

    Across four modules

  • 03 · ACTIVE RUNS

    3 running

    Live on this branch

  • 04 · NEXT ACTIONS

    Recommended

    Triage gaps, new spec

Console (index) | Zof AI Documentation