Spina Grammatica

Every claim passes through exactly five stops. This is both a validation pipeline and a grammatical structure for how claims are told, checked, and connected.

Spina non negotiabilis est. — The spine is non-negotiable.

Governance as Punctuation

Two mechanisms punctuate the spine without being the spine itself.

Manifest (Manifestum)

Provenance — binds artifacts to time, tools, checksums. Every claim carries its receipt.

Contains: SHA-256 checksums, timestamps, tool versions, data sources, contract reference. The manifest proves the claim was produced by the declared process.

Weld (Sutura)

Continuity across change — the only legitimate way to change policy.

Protocol: Names an anchor, runs pre/post tests, enforces κ-continuity (residual ≤ tol). History is append-only and welded, never rewritten.
Historia numquam rescribitur; sutura tantum additur.

Using the Spine in Practice

For Validation

  1. Freeze — declare contract, sources, normalization before computing
  2. Compute — run kernel on embedded trace vector
  3. Publish — thresholds and their order; no mid-episode edits
  4. Reconcile — debit/credit budget Δκ = R·τ_R − (D_ω + D_C)
  5. Read — derive regime from gates, emit three-valued verdict

For Discourse

  1. Contract — state what rules constrain your claim
  2. Canon — narrate using Drift, Fidelity, Roughness, Return, Integrity
  3. Closures — name your thresholds; if they change, say so
  4. Ledger — show the receipt: what was debited, credited, residual?
  5. Stance — state the derived verdict — never assert, always derive
Omnia per spinam transeunt. — Everything passes through the spine.