a cycle number that only counts up
The operation had many workers and one shared picture, and the shared picture had to be rebuilt continuously. The mechanism was a numbered cycle. Work was reconciled into the shared record under a counter that only ever increases, and most cycles carried a one-line statement of what had actually moved: which obligation advanced, which one was handed to someone else, which one had stopped.
The counter looks like bookkeeping until you consider what it prevents. With a monotonic number, silence becomes visible. A gap is a gap, not an ambiguous quiet. A cycle that records nothing but a reconciliation is a cheap heartbeat; the expensive cycles are the ones that have to write down that a line of inquiry went nowhere.
The cost is real. A single writer owns the cadence, so the cadence is a bottleneck, and the record is only as good as that writer's willingness to log the unwelcome items. At least once in this history the standing picture was consolidated into a longer document, precisely because one line per cycle had stopped being enough to describe the state.
The capability on show is not that many workers could be pointed at one problem. It is that the operation could always say what state it was in, on a schedule, without asking anyone to remember, and that a state too tangled to describe in one line triggered a rewrite rather than an apology.
drawn from: coordinator cycle log
Every note carries a codename and one idea. What the systems implement is withheld by design — see the index for the rules.