Skip to main content

Proof And Evidence Workflow

Purpose​

  • This page explains how Origo contributors should think about proof, observability, and evidence when making or reviewing changes.

Required reading​

  • contracts/governance/observability-as-proof.json
  • docs/observability-as-proof-reference.md
  • docs/observability-reference.md
  • docs/backfill-status-reference.md

Process​

  1. Decide whether the work is runtime-touching.
  2. Declare the supporting proof obligations, terminal proof obligations, freshness expectations, and blocking gaps.
  3. Confirm the relevant observability or proof surfaces are available.
  4. Close the claim only when supporting and terminal proof expectations are satisfied.

Checklist​

  • Runtime-touching status is explicit.
  • Supporting proof is not confused with terminal proof.
  • Proof freshness is stated when it matters.
  • Blocking gaps are visible rather than hand-waved away.

Failure cases and review notes​

  • Do not use slice-closeout prose as a substitute for terminal runtime proof.
  • Do not close a runtime claim if observability surfaces disagree with the proof narrative.
  • docs/Developer/Tests-And-Gates.md
  • docs/Developer/Governance-Reading-Guide.md
  • docs/observability-as-proof-reference.md