Skip to content

Lifecycle

ADRs are tracked from ledger events first, with docs as narrative overlay. Operational delivery still happens at OBPI scope, with ADR lifecycle as roll-up state.

Canonical GovZero source: docs/governance/GovZero/adr-lifecycle.md.

Canonical Lifecycle Outcomes

Lifecycle Meaning
Pending Not yet attested
Completed Attested as completed or partial
Abandoned Attested as dropped
Validated ADR-level receipt emitted with receipt_event=validated

gz status and gz adr status derive these values from ledger events. OBPI-scoped receipts that explicitly declare adr_completion: not_completed do not promote ADR lifecycle to Validated. OBPI execution boundaries, scope law, and parallel-safe blocking are defined in the OBPI Transaction Contract. OBPI runtime payload fields and state names are defined in the OBPI Runtime Contract.

Derived Closeout Phase

Runtime also exposes closeout progression:

Closeout phase Trigger
pre_closeout No closeout initiation yet
closeout_initiated closeout_initiated event recorded
attested attested event recorded
validated audit_receipt_emitted with validated

This phase model is additive and does not replace canonical lifecycle terms.

Attestation Mapping

CLI attestation tokens remain stable, but presentations map to canonical terms:

Token Canonical term Lifecycle effect
completed Completed Completed
partial Completed — Partial Completed
dropped Dropped Abandoned

Operational Sequence

  1. Load OBPI transaction context (brief, ADR, handoff context, and plan receipt when present) before implementation begins
  2. Run OBPI increments repeatedly through the transaction contract
  3. After required ceremony/attestation, run guarded repo sync with uv run gz git-sync --apply --lint --test
  4. Record OBPI-scoped receipts using gz obpi emit-receipt Completed receipts are fail-closed when required value narrative/key proof evidence is missing. Heavy-lane parent ADRs (any kind) additionally require explicit human-attestation evidence. Foundation-kind ADRs follow the attestation walkthrough discipline in ADR-0.0.18 regardless of lane.
  5. Reconcile OBPI completeness at ADR boundary (gz obpi reconcile, gz adr audit-check)
  6. Perform ADR closeout and attestation (gz closeout, gz attest) gz closeout remains blocked until linked OBPIs are closeout-ready.
  7. Run post-attestation audit (gz audit)
  8. Emit ADR-level receipt/accounting (gz adr emit-receipt)

If a required compatibility surface is missing, the transaction contract still controls: shared or spine-touch execution must stay single-OBPI, and missing plan-receipt infrastructure must be treated as a governance gap rather than a license to skip context loading.