A universal binary communication protocol. From a single heartbeat byte to a fully identified, timestamped, valued, tasked, and annotated civilisational record — in as few as one byte. Not hardware. Not a device. A wire format for channels too constrained for JSON.
A complete financial transaction in 40 bits. A heartbeat in 1 byte. A full operational record in a few hundred bits. Compact enough for SMS, satellite burst, sub-GHz radio, or QR code.
1 byte · minimum frameThe first bits of a frame declare what kind of data follows. Receivers parse without prior negotiation, without schemas, without versioned APIs. The frame is the contract.
mode declarations · no handshakeBase records extend with structured annotations via a formal grammar. Enhancements chain, nest, and compose. A sensor reading gains a timestamp gains a location gains a signature — without breaking the base frame.
chainable · nestable · composableEvery frame carries integrity verification. If the bits parse, the record is structurally sound. No application-layer validation needed to confirm transmission integrity.
wire-level verificationThe same structural invariants that apply to financial double-entry — nothing created or destroyed without a balancing counterpart — apply to any domain: spatial, IoT, manufacturing, agricultural.
domain-agnostic · conservation lawForward error correction for degraded radio links. Store-and-forward for intermittent connectivity. Idempotent records for unreliable retransmission. Hash chains for ordering across latency.
FEC · store-and-forward · idempotentThe specification is public. The CLI is open source. Implementations are welcome.
bitpads.org → · Standard → · CLI → · Tools →