B0 · Overview
The whole idea, in three dives.
The shortest path into the Branded Component System: the one move it makes, the contract that move leaves behind, and the shape of the stack the rest of the course builds.
Three dives. Read these, and every later chapter is an elaboration of one of them.
The three dives
each a leaf, the teachingThe one relocation
The single move: the encapsulation boundary leaves the object and surrounds the system, and the object’s last possession — its name — is promoted to the interface.
B0.2Identity as a contract
Why the name is not a string but a contract: typed by namespace, ordered by mint time, placed by hash, conformant across runtimes.
B0.3The stack and the floor
The shape of what the course builds: echo_data, the bus, the store, and the durable floor beneath the volatile tiers.
A chapter is three dives. Each dive is one idea with one figure you can take apart.
The contract, verified
echo_data · branded_id.exThe id is fourteen printable bytes: a three-byte namespace and eleven Base62 characters carrying a 63-bit snowflake. The course inherits one rule from the manuscript — a number the committed tree cannot prove does not appear — and the contract proves its own, asserted at boot before either code path is trusted: placement(USR0KHTOWnGLuC) is 234878118 on the native and pure paths alike.
placement(USR0KHTOWnGLuC) → 234878118 native and pure agree parse(USR0NgWEfAEJfs) → {:ok, "USR", 320636799581945856} decode(USRzzzzzzzzzzz) → :error an overflow is refused, not wrapped
The doors
the sibling coursesEchoMQ — the protocol, in depth
The bus B3 narrates, taught rung by rung: the keyspace, the Lua inventory, and the 3.0 Stream Tier — XADD, XREADGROUP, XACK — with conformance on Valkey.
Redis Patterns Applied
The substrate patterns under the bus: sorted sets, atomic Lua moves, locks, and streams — the judgement layer.
/echo-persistenceEcho Persistence — the durable floor
Beneath the volatile tiers: the Graft page engine built twice, the commit-LSN loop, and the stream archive on Tigris. Where Part I says state lives somewhere, this says where it lives durably.
References
sources · relatedSources
- Erlang/OTP — the ets moduleownership and ordered_set term order
- Hoare — Record Handling (ALGOL Bulletin 21, 1965)the tag inside the value the namespace descends from
- King — Announcing Snowflake (2010)the roughly-sortable id the contract hardens
Related
- BCS — the course homethe law, the id anatomy, the chapter map
- Echo Persistencethe durable floor beneath the bus