BitPads Protocol

Every bit must earn its place

The minimum wire footprint is a hard commitment, not a preference. BitPads encoding is designed to carry the full PADS job record — Processes, Actions, Details, Story — in a payload that travels as a standard SMS message. No field is included by default that is not required for reconstruction. Every release of BitPads must be evaluated against this constraint: does any change increase the minimum payload size? If so, the change requires explicit justification and must be weighed against the cost to the lowest-bandwidth use case.

Structural honesty at the wire level

A malformed BitPads record cannot be encoded. This is a property of the format, not a validator that runs at application layer. The encoding enforces the structural constraints of the PADS model by construction: a record missing required fields does not produce a partial encoding — it does not produce an encoding at all. Every release must preserve this property. Adding fields or extending the schema must never introduce partial-validity states where a record can be encoded but not safely decoded.

The Baudot inheritance

BitPads reclaims three upper bits of the C0 control character space that Baudot established in 1870 and every subsequent standard has left unclaimed. This is not a historical curiosity — it is a structural pocket mathematically guaranteed by the five-bit constraint that has governed every binary communication standard from telegraph code through ASCII to Unicode control characters. The BitPads Enhancement Grammar defines the occupancy of this space and owns it forward. Each release must document any extension to the Enhancement Grammar with full justification for why it belongs in this reserved pocket.

Transport agnosticism

BitPads payloads are designed to travel over any binary channel: SMS, IP, satellite, serial, or any future transport. The protocol makes no assumptions about the channel it traverses. It does not assume packet ordering, reliable delivery, or low latency. It does not assume the sender and receiver share a data connection. It assumes only that bits can be transmitted and that the receiver can decode them. Every release must test against this minimum transport assumption, not against the most convenient modern network.

Open standard, freely implementable

BitPads is an open standard under the same governance model as BASICS — no license fees, no platform dependency, no proprietary encoding. The specification is the standard; the reference implementation demonstrates it. Any developer may implement BitPads encoding and decoding independently, and those implementations are equally valid BitPads implementations if they conform to the specification. Conformance is verifiable, not claimed. Each release ships a conformance test suite that any implementation can run.