Reference
Glossary
Canonical public terminology for Zof reliability infrastructure.
Overview
Canonical public terminology for Zof reliability infrastructure (44 terms). Use consistently across Console UI, documentation, and customer communications.
Glossary
- Zof Console
- Web control plane for reliability workflows, agents, tests, and governance.
- autonomous reliability infrastructure
- Platform capability for continuous test, analysis, and governed remediation.
- AI testing agent
- Catalog agent that generates or executes specialized tests.
- AI remediation agent
- Catalog agent that proposes fixes under policy and human approval.
- cloud agent
- Test runner in Zof-managed infrastructure.
- endpoint agent
- Test runner on customer-controlled infrastructure.
- control plane
- Console and APIs orchestrating policies, runs, and agents.
- System Graph
- Model of components, dependencies, and change (Topology UI).
- Zof Studio
- Governed development environment (web and desktop).
- project
- Test container organizing scenarios, cases, runs, not the application itself.
- application
- System under test registered under a team.
- requirement
- Tracked requirement record linked to coverage.
- requirements document
- Uploaded spec or SRD file.
- test scenario
- Workflow-level behavior to validate.
- test case
- Executable steps and expected results.
- test suite
- Grouped collection of cases for execution.
- test run
- Single execution instance producing results.
- test result
- Per-case outcome within a run.
- execution environment
- Target deployment such as staging or production.
- telemetry
- Metrics and events from agents and runs.
- artifact
- Log, screenshot, trace, or export from a run.
- reliability report
- Aggregated report across runs and metrics.
- governed remediation
- Remediation with policy, approval, verification, and audit.
- human authorization
- Explicit approver action before apply.
- organization
- Customer tenant with isolated data and users.
- team
- Group owning applications and tests.
- role
- Named permission set for Console operations.
- permission
- Atomic capability such as integrations:manage.
- integration
- Connection to external tool (GitHub, Jira, etc.).
- CI/CD
- Pipeline triggering automated validation runs.
- Playwright
- Browser automation framework used for Console QA, not necessarily customer runners.
- agent orchestration
- Coordinating multiple agents on runs.
- endpoint
- Customer machine hosting an endpoint agent.
- capability
- Advertised skill of an agent.
- label
- Tag for policy-based agent targeting.
- policy
- Rule constraining execution or remediation.
- Demo Mode
- View sample tenant data without affecting production.
- Topology
- Console UI for System Graph.
- Agent Console
- Sub-surface for cloud and endpoint execution fleet.
- Control Center
- AI Agents operational landing tab in Agent Console.
- Test Health
- Flakiness and failure analysis (formerly Signal Quality).
- Release Readiness
- Releases and quality gates before ship.
- Engine run
- Deep execution record with steps and artifacts.
- Persona
- UX lens shaping navigation emphasis (QA, SRE, executive, admin).
How to use this page
Orient
Read the overview to understand scope and Console locations referenced.
Open linked related documents for step-by-step procedures.
Apply
Execute workflows in staging before production gates depend on results.
Capture run IDs, project IDs, and timestamps for audit trails.
Validate
Confirm outcomes match expected behavior documented in related guides.
Escalate discrepancies to your administrator or Zof support with evidence attached.
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.
Support
For operational issues include run ID, project ID, environment name, and UTC timestamps when contacting support. See Troubleshooting for common failure modes and escalation paths.
Was this page helpful?