Observability-as-Proof Reference

Purpose

• Observability is not optional supporting material for runtime-touching work.
• Runtime and operational claims must terminate on real operator-visible Slice 40 surfaces plus the underlying authoritative truth surfaces.
• Assertion-only evidence can support a claim, but it cannot close a runtime claim by itself.

Canonical Source

• The canonical declaration surface is the authoritative GitHub slice issue.
• The required issue section is Proof Coverage.
• Proof Coverage must agree with Runtime and Observability Scope.

What Runtime-Touching Means

• Runtime touched in this slice is the canonical discriminator.
• yes means proof coverage is mandatory before implementation starts.
• no means the Proof Coverage section must stay explicitly none for claim classes, obligations, freshness requirements, and blocking gaps.

Proof Types

• Supporting proof:
  • acceptance tests
  • replay tests on fixed fixtures
  • deterministic repeated-run checks
  • contract/replay/integrity CI
• Terminal proof:
  • Slice 40 operator-visible dashboards
  • the underlying authoritative truth surfaces those dashboards render
• Final adequacy review:
  • zero-bang

Claim Closure Rule

• Runtime claims are not complete until both are true:
  • required Slice 40 dashboard families show the claimed truth
  • the underlying authoritative truth surfaces agree
• Split-brain is failure, not partial success.
• Historical/query/export runtime claims now require:
  • Canonical Whole System Truth for authoritative partition completion
  • Canonical Pipeline Residue when the claim depends on provisional residue
  • Origo Store Truth / Event Sourcing for store-level truth

Gap Visibility

• Proof gaps must remain visible on the authoritative program-tracking GitHub surface until closed.
• spec/slices.json is not the proof-gap inventory.