jonnify·bcs /bcs/together

B6 · Putting It All Together

Four systems, one stack.

The course’s four libraries compose into one dependency-ordered umbrella, wire ← data ← mq ← store, booting only after the identity contract proves itself. Then a write goes all the way down, and a read all the way up.

Three dives. The umbrella and its boot; one write down through the outbox, a lane, and a flow; one read up the four-tier ladder, kept current by coherence.

A system over four libraries; a write descends, a read ascends. Select a part.
a BCS system echo_store · cache + floorecho_mq · the busecho_data · ids + storesecho_wire · the wireone dependency-ordered tree a writestore → lane→ floor a readcache → store→ floor
readout · Select a part. Four libraries compose into one dependency-ordered tree; a write descends to the floor through the outbox and lanes; a read ascends the four-tier ladder.
§1

The three dives

each a leaf, the teaching

A chapter is three dives. Each dive is one idea with one figure you can take apart.

§2

The whole, in one law

echo · the umbrella

B6 puts the course together: the four libraries — echo_wire, echo_data, echo_mq, echo_store — compose into one dependency-ordered umbrella, wire ← data ← mq ← store, that boots only after the identity contract proves itself. A write begins at a system’s store and fans out through a transactional outbox: record the intent, enqueue on a lane, mark it enqueued, with replay covering every crash window; multi-step work rides an atomic Flow, settlement rides a lane, and the write ends durable on the floor and announced by coherence. A read climbs the same stack in reverse — a caller-side L1 hit, or a miss filling down through Valkey, the store, and the floor — ETS to Tigris, one branded id keying every tier. The pieces are not merged; they are composed, fast at the top and durable at the bottom.

§4

The doors

the sibling courses
§4

References

sources · related

Sources

Related