The Village Hall

The organizer's phone promotes itself to Director. Every other phone attaches to it directly: no broker in the middle, no address that resolves outside the building.

The handshake is a QR code on the organizer's screen. It carries six lines, and they are the whole of what one phone needs to know about another.

Once a phone is through the door it receives the entire history from entry zero, and arrives current without replaying a decision of its own. It does not recompute the evening. It receives it.

The address

where that phone answers, on the hall's own network

The fingerprint

of a certificate the phone signed for itself the first time it was opened, and keeps

Who invites

the identity of the journal doing the inviting

Three channels

coordination, replication and commands — separate addresses for separate traffic

“cloud and microservice ecosystems become libraries the program invokes rather than habitats the program inhabits”

Paper 07 · After the Substrate

Every phone in the room keeps its own journal, and a journal is a directory in the application's private storage. There is no schema to migrate, no connection string, no engine to install and nothing to be reachable.

This is what makes the operational questions collapse into one another. Backing up the evening is copying the folder. Handing it to another phone is sending the same entries. Coming back after the signal dropped is replaying what arrived late.

In the substrate's own laboratories an entry encodes to between 33 and 96.7 bytes, against 118 to 910.7 for the same operation written out in full — and compressing the written-out form afterwards closes the gap only to fourfold, because the saving is in how the operation is named rather than in how the bytes are packed. Those are measurements of Puppeteer, not of this evening. What they say about the hall is that a night of bingo is a small file.

“For a journaled program, deployment is replay, replication is sharing history, backup is copying the program, and offline operation is delayed replay.”

Paper 05 · The Journal as Substrate

The number printed on the paper card is not a key into a table of cards. It is the card. Twenty-four numbers fall out of it by a keyed hash, the same way on every handset, so a phone that has never heard of that card can draw it correctly the moment someone reads the number aloud.

Nothing about a card is transmitted, stored or synchronized. A seller hands over a printed card and the buyer's phone already agrees with it.

Cardface Of(CardNumber number)
    stream  = HMACSHA256("bingo75.cardface.v1", number)
    columns = five bands drawn from that stream

When a ball is called, no phone receives a board. Each one receives the fact that a ball came out, and applies it to its own journal — the same operation the organizer performed, performed again locally.

A phone that closes and reopens does not ask anyone what it missed, because the marks were never only in memory. And a ball carries the round it belongs to: keying the wrong number twice in one evening is two corrections, not a repetition of the first.

ListenAs(role)
    .Told("Bolita").With<int>("numero")
        .Command("game.RegisterDraw(@numero);")
    .Told("Correccion").With<int>("malo").With<int>("bueno")
        .Command("game.CorrectDraw(@malo, @bueno);")

“Recording cross-actor messages as program operations preserves continuity edge by edge, without orchestration.”

Paper 04 · Preserving Semantic Continuity Across Actors