The Same
Algebra

System context. An Orion-class service module carries a bi-propellant system: Monomethylhydrazine (MMH) fuel and Nitrogen Tetroxide (NTO) oxidiser, two tanks each propellant, feeding 16 attitude control thrusters plus one orbital manoeuvre engine (OME). Each burn event records propellant leaving a specific tank and arriving at a specific thruster manifold. The burn is logged the moment it occurs — not post-processed from a telemetry stream.

Encoding a 450 g attitude control burn. MMH tank 1 fires thruster 7 for 450 ms, consuming 450 g of propellant. The encoding uses Quantity Type 1 (mass, grams), Scaling Factor ×1 (raw grams), Decimal Position 0 (integer gram precision).

Conservation check. A session batch covers one mission phase. At batch close, the conservation invariant requires: sum of all FLOW OUT from all tanks + sum of all FLOW IN to all thrusters = 0 (signed). If the OME consumes 180 kg and 16 attitude thrusters together consume 12 kg over the phase, those 192 kg must appear as FLOW IN to propulsion components. Tank levels at phase end = tank levels at phase start − 192 kg. Any discrepancy is a non-zero Rounding Balance in Layer 2 — the protocol flags it before mission planning software reads a single record.

The reduction is structural. No decompression step. The decoder reads fixed bit positions and the record is decoded. On a deep-space link where bandwidth is measured in bits per second, 500 bytes vs 45,000 bytes is an operational constraint, not a convenience.

System context. An ISS-equivalent ECLSS tracks three primary flows simultaneously: O₂ generation from the Oxygen Generation Assembly (OGA), CO₂ removal via the Carbon Dioxide Removal Assembly (CDRA), and water recovery through the Water Recovery System (WRS). Each process is governed by a different flow archetype. Multiple archetypes operate in the same session batch — this is the default operating mode for real life support systems, not an edge case.

Single 5-byte record: O₂ partial pressure delta in one breathing cycle. The OGA generates enough O₂ to raise cabin partial pressure by 1.4 mbar (14 encoded at D=1, mbar × 10). This records one OGA output cycle — approximately 5 minutes of generation at nominal rate.

Conservation invariant for atmosphere management. Across any closed batch period, the conservation invariant reads: O₂ generated = O₂ consumed by crew + O₂ stored in tank + O₂ lost to any detected leak. This is not a software check written in mission software — it is enforced by the protocol structure before the ECLSS controller processes a single record. A non-zero Rounding Balance at batch close is the signal that the atmosphere budget is not balanced. This detects leaks, sensor faults, and OGA malfunctions at the protocol layer.

CO₂ alert via Wave frame. When the CO₂ partial pressure crosses a threshold (above 5.3 mbar in the CDRA intake), the CDRA controller does not wait to assemble a full 5-byte record. It transmits a 4-byte Wave frame declaring Zone = CDRA, reading = 5.8 mbar, alert type = CO₂-HIGH. The receiver is in elevated alert mode before the full record is assembled. This is the Wave category in action — the full record follows as audit trail, but the alert arrives in a single Wave frame.

System context. A 40-satellite LEO constellation operates a power-sharing agreement. During eclipse periods (36 minutes per 92-minute orbit), eclipse-phase satellites draw power from battery stores. Sunlit satellites accumulate solar generation credit. The constellation settles these power obligations continuously — each orbital pass is one BitLedger session. The session covers all 40 satellites' records under a single CRC-15.

Multi-leg compound transfer. Satellite A (eclipse, node 01) cannot transmit directly to Satellite B (sunlit, node 12). It routes through Relay Satellite C (node 07). This three-leg transfer — A records obligation, relay acknowledges routing, B records receipt — is one logical transaction. The compound continuation marker 1111 links all three records. The 1111 code in the archetype field means "this record continues the preceding compound group." Together they are one event.

System context. An automotive stamping plant processes steel coil stock through five stations: Uncoil, Blank, Draw, Trim, and Pierce. Each station receives material from the prior station, transforms it, and passes the output forward. Scrap is generated at Blank (skeleton offcuts), Trim (edge waste), and Pierce (slug waste). Every station-to-station transfer is one BitLedger record. Every scrap event is the Rounding Balance field — the protocol has an explicit field for the net conservation error, which is exactly what scrap is.

Station 2 (Blank): coil input to blank output. Station 2 receives 850 kg of steel coil from the uncoiler, blanks it into door panel blanks. Output = 781 kg of blanks. Scrap = 69 kg of skeleton offcuts. The conservation check: 850 kg in − 781 kg out − 69 kg scrap = 0. The 69 kg scrap appears in the Rounding Balance field of the Layer 2 batch header for this station's batch. The MES receives a record that has already verified its own conservation before it arrived.

If the scrap weight reported by the Blank station's scale disagrees with the difference between input and output records, the conservation check fails before the batch reaches the MES. The discrepancy is flagged at the wire level — no separate reconciliation run is required. At 10,000 parts per shift, the complete material tracking log is 50,000 bytes of BitLedger records (10,000 parts × 5 records/part chain × 1 byte overhead average). The JSON equivalent of the same event data is approximately 40MB.

System context. A 200-sensor smart building tracks energy consumption, water flow, and HVAC delivery across 40 zones. Each sensor operates on a three-tier transmission schedule: 1-byte Pure Signal heartbeat every 60 seconds for liveness; 4-byte Wave frame for threshold alerts; full 5-byte BitLedger record once per hour for formal accounting. The protocol tier is selected by the sensor's state — normal operation needs only the heartbeat; anomalies escalate to Wave or Record automatically.

Heartbeat protocol. Each sensor transmits 0x40 every 60 seconds. This is Meta byte 1 alone: Wave mode, ACK request, complete, basic treatment, no flags. One byte declares "I am here, acknowledge me." At 200 sensors, heartbeat traffic is 200 bytes per minute — 12,000 bytes per hour — across the entire building liveness network. The building controller knows within 60 seconds if any sensor has dropped.

Enhancement Grammar context declaration. Before transmitting 50 zone-B energy records, the HVAC controller transmits one Category 1101 Context Declaration Enhancement byte. This declares the context — Zone-B, Energy, HVAC — once. The 50 subsequent records inherit that context without re-stating it in each record. This is the Enhancement Grammar's context accumulation mechanism: declare once, apply to the entire subsequent block. The 50 records cost 250 bytes instead of the 350 bytes they would cost if each record included a full zone declaration.

Anomaly records with T1S timestamp. When an energy sensor records an anomaly — consumption spike, sudden drop — it transmits a full BitLedger record with a T1S time component (Unix epoch seconds, 4 bytes). The T1S block attaches to the record via the component sequence in BitPads v2: Meta byte 2 declares the Time component present, and the 4-byte T1S block follows immediately after the Layer 3 record. Total anomaly record: 13 bytes (Meta 1 + Meta 2 + Layer 1 session header omitted on continuation + Layer 3 + T1S). The exact timestamp is preserved for maintenance correlation without any separate logging system.

The fundamental problem. Earth-to-Mars communication latency is 7 to 30 minutes one-way depending on orbital position. Every supply chain decision — O₂ generation rate, food ration allocation, water recovery priority, spare part scheduling — must be made locally. There is no Earth-side database query with a 20-minute turnaround. The conservation enforcement must live in the colony. The protocol must work without a network connection to its originating authority.

BitLedger is the on-colony ledger. The same 40-bit records that enforce conservation on a terrestrial factory floor enforce conservation in Habitat Module 4. The invariant does not require a server. It is structural — a record that violates conservation is rejected at encoding time, before it reaches the habitat management system, whether or not Mars is in conjunction with Earth.

Identity encoding for 8 habitat modules. The 32-bit Sender ID encodes the full addressing hierarchy in a single field. Bits 31–24: habitat module (0–7, 3 bits used). Bits 23–18: supply category (O₂=0, H₂O=1, Food=2, Power=3, Parts=4, Medical=5). Bits 17–0: individual item ID within category (up to 262,143 distinct items per category per module). All 8 modules × 6 categories × 262,143 items = 12.6 million addressable supply items within the 32-bit sender space.

Hybrid domain: physical and financial in one session. When domain bits 3–4 = 10 (Hybrid), the session contains both physical flow records and financial obligation records. A resupply shipment from Earth has physical mass (tracked with archetype 0101, quantity type 1, grams) and financial cost (tracked with Debtor-to-Creditor archetype, currency code USD, per-kg launch cost). One session covers both the physical inventory update and the mission cost accounting. The decoder distinguishes record type by the archetype code — physical archetypes and financial account pair codes occupy non-overlapping ranges in the hybrid interpretation.

All 16 flow archetypes are active in a Mars colony deployment. Internal module transfers use Source-to-Sink. Crew ration allocations use Parent-to-Child. Borrowed supplies between modules use Debtor-to-Creditor. Atmosphere recycling uses Transformation. Earth shipments use Generation/Input. Emergency reserves use Reservation/Escrow. Resupply debt from prior shipments uses Repayment/Return. This is not a contrived mapping — it is the natural vocabulary of any complex supply chain, and the 16 archetypes were derived from exactly this class of system.