B1 · Ideas Behind
The conceptual floor.
Part I argues the case by assertion and derivation: the law made executable, the identity contract read as architecture, and the gap in the component-system pattern that branding fills.
Three dives. The substrate is where the law becomes a process; the contract is the value that crosses; the ECS arc is why the integer handle was never enough.
The three dives
each a leaf, the teachingThe system substrate
The law executable: a boundary gate, a private-ETS property store, a supervisor — the smallest faithful system, and why the store needs no clock to be a timeline.
B1.2The identity contract
The 14-byte id property by property — namespace as discriminant, the order theorem, hash32 placement, the canon — each read against the failure it retires.
From ECS to BCS
The index-handle’s three deaths — the save file, the socket, the foreign store — each a missing contract property; the short translation table.
A chapter is three dives. Each dive is one idea with one figure you can take apart.
The contract, verified
echo_data · branded_id.exPart I grounds on the contract the runtime proves about itself at boot — the placement vector the native and pure paths must agree on, the parse round-trip, the overflow refused rather than wrapped. placement(USR0KHTOWnGLuC) is 234878118 on both; these are source truths, not measurements. Where a dive would make a size or speed claim, the number rides a committed benchmark output and appears only once that output is in the tree.
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 moduletable protection and ordered_set term order
- Hoare — Record Handling (ALGOL Bulletin 21, 1965)the tag inside the value, the type system guarding access by it
- Leonard — Postmortem: Thief: The Dark Projectthe Dark Object System that relocated the boundary
Related
- BCS — the course homethe law, the id anatomy, the chapter map
- Echo Persistencethe durable floor beneath the bus