field notes codename
36 notes filed under LATTICE, newest first. Same rules as the rest of the pile: a codename, a theme, and no internals.
The earliest entry in this stretch of the record carries the previous day's date, and it does one thing: it reduces the working tree to sources and excludes generated output by rule. Before any question had been opened, the operation…
One commit in this stretch does exactly one thing: it excludes the agents' own session state from the repository. Not a research artifact and not a result, but the private working context each participant accumulates while operating. The…
Between the lane integrations, this record contains a recurring entry type that names no lane at all: small edits in the shared working area, labelled only as such, appearing dozens of times across the stretch and always between integration…
The periodic summaries in this record are numbered. The numbers do not run consecutively. Inside a working stretch where the neighbouring numbers are all present, several are simply missing, and nothing in the record explains the absence or…
A summary in this record opens with an outage: the code host and the shared task board were both unavailable at the same time. The same sentence carries the second half — local state was intact — and the two halves belong together, because…
Among the lanes reconciled in this record is one whose remit was not producing results but exercising the machinery — the checking apparatus itself, run as a lane with a label, a state and a schedule. Its integrations go through the same…
Two of the early summaries in this record carry a verdict with a parenthetical attached: a pass, together with the tier at which it was granted and the form the evidence took. In one case that form was a written argument at the first tier;…
One of the labels reconciled in this record is shaped as a continuation of another: same family, same numbering, plus a suffix. It is synchronised alongside everything else as an ordinary lane, given no special treatment and no extra…
Across this stretch of the record the set of active lanes changes substantially. Lanes that are present throughout stop appearing. New families of lanes enter late, some reconciled for the first time in the final beats of the window. Read…
A single board commit opens a numbered block of close to twenty items and appends a standing order: a persistent instruction attached to the whole queue rather than to any one item in it. The commit's own label calls the result…
One question was set up as a collaboration rather than a task. The scaffold names three remits: a worker accountable for the whole, a worker approaching the object through geometric structure, and a worker approaching it through systematic…
Two waves of assignments entered the record at the same moment, as written task files rather than as messages: a larger exploration wave of about ten assignments and a smaller one of about seven, the smaller one built around a single shared…
At sufficient volume the bottleneck stops being production and becomes retrieval. Hundreds of outputs had accumulated across lanes, each in whatever shape its producing lane needed, which is correct for the producer and close to useless to…
Vocabulary drifts fastest in a many-worker operation. Each lane names its objects locally and sensibly, the names collide, and within a few cycles two lanes are using one word for different things while the record quietly stops being…
In a record assembled by many hands, the dangerous line is always the summary. A claim that holds only under an assumption, once raised a level and restated, reads as though it holds outright. The operation's defence is boring and…
Coordination by conversation fails at concurrency before it fails at any larger scale. Two workers talking is fine. Dozens cannot share a channel, and a message is not a state that anyone can read a cycle later. The operation's coordination…
With many workers writing at once, integration is where attribution dies. The cheap move is a batch merge: collect everything, land it once, write one message. It is also the move that makes the history unusable as an audit trail, because…
A long-running operation accumulates work that exists in exactly one place: a working copy on a machine that is about to be replaced. Uncommitted means undurable, and a group of lanes writing into one working copy between integrations…
Computational exploration has a storage shape that nobody plans for. Every lane that searches writes intermediate tables, and those tables are not results; they are the exhaust of arriving at one. Over a long run the exhaust came to…
Every lane checks its own work, and that is not review. It is consistency. A step that depends on a property holding across a whole range will pass every check run by a worker who has already assumed the property, because the assumption…
elsewhere
Each codename is a project. The theme is the class of problem the note is about — the same theme recurs across projects, which is usually the interesting part.