Encyclopedia Holography Holography Ledger State Horizon Context

ARTICLE 5 claims 5 theorems

Holography Ledger State Horizon Context

A ledger's own record of debits and credits defines the boundary that physics describes, making a legal transaction and its observable trace two views of one event.

The ledger horizon

In Recognition Science, a ledger is a discrete record of events. The LedgerStateHorizonContext construction builds a bridge from that record to a horizon, the boundary that separates the inside of a system from its outside. The central construction is simple: from any ledger state, the framework derives a horizon context whose single defining number is the total count of committed units, the sum of the absolute values of all debits and credits. That count is not a free parameter; it is computed from the ledger itself.

The framework then proves that a legal atomic tick, the smallest allowed change to the ledger, is exactly a move that extends this horizon by one unit. The theorem T1 states that after such a tick, the horizon record of the new state equals the extended horizon record of the old state. The same event, seen from the ledger side, is a posting step that changes a debit or credit; seen from the boundary side, it is a unit increase in the horizon. The theorem same_event_projections packages this: a legal tick is a posting step, its induced boundary heat is 1, and the horizon record extends by one.

The framework also proves what a legal tick is not. It cannot be reversed: a reverse transition is never a legal atomic tick. It cannot be a zero transfer: a legal tick always changes the ledger state. And the boundary heat it induces is genuinely nonzero, distinct from the heat of a zero extension. These are not assumptions; they are theorems proved from the definition of a legal tick.

There is a named limit to what this construction establishes. The exterior reading derived from a ledger state is all ones: every boundary bit reads 1. The theorem allOnes_cut_does_not_separate_debit_credit shows that this reading cannot distinguish a debit posting from a credit posting that share the same pre-state. The ledger's totals alone do not carry enough information to separate the two sides. This is an open residual, flagged as a trigger for future escalation, not a failure of the construction.

What this construction establishes in plain language is that the boundary of a system is not an additional ingredient. It is a projection of the ledger's own committed units. A legal change to the ledger is a legal change to the boundary, and the two descriptions are the same event seen from two sides. This is the first step toward a holographic principle inside the framework: the volume of activity and the boundary record are tied together by definition, not by a separate postulate.

THEOREM contextOfLedgerState · ledgerCommittedUnits · IndisputableMonolith/Holography/LedgerStateHorizonContext.lean
/--
Horizon context of a ledger state: exterior aperture count equals committed
ledger content; seam/interior/rest are zero constants; rate is the fixed unit.
-/
noncomputable def contextOfLedgerState {d : Nat} (L : LedgerState d) :
    LocalHorizonContext (ledgerCommittedUnits L) 0 0 0 ledgerDerivedKappa :=
  mkLedgerContext (ledgerCommittedUnits L)
/-- Total committed ledger content in absolute debit+credit units. -/
noncomputable def ledgerCommittedUnits {d : Nat} (L : LedgerState d) : Nat :=
  (∑ i : Fin d, Int.natAbs (L.debit i)) +
    (∑ i : Fin d, Int.natAbs (L.credit i))
THEOREM T1 · IndisputableMonolith/Holography/LedgerStateHorizonContext.lean
/--
Make-or-break theorem T1: a legal atomic tick increments the horizon record by
exactly one. Because contexts are subsingleton up to record
(`context_eq_of_record_eq`), this is the content of
`contextOfLedgerState (postState) = extendContext (contextOfLedgerState (preState))`
once the aperture index is identified by `ledgerCommittedUnits_legalAtomicTick_succ`.
-/
theorem T1 {d : Nat} {L L' : LedgerState d}
    (hn : NonnegLedger (d := d) L)
    (h : LegalAtomicTick (d := d) L L') :
    (contextOfLedgerState L').horizonRecord =
      (extendContext (contextOfLedgerState L)).horizonRecord := by
  change ledgerCommittedUnits L' = ledgerCommittedUnits L + 1
  exact ledgerCommittedUnits_legalAtomicTick_succ hn h
THEOREM same_event_projections · IndisputableMonolith/Holography/LedgerStateHorizonContext.lean
/--
Same-event packaging: posting step, unit heat, and context-record extension are
projections of one legal tick. Cut equality does **not** recover the changed
account (see `allOnes_cut_does_not_separate_debit_credit`).
-/
theorem same_event_projections {d : Nat} {L L' : LedgerState d}
    (hn : NonnegLedger (d := d) L)
    (h : LegalAtomicTick (d := d) L L') :
    PostingStep (d := d) L L' ∧
      movingStepHeat (cutOfLedgerState L) (cutOfLedgerState L') = 1 ∧
      (contextOfLedgerState L').horizonRecord =
        (extendContext (contextOfLedgerState L)).horizonRecord :=
  ⟨legalAtomicTick_implies_PostingStep h,
    induced_movingStepHeat_eq_one hn h,
    T1 hn h⟩
THEOREM reverse_not_legalAtomicTick · IndisputableMonolith/Holography/LedgerStateHorizonContext.lean
/-- Reverse of a legal atomic tick is not a legal atomic tick (monotonicity). -/
theorem reverse_not_legalAtomicTick {d : Nat} {L L' : LedgerState d}
    (h : LegalAtomicTick (d := d) L L') :
    ¬ LegalAtomicTick (d := d) L' L := by
  intro hrev
  obtain ⟨k, side, rfl⟩ := legalAtomicTick_implies_PostingStep (d := d) h
  rcases hrev with ⟨⟨hmonoD, hmonoC⟩, _⟩
  cases side with
  | debit =>
    have hle : L.debit k + 1 ≤ L.debit k := by simpa [post] using hmonoD k
    omega
  | credit =>
    have hle : L.credit k + 1 ≤ L.credit k := by simpa [post] using hmonoC k
    omega
THEOREM allOnes_cut_does_not_separate_debit_credit · IndisputableMonolith/Holography/LedgerStateHorizonContext.lean
allOnes_cut_does_not_separate_debit_credit · IndisputableMonolith/Holography/LedgerStateHorizonContext.lean:396
/--
Obstruction witness: debit and credit posts from the zero ledger are distinct
legal ticks of equal committed size. Their all-ones cuts are HEq (same aperture
count). Totals alone do not yield a separating exterior-channel enumeration
(C7/C6 escalation trigger).
-/
theorem allOnes_cut_does_not_separate_debit_credit
    (d : Nat) [NeZero d] :
    let L0 : LedgerState d := { debit := fun _ => 0, credit := fun _ => 0 }
    let k : Fin d := ⟨0, Nat.pos_of_ne_zero (NeZero.ne d)⟩
    let Ldebit := post L0 k Side.debit
    let Lcredit := post L0 k Side.credit
    Ldebit ≠ Lcredit ∧
      ledgerCommittedUnits Ldebit = ledgerCommittedUnits Lcredit ∧
      NonnegLedger (d := d) L0 ∧
      LegalAtomicTick (d := d) L0 Ldebit ∧
      LegalAtomicTick (d := d) L0 Lcredit ∧
      HEq (cutOfLedgerState Ldebit) (cutOfLedgerState Lcredit) := by
  intro L0 k Ldebit Lcredit
  have hn : NonnegLedger (d := d) L0 := ⟨fun _ => le_rfl, fun _ => le_rfl⟩
  have hunits :
      ledgerCommittedUnits Ldebit = ledgerCommittedUnits Lcredit := by
    simp [Ldebit, Lcredit, ledgerCommittedUnits_post hn]
  refine ⟨?_, hunits, hn, legalAtomicTick_of_post L0 k Side.debit,
    legalAtomicTick_of_post L0 k Side.credit, ?_⟩
  · intro heq
    have : Ldebit.debit k = Lcredit.debit k := congrArg (fun M => M.debit k) heq
    simp [Ldebit, Lcredit, post] at this
  · change HEq (mkLedgerCut (ledgerCommittedUnits Ldebit))
        (mkLedgerCut (ledgerCommittedUnits Lcredit))
    rw [hunits]

What this page does not claim

This construction does not claim that the all-ones exterior reading is the only possible boundary reading. This construction does not claim that the ledger-derived horizon context is the full holographic principle of the framework. This construction does not claim that the boundary heat is a physical temperature in the conventional sense.

Verify this page

Every tagged claim above names its theorem. To check one yourself rather than trust this page, elaborate the source module with Lean 4 and audit its axiom basis:

$ lake env lean IndisputableMonolith/Holography/LedgerStateHorizonContext.lean
expected axiom basis: [propext, Classical.choice, Quot.sound] (the Lean kernel's standard three; no RS-specific axioms)

A page whose claims cannot be reproduced this way does not ship. In production, every anchor links to the exact declaration in the public source release, and this block carries the build receipt for the page itself.

Derived articles

This page is generated by a question-recursion engine: the questions its answers raise become the next pages. The current agenda, with open targets marked red:

MACHINE LAYER · GROUNDED CLAIM TABLE · CLICK TO EXPAND