Skip to content

Closeout Ceremony

Closeout is a mode where the agent presents evidence paths and commands, and the human observes and decides.

Canonical GovZero source: docs/governance/GovZero/audit-protocol.md.

Sequence

  1. Orientation
  2. Confirm target ADR and OBPI scope.
  3. Confirm lane obligations.
  4. Presentation (gz closeout)
  5. Agent provides Gate 1 path, OBPI completion summary, and verification commands.
  6. Linked OBPI proof is reconciled first. If any OBPI is not closeout-ready, closeout prints BLOCKERS: plus follow-up commands and stops before recording closeout_initiated.
  7. Human Observation
  8. Human runs commands and inspects artifacts directly after closeout is unblocked.
  9. Attestation (gz attest)
  10. Human records completed, partial, or dropped.
  11. gz attest enforces prerequisite gates by default.
  12. Post-attestation Audit (gz audit)
  13. Reconciliation only; blocked before attestation.
  14. Receipts/Accounting (gz adr emit-receipt)
  15. Record ADR-level completed/validated receipts after attestation.
  16. OBPI completion accounting belongs in the OBPI pipeline before ADR closeout, after guarded git sync.

Heavy Lane Gate 4 Handling

For heavy lane ADRs:

  • Closeout includes the Gate 4 BDD command.
  • Closeout remains blocked until linked heavy-lane OBPIs satisfy their attestation-proof rules.
  • Gate 4 must pass before attestation.

Canonical Attestation Choices

  • Completed
  • Completed — Partial: [reason]
  • Dropped — [reason]