Console
Home
Persona-composed operational landing with metrics and quick actions.
Overview
Console Home is the persona-aware operational landing surface. Rather than a static dashboard, Home adapts cards, metrics, and quick actions to how your role interacts with autonomous reliability infrastructure, whether you ship releases, stabilize tests, or oversee organizational posture.
Home aggregates signals from recent runs, open failures, coverage movement, pending approvals, and agent fleet health without replacing deep operational views in Operate or Quality. Think of Home as your shift-start screen; drill into Runs or Test Health for investigation.
Executives and engineering managers often review Home weekly; QA leads and SREs may visit multiple times per day. Configure persona and notification settings so Home highlights what matters before you open the command palette.
Who should read this
- QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.
Prerequisites
- At least one project or run history in your organization (blank states appear for new tenants)
- Persona lens selected or defaulted for your user profile
When to use this workflow
- Beginning a work session to see what changed overnight in reliability posture
- Checking quick actions before a release readiness meeting
- Orienting new team members before guided tours of Operate and Quality
Step-by-step procedure
Review reliability summary metrics
Scan pass rate, failure count, and trend indicators on Home for the time window your persona emphasizes (7-day vs 30-day).
Compare movement to your team SLOs or internal targets, not every metric is a release gate by default.
Click a metric card when available to drill into the underlying Runs or Test Health view.
Act on quick actions
Use quick actions such as Start run, Open reports, or Create project when they match your immediate task.
Prefer quick actions for common paths; use ⌘K for less frequent destinations like Coverage or Topology.
Confirm environment context in the run launcher before starting production-impacting validation.
Triage recent activity
Review recent runs list for failures, cancellations, or unusually long durations.
Open failed runs directly from activity feeds to inspect case outcomes and artifacts.
Note run IDs when escalating to support or attaching evidence to incident tickets.
Follow persona-specific cards
QA personas surface test library shortcuts, review backlog hints, and coverage gaps.
SRE personas emphasize agent status summaries and links toward Agent Console telemetry.
Executive personas highlight report snapshots and release gate posture when enabled.
Adjust Home context via Settings
Open Console Settings to change persona lens, notification cadence, or default time range where offered.
Return to Home after saving preferences to confirm cards reordered as expected.
Coordinate with administrators if Home lacks data you expect, role scope may limit visiblity.
Transition to deep operational views
From Console Home, select Operate → Runs when investigating execution history in bulk.
Use Quality → Test Health when failures cluster or flakiness spikes on Home trend cards.
Schedule recurring reports from Operate when stakeholders need automated email summaries.
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
- Start shifts on Home, then navigate with the command palette for speed
- Align persona lens with your primary function to reduce noise from irrelevant cards
- Treat Home trends as directional, confirm anomalies in run detail before declaring incidents
- Pin internal wiki links to Home for your org onboarding checklist
Common issues
- Home appears empty for a new organization
- Create a project, complete at least one run, or wait for scheduled jobs to populate activity. Blank states are normal during pilot setup.
- Metrics differ between Home and Reports
- Time windows or filters may differ. Align date range and project scope before comparing figures in meetings.
Was this page helpful?