The coder's files

One page per kind of file in the coder instrument (v32) and the run yard. Each page says what the file holds, who writes it and when, why it exists, and where it is. The levels below follow the coder page, from the contracts that govern every agent down to the yard that runs every room; how it was built tells why each level came to exist.

1. What governs: the contracts and notes

One contract holds the method. The others exist because the roles differ: a large room needs a case lead and fleet coders, the week before the canvas needs a brief writer, and the yard needs a scheduler. Each role file says only what differs from the main contract.

2. One room

Everything needed to code a community sits in its own folder, so a room can be run, rebuilt or forked on its own.

3. The tools

Handing an agent the material and asking for codes did not work: it spent its turns writing parsers and serialisers, and its account of its own reading could not be checked. Each tool takes one job away from the agent and leaves a record.

Reading, citing, emitting, closing

Building a directory and its corpus

4. The serial fleet and the case lead

A room of more than 500 items does not fit one reader. It is cut into slices, read by one coder after another, and handed to a case lead who writes the account.

5. The yard and its scheduler

The yard, file by file: every part of the yard the scheduler built, what it is, who writes it, what a new yard handler reads first, and what to change to run a yard elsewhere.

The yard runs every room, smallest first, under a scheduler. The case lead is the one agent saved whole, so a room can be resumed or forked later.

Other yard tools, without a page of their own

Each line is the script's own first line.