Overview

March 2026 delivers governed remediation approvals queue, System Graph Topology beta, and official GitHub Actions integration template with zof run --wait PR gate pattern.

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

Try Topology beta

Platform → Topology → enable beta if available on your plan.

Map services before enabling risk propagation alerts.

Adopt GitHub gate

Copy example from /docs/examples/github-actions-pr-gate.

Store ZOF_API_KEY and ZOF_PROJECT_ID as repository secrets.

Key concepts

Approvals queue: Governance → Remediation → pending plans requiring explicit approver action.
Topology beta: Platform → Topology service graph with dependency risk propagation.
GitHub Actions template: Documented workflow in /docs/examples/github-actions-pr-gate.

Best practices

Enable remediation approvals before autonomous apply in production environments
Review Topology map accuracy after major service decomposition