From {packet,4} to Planet-Scale: Framing for the Next Decade
Every distributed system eventually discovers that the wire format is the contract. S1.4 documented why pipes corrupt and how {packet,4} length-prefixing fixes it — the humble framing protocol that tells the receiver exactly how many bytes belong to each message. The futures thesis is that framing is not a detail; it is the foundation of planet-scale coordination. As the mesh grows from one host to a fleet spread across a tailnet, the messages between actors become the organization’s bloodstream, and the framing protocol determines whether that blood flows clean.
What we built
The {packet,4} framing choice is live evidence in the S1.4 article — a real protocol decision documented with the failure modes it prevents (S1.4: “why pipes corrupt and how length-prefixing fixes it”). The erlang-actor-mesh-prototype skill uses it as the deployment model for 1000-actor fleets. The distribution layer from S1.6 extends this across hosts. What the current stack has not yet done is put a schema on top of the frame — a typed message envelope that survives version drift as the fleet evolves.
The vision
Planet-scale framing means three things. First, versioned envelopes: every message carries a schema version, so a fleet can upgrade actors one at a time without a big-bang redeploy. Second, content-addressed payloads: messages reference canonical artifacts by hash, not by content — so the wire carries pointers, and the vault is the store. Third, encrypted frames end to end over the tailnet: the {packet,4} length tells you where the message is, but the wireguard layer tells you who can read it. Framing, versioning, and encryption compose into a message contract that a thousand actors can evolve without breaking each other.
What’s next
The next increment is to define the versioned envelope for the mesh — a small typed message format that wraps the existing {packet,4} frames, with a migration story from unversioned to versioned traffic. The S1.4 article proved the framing layer works; the envelope is the protocol layer above it.
Grounded in the S1.4 article evidence, vault entity erlang-actor-mesh-prototype, and wiki concepts a2a-protocol, bridge-architecture. Sixth article in the SECTOR07a futures series.
