Foundation Pair Kernel Production Operation Channel Selection S25 Consumer S25 O

The independence lemma

In the Recognition Science framework, a ledger is a discrete record of events, and a recognition is the act of registering one. The declaration s25_operationSelection_independence_compiles is a definition in the framework's machine-checked library of formal theorems. It states, in effect, that the bookkeeping operations which commit a transaction can be compiled separately from the selection of which physical channel carries the result. The lemma is named committedOperations_admit_channelSelection_split: committed operations admit a split from channel selection.

The content of the lemma is a formal statement about a class of posting events. For any realized event and any field assignment, the source operations compile with two properties. First, reversing a spatial edge action and applying it again gives back the original exact cost, and the flux changes sign. Second, the balance current probe is preserved. These are algebraic identities about orientation and batch laws, not physical claims. They say that the bookkeeping layer is internally consistent: reversing an operation undoes its cost and flips its flux, while the conserved current remains intact.

The lemma's role is to separate concerns. The framework proves that a physical readout stack compiles if and only if an operation-to-channel selector is supplied for a candidate system. This selector is still open: the framework does not derive which channel is chosen. The independence lemma establishes that the bookkeeping operations do not depend on that choice. You can compile the source operations first, and attach the channel selection later. The proof shows the two tasks do not entangle.

What the declaration does not claim is just as important. It does not prove that any particular channel selector exists. It does not derive the physical channel carrier dimension, which appears in a separate theorem as 5. It does not say that the operation boundary is closed; in fact, a docstring notes the boundary remains active rather than silently selecting a complete carrier. The lemma is a structural separation result, not a physical prediction. It tells you that the bookkeeping layer is modular, and it leaves the selection problem open for a candidate system.

/-- The operation boundary remains active rather than silently selecting the
complete MODEL carrier. -/
def s25_operationSelection_independence_compiles :=
  committedOperations_admit_channelSelection_split

/-- Source-operation consumer: every S8 event carries active action, one Tick
commit, and a conserved current; orientation and batch exact action compile. -/
theorem productionOperations_source_consumer
    (event : RealizedPostingEvent3 3)
    (field : Fin (TorusCard3 3) → ℝ) :
    CommittedProductionOperations3 ∧
      spatialEdgeActionExactCost3
          (reverseSpatialEdgeActionOperation3
            (spatialEdgeActionOperation3 event))
          field =
        spatialEdgeActionExactCost3
          (spatialEdgeActionOperation3 event)
          field ∧
      spatialEdgeActionFlux3
          (reverseSpatialEdgeActionOperation3
            (spatialEdgeActionOperation3 event))
          field =
        -spatialEdgeActionFlux3
          (spatialEdgeActionOperation3 event)
          field ∧
      BalanceCurrentProbe3
        (balanceCurrentOperationCurrent3
          (balanceCurrentOperation3 event)) :=
  ⟨committedProductionOperations_hold,
    spatialEdgeActionExactCost_reverse _ _,
    spatialEdgeActionFlux_reverse _ _,
    balanceCurrentOperation_passes_probe _⟩

/-- The physical readout stack compiles if and only if the still-open
operation-to-channel selector is supplied for a candidate system. -/
theorem operationSelectedProduction_scaleCovariant_consumer_exists
    (system : PostingPhysicalResponseSystem3.{0} 3)
    (hselect :
      ProductionOperationsSelectPhysicalChannels3 system) :
    ∃ event : RealizedPostingEvent3 3,
      normalizedPostingDuration3
          (observableProductionScaleCovariantPostingReadoutSemantics3
            system
            ((productionOperationSelectors_iff_observableExhaustion
              system).1 hselect))
          event.1 = 1 ∧
        normalizedPostingEnergy3
          (observableProductionScaleCovariantPostingReadoutSemantics3
            system
            ((productionOperationSelectors_iff_observableExhaustion
              system).1 hselect))
          event.1 =
            canonicalPostingEventChannelPrice3 event ∧
        normalizedPostingAction3
          (observableProductionScaleCovariantPostingReadoutSemantics3
            system
            ((productionOperationSelectors_iff_observableExhaustion
              system).1 hselect))
          event.1 =
            canonicalPostingEventChannelPrice3 event ∧
        physicalPostingCarrierDimension3
          (observableProductionPhysicalChannelCarrier3
            system
            ((productionOperationSelectors_iff_observableExhaustion
              system).1 hselect))
          event = 5 ∧
        PostingCarrierResponseObservability3
          (observableProductionResponseSystem3
            system
            ((productionOperationSelectors_iff_observableExhaustion
              system).1 hselect)) := by
  exact transportedProduction_scaleCovariant_consumer_exists
    system
    ((productionOperationSelectors_iff_eventActTransport
      system).1 hselect)

What this page does not claim

The lemma does not prove that any particular physical channel selector exists. The lemma does not derive the physical carrier dimension, which appears in a separate theorem. The lemma does not close the operation boundary; the boundary remains active.

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/PairKernelProductionOperationChannelSelectionS25Consumer.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: