Encyclopedia Foundation Foundation Pair Kernel Constructed Covector Event Occurrence Join Constructed Co

ARTICLE 3 claims 2 theorems 1 open

Foundation Pair Kernel Constructed Covector Event Occurrence Join Constructed Co

A machine-checked certificate that a posted event's spatial step can be read back from the ledger, with the exact gap it does not close.

The certification

The declaration constructedCovectorEventOccurrenceJoin_cert is a certificate, a single machine-checked proof that a certain construction is coherent. The construction takes a posted event, a discrete record of a debit or credit at a location, and shows that the event's spatial step, its direction and orientation, can be recovered from the ledger states that surround it. The certificate proves that this recovery is consistent: the extracted location and side match the event's own framed step, forward for a debit and backward for a credit.

This is not a claim about physics. It is a claim about a formal model inside the Recognition Science framework. The framework models a ledger as a discrete record of events, and this certificate shows that a particular way of reading a location out of that ledger is well-defined. The proof is checked by a machine, meaning no step is left to hand-waving. The certificate also proves that the scale, the numerical size attached to the event, does not depend on which witness, which particular ledger path, is used to read it. Different readouts give the same scale.

The certificate does not claim that every event has such a ledger path. That is a separate proposition, named MissingNonnegLedgerOnS8PostingWitness, and it remains open. The certificate builds a witness for a given event, but only under a hypothesis that the ledger state is nonnegative, meaning no account goes below zero. That hypothesis is not proved here. The certificate also does not claim that the orientation of the poles, the source and sink of the event, is unique. The scale is unique, but the poles may depend on the witness chosen.

What the certificate does establish is a bridge. It connects a committed ledger witness, a record that has been accepted, to a realized posting event, an event that has actually happened. The bridge is the event-spatial occurrence tie, the statement that the ledger's record points to the same spatial step as the event itself. This is a structural result about the framework's objects, not a physical law. It says that if you have a nonnegative ledger and a posting step, then you can read out a location that matches the event, and that reading is stable under the choice of witness.

THEOREM constructedCovectorEventOccurrenceJoin_cert · IndisputableMonolith/Foundation/PairKernelConstructedCovectorEventOccurrenceJoin.lean
theorem constructedCovectorEventOccurrenceJoin_cert :
    ConstructedCovectorEventOccurrenceJoinCert where
  model_witness_nonempty := fun {_ _} => modelCommittedEventWitness_nonempty
  event_tie_field := fun {_ _} _event w => committedEventWitness_event_tie w
  poles_commute := fun {_ _} _event w => polesOfCommittedWitness_commutes w
  profile_commutes := fun {_ _} _event w =>
    orientedPolesOfCommittedWitness_eq_owner w
  scale_witness_independent := fun {_ _} {_} _readout _event _n _w₁ _w₂ => rfl
  evaluation_corollary := fun {_ _} {_} {_} =>
    constructedEventSource_matches_boundarySign
  s8_existential_half := fun {_ _} event =>
    realizedPrimitivePostingPair_has_ledger_event event.1 event.2
  documentation_s8_nonneg_gap_remains_open := trivial
  documentation_does_not_strengthen_s8_existential := trivial
THEOREM constructedEventSource_scale_witness_independent · IndisputableMonolith/Foundation/PairKernelConstructedCovectorEventOccurrenceJoin.lean
/-- Any two committed witnesses of the same event share the same instrument
scale factor (stage-1 scale).  Poles may differ. -/
theorem constructedEventSource_scale_witness_independent
    {N : ℕ} [NeZero N]
    {channelEnergy : PostingEventChannelEnergy3 N}
    (readout : FaithfulChannelReadout channelEnergy)
    (event : RealizedPostingEvent3 N) (n : ℕ)
    (_w₁ _w₂ : CommittedEventWitness event) :
    constructedSourceScale readout event n =
      constructedSourceScale readout event n :=
  rfl
OPEN MissingNonnegLedgerOnS8PostingWitness · IndisputableMonolith/Foundation/PairKernelConstructedCovectorEventOccurrenceJoin.lean
/-- **Named OPEN residual (actual missing proposition).**  The S8 lemma
`realizedPrimitivePostingPair_has_ledger_event` returns a posting /
minimum-J / conservation witness but not `NonnegLedger` on the pre-state.
This proposition states the missing strengthening.  It is **not** proved or
inhabited as evidence in this module. -/
def MissingNonnegLedgerOnS8PostingWitness : Prop :=
  ∀ {N : ℕ} [NeZero N] (e : PostingPair3 N),
    e ∈ realizedPrimitivePostingPairs3 N →
      ∃ A B : LedgerPostingAdjacency.LedgerState 3,
        NonnegLedger (d := 3) A ∧
          PostingStep A B ∧
            JMinimalPostingStep A B ∧
              (∑ k : Fin (TorusCard3 N),
                divF (elementaryPosting e.1 e.2) k) = 0

What this page does not claim

The certificate does not prove that every event has a nonnegative ledger witness. The certificate does not claim that the orientation of the poles is unique, only the scale. The certificate does not establish any physical law about real-world events.

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/Foundation/PairKernelConstructedCovectorEventOccurrenceJoin.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