Integrity Ledger
Auditus praecedit responsum — hearing precedes response.
The ledger is the fourth stop on the spine: it debits Drift and Roughness, credits Return, and derives the verdict. This page shows the kernel metrics for all 20 closure domains — where each domain stands, how they compare, and where the heterogeneity gap reveals structural insight.
What the Ledger Does
Debit Side
- − D_ω (Drift debit) — how far the system moved from the Contract baseline
- − D_C (Curvature debit) — friction from coupling to uncontrolled degrees of freedom
Credit Side
- + R·τ_R (Return credit) — credible re-entry, typed and timestamped. Zero if τ_R = ∞_rec
Three-Valued Verdict
Numquam binarius; tertia via semper patet. — Never boolean; the third way is always open.
The 20 Closure Domains
Each domain selects which real-world quantities become trace vector channels. The kernel function is the same everywhere — Tier-2 closures choose the input; Tier-1 computes the output. The ledger records both.
Domain Ledger
Domain Overview & Ledger
Overview of all 20 closure domains with kernel metrics, regime classification, and cross-domain comparison.
Quick Domain Kernel
Select a preset domain trace or enter custom values to compute kernel invariants.
All 20 Domains — Kernel Summary
| Domain | F | ω | IC | Δ | S | C | Regime | IC/F |
|---|
Cross-Domain Regime Distribution
The Ledger in the Spine
The Integrity Ledger is the fourth stop on the spine. Everything before it produces data (Contract freezes, Canon narrates, Closures gate). The Ledger reconciles — it is the proof that the sentence is well-formed. The Stance that follows is read from the reconciled ledger, never asserted independently.
Continuitas non narratur: mensuratur. — Continuity is not narrated: it is measured.