Core Concepts
Key Concepts
Core terminology and mental models for projects, agents, runs, and governance.
Overview
Canonical terminology for Zof Console, the reliability API, and enterprise workflows. Use these definitions consistently across documentation, runbooks, and customer communications.
Each concept page explains meaning, Console location, workflow usage, and links to operational documentation.
Who should read this
- QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.
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
New to Zof
Start with organization, project, and test run.
Then read governed remediation and release gate for enterprise workflows.
Integration authors
Focus on application, test case, test run, and integration concepts.
Map API resource names to these definitions.
Key concepts
- Autonomous reliability infrastructure
- Continuous validation, analysis, and governed remediation across the software lifecycle under enterprise policy and huma…
- Organization
- Customer tenant boundary with isolated data, users, billing, and policy scope. Runtime sessions scope to your organizati…
- Team
- Group owning applications, tests, and operational responsibility. Teams drive RBAC scoping for day-to-day Console work.…
- Role
- Named permission profile assigning capabilities such as runs:create, integrations:manage, or remediation:approve.…
- Permission
- Atomic capability enforced on API and Console routes, composed into roles for enterprise access control.…
- Project
- Primary container organizing requirements, scenarios, cases, runs, and results for a reliability initiative.…
- Application
- Registered system under test with team ownership, environment URLs, and feature hierarchy.…
- Requirement
- Tracked requirement record linked to coverage and traceability matrices, not just the uploaded document file.…
- Requirements document
- Uploaded PRD, SRD, or acceptance criteria file driving governed test generation.…
- Test scenario
- Workflow-level behavior to validate, linked to test types and requirements.…
- Test case
- Executable validation with structured steps, expected outcomes, priority, and platform metadata.…
- Test suite
- Ordered collection of cases executed together for regression or release validation.…
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?
