Lnal Opcodes Balance Mode

Balance mode

In the Recognition Science framework's instruction set, BalanceMode is a simple two-valued switch attached to the BALANCE opcode. It distinguishes two kinds of reset that the BALANCE primitive can perform. The first value, window, resets a neutral window, a short accounting interval in the framework's ledger, its discrete record of recognition events. The second value, cycle, resets a full recognition cycle, the complete eight-tick sequence that the framework derives from its cost function. The distinction matters because a window reset is local and frequent, while a cycle reset is global and rare.

The declaration itself is a definition, not a theorem. It establishes that the BALANCE opcode accepts exactly two modes and no others. It does not prove that either mode is correct, that a reset must happen, or that the framework's cycle has eight ticks. Those claims live elsewhere in the framework's machine-checked library of formal theorems. BalanceMode only names the two options that the instruction grammar permits, so that a program can say which kind of reset it means.

In the framework's account, the BALANCE opcode is one of eight primitives, alongside LOCK, FOLD, SEED, BRAID, MERGE, LISTEN, and FLIP. Each primitive carries optional argument metadata, and BalanceMode is the metadata for BALANCE. A convenience constructor, balance, builds a complete instruction from a mode in one step: given the mode cycle, it returns an instruction whose opcode is BALANCE and whose argument is that mode. The constructor is a shorthand for writing the full instruction by hand.

What BalanceMode does not claim is just as precise. It does not define what a window or a cycle contains, how long either lasts, or what a reset does to the ledger's numbers. It does not say when a program should choose one mode over the other. Those decisions belong to the semantics of the BALANCE primitive itself, which the declaration does not specify. BalanceMode is a vocabulary choice: it fixes the two names, and leaves the behavior to the opcode that consumes them.

/-- Balance modes distinguish neutral window resets from full cycle resets. -/
inductive BalanceMode
| window
| cycle

/-- Balance modes distinguish neutral window resets from full cycle resets. -/
inductive BalanceMode
| window
| cycle

/-- Balance modes distinguish neutral window resets from full cycle resets. -/
inductive BalanceMode
| window
| cycle

/-- Convenience constructor for balance instructions. -/
@[simp] def balance (mode : BalanceMode) : LInstr :=
  { op := Opcode.BALANCE, arg := OpcodeArg.balance mode }

What this page does not claim

BalanceMode does not prove that either reset mode is correct or necessary. BalanceMode does not define what a window or cycle contains or how long either lasts. BalanceMode does not specify when a program should choose window over cycle.

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/LNAL/Opcodes.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: