The polyglot fleet.

A branded id is a 3-character uppercase namespace plus 11 Base62 characters carrying a 63-bit snowflake ts(41) | node(10) | seq(12). It has four properties: typed — the namespace declares the domain class on the wire and in the type system; ordered — the name sorts as its mint instant sorts, so a table keyed by it is a timeline; placed — one function, hash32, locates a row from the identity alone; and conformant — one source of truth and one vector file make encode and decode identical across five runtimes: Elixir, Node, Go, PostgreSQL, and WASM. Which language runs a worker is a deployment detail.

Conformance is the property a fleet needs. If a Go worker and the Elixir bus disagree by one bit on how an id encodes, the Go worker cannot read a JOB key the bus wrote — the fleet is broken at the identity. One canon, one vector file, removes that failure mode by construction.

Conformance is not a claim on a slide — it is asserted at boot. self_check! mints, encodes, decodes, and hashes a known id down both the native and pure-Elixir paths and checks each result against a committed vector. A node whose native core disagrees with the pure one never reaches its first message. Select a vector below and read what it proves.

The placement line is the placed property read at boot: the id USR0KHTOWnGLuC encodes the snowflake 274557032793636864, and hash32(274557032793636864) is 234878118 down both paths. The parse line proves a round trip recovers the namespace and the snowflake exactly. The decode line proves the codec is total in the safe direction — USRzzzzzzzzzzz would overflow 63 bits, and the codec answers :error rather than wrap to a wrong number. These are source truths, not benchmarks — no number on this page is a measurement.

The USR namespace in these vectors is the manuscript's illustrative brand for teaching the id contract; it is the figure exactly as the runtime asserts it. A real application uses its own brands — codemojex mints PLR, ROM, GAM, GES, and JOB.

What ships today is honest to state: the bus is Elixir, in echo/apps/echo_mq. A Go or Node worker fleet does not run in production now. The polyglot fleet is the conformance target — the wire protocol and the id contract are precisely what make it reachable, because a worker in any of the five runtimes can mint, parse, and place the same id and address the same braced keys over the same wire. The id is the thread that ties a worker to the bus regardless of the worker's language.

That target is the dedicated EchoMQ course's subject — the polyglot protocol, the full Lua inventory, and the conformance suite that proves a second runtime agrees with the first. This dive is the door to it.

When the fleet grows beyond Elixir, the wire and the id contract are already in place: a new-runtime worker implements the same codec, passes the same vector file, and drains the same braced queues. The operator's path to a second runtime is to satisfy the vectors — not to negotiate a new protocol.

The branded id is conformant: one source of truth and one vector file make encode and decode identical across Elixir, Node, Go, PostgreSQL, and WASM, and self_check! asserts the vectors at boot. That is what lets a polyglot worker fleet share one bus over one wire — the scale move of operating the bus, and the bridge to the dedicated EchoMQ course. Colocate, observe, scale: three operator moves, one bus.