PCD Workflow Contracts agent-readable instructions
Workflow Contracts model release trains, CI/CD gates, and approvals as explicit state machines with required evidence.
- Release trains: Track draft, verified, public, and rollback states with attached evidence.
- CI/CD gates: Require command output, manifest hashes, and reviewer decisions before transition.
- Deployment approvals: Make required evidence and explicit approval state part of the workflow.
- Boundary: a Workflow Contract helps govern a modeled process. It does not prove external providers cannot fail.
PCD Workflow Contracts
Make release work explicit.
Workflow Contracts model release trains, CI/CD gates, and approvals as explicit state machines with required evidence.
Workflow Governance
Move critical operations out of Markdown-only runbooks.
Contracts make the state, evidence, and failure behavior visible before work is treated as complete.
Core Use Cases
The public page should explain the workflow, not bury it in implementation detail.
Release trains
Track draft, verified, public, and rollback states with attached evidence.
CI/CD gates
Require command output, manifest hashes, and reviewer decisions before transition.
Deployment approvals
Make required evidence and explicit approval state part of the workflow.
Agent-Safe Operation
The contract gives humans and agents the same visible rulebook for critical operations.
Read state
Inspect current state, required evidence, and allowed next actions.
Run gates
Collect command output, hashes, observations, and review notes.
Propose transition
Report evidence status and remaining assumptions before public handoff.
Make the release path auditable before it becomes public state.
Use Workflow Contracts where stale evidence or unsupported public copy would create operational risk.