B1 · Ideas Behind — manuscript Part I

The conceptual floor.

Part I is the floor every later Part stands on: the law in three clauses, the identity contract read as architecture, the storage economics that priced the contract, the ECS arc that distribution completes, the time inside the name, and the encode trial that closes it.

The manuscript states Part I as assertion and argument; Part II begins demonstrating. Each module below teaches one written chapter, with its committed evidence quoted verbatim on the page.

The Part I arc — six chapters in reading order. Select a node to read its thesis.

readout · Select a chapter to read its thesis. Reading order runs left to right; B1.1 is the start of the course's substance.

§1

The six modules

content/bcs1.1.md – bcs1.a1.md

B1.1

The System Substrate

The law, executable: a boundary gate, a private-ETS property store, a supervisor. Six gates refuse the canonical crimes on stage — the transcript reads PASS 6/6.

3 divesbuilt B1.2

The Identity Contract, Read as Architecture

The contract property by property — namespace, order theorem, hash32 placement, canon — each read against the failure it retires.

4 divesbuilt B1.3

Choosing the ID System

The chooser, settled by measurement on Valkey 8.1's new hash table: seven key shapes, two engines, a million keys each. The branded form ties binary UUID-16 at 65 bytes and beats its own decimal.

4 divesbuilt B1.4

From ECS to BCS

What distribution changes: the index-handle's three deaths — the save file, the socket, the foreign store — each traced to a missing contract property; the ECS→BCS translation table.

3 divesbuilt B1.5

The Time Inside the Name

Time as a subject: the 41-bit horizon (September 2093), the law of two clocks, the monotonic mint floor, and the store's TTL as a third clock deliberately unmerged.

3 divesbuilt B1.6

Branding Beats Its Own Integer

The encode trial in five runtimes: C 2.8×, Rust 4.2×, the BEAM a tie, and the one V8 loss in exactly the place the contract prescribes the wasm crossing.

3 divesbuilt

A module card becomes a link when its pages ship. The dives per module are fixed in the chapter spec; the reading order is the arc above.

§2

The floor under the floor

committed outputs, quoted verbatim

Part I is fully written, and every chapter is backed by a rung — an executable check script and a frozen transcript, committed beside the prose. The course inherits the ethic: a number that is not in a committed output does not appear on a page. The first rung sets the tone:

content/bcs1.1.md · the smallest faithful system, on stagefrozen

G1 reach-through ok   outside lookup/insert → ArgumentError; info: protection :private
G2 traveling-object   map/tuple/integer ids → FunctionClauseError 3/3
G3 typed ok           rejects 4/4 as :invalid; wrong namespace → {:error, :namespace}
G4 ordered ok         page_desc(2000) == byte-sort desc; store holds no clock
G5 placed ok          placement(USR0KHTOWnGLuC) → 234878118
G6 canon ok           self_check! → {:ok, :native}
PASS 6/6

§3

Up next

built as the manuscript ships

The Elixir BCS Core

Part II — systems as OTP applications, property stores, CHAMP, archetypes, relations.

6 modulessoon

The Bus

Part III — EchoMQ, Valkey-native: the keyspace, jobs as entities, the state machine in Lua.

7 modulessoon

B4–B8

Cache, Go, Node, Fly, Trading

Parts IV–VIII — the near-cache, the runtimes, production on Fly, and the trading capstone. The manuscript plans these chapters; the course builds them as the book ships.

15 modulessoon

§4

The doors

the sibling courses

/echomq

References

sources · related

Sources

Erlang/OTP — the ets moduletable protection levels, ordered_set term order — the substrate's ownership mechanism
The Go Project — Share Memory By Communicatingthe owner-goroutine pattern; sequential access by construction
Söderqvist — A new hash tablethe cache-line bucket design under the storage chooser
Lamport — Time, Clocks, and the Ordering of Events (1978)the foundation under the law of two clocks
King — Announcing Snowflake (2010)the roughly-sortable id the contract hardens to exact per node

BCS — the course homethe law, the id anatomy, the chapter map
EchoMQ — the coursethe far side of the B3 door
Redis Patterns Appliedthe substrate patterns, taught applied
Functional Programming in Elixirthe umbrella where echo_data lives