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.

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.…

Use the concepts to describe one real workflow

Choose a single application change and explain its requirements, tests, execution conditions, observed results, and review decision. Keep the distinction between intended behavior, generated test logic, and evidence of actual execution clear.

When two teams use the same term differently, resolve the meaning in the context of the workflow. A score summarizes selected evidence; it does not replace the underlying result, its scope, or the judgment required for a release.

Was this page helpful?