Codemoji on the substrate.

Codemoji’s Broadcast system is the worked proof that the discipline is buildable, and it is BCS to the letter. It has four entities, each a branded identity: a BroadcastTemplate (BTP) — reusable content, schedule, and a compaction period; a Broadcast (BCA) — one run of a template, a state machine whose components aggregate as it goes; a BroadcastDelivery (BDV) — one per recipient message; and a RecipientGroup (RGP) — the audience and the failure sink. Their data are plain component bundles, never behaviour. The audience is held by reference: a BTP carries the RGP id, not an embedded recipient list — the law from the last dive, in production. And each entity is owned by a system-process gated on its namespace, so the only things crossing between them are identities and messages about identities. Every primitive it stands on is from the floor this course built: the deliveries are property rows keyed by their branded id (14.1), the run’s state stays coherent by newer-wins, the durable record is a Graft commit, and the sends ride the EchoMQ bus. Nothing here is bespoke infrastructure; it is the substrate, used.

The sharpest payoff is the one the very first modules set up. A broadcast to a large audience produces a great many transient BDV rows, and after the template’s period elapses they must collapse into a single durable Result. In most systems that is a sort-and-aggregate over a timestamp column. Here it is neither: because a BDV’s id is a branded snowflake, and a branded snowflake sorts lexicographically in mint order, the deliveries are already chronological — compaction reads them in mint order with no sort at all, folds them into the Result, and trims the transient rows. The same property that gave free-order stream archival in Chapter 11 and a version-free coherence rule in 14.1 here gives free-order compaction in an app. Step back and the whole course is one idea, applied at every layer: a branded id that sorts by birth becomes the loss-window dial of the accept tier, the LSN cursor of the commit tier, the recovery key across runtimes, the version for cache coherence, the chronological key for compaction, and finally the entity of a component system. The durable floor was always in service of this — a place where state keyed by a time-ordered identity is cheap, replicated, and coherent — so that systems built the BCS way get their hardest properties for free. That is the door this course opened. On the other side, the platform is just identities, components, and systems — standing on Echo Persistence.