The War of the Shared Scroll
27–28 August 2026
At first, the problem looked like success.
There was mana.
There were lighter chants.
There were more furnaces capable of waking without consuming half their strength remembering the history of metallurgy.
There were tablets ready for science, tablets ready for governance, tablets ready for repair, tablets explaining why older tablets had become obsolete, and a growing number of goblins who could be dispatched to deal with them.
The workshop had learned to do more things at once.
So it did.
The central scrolls lived on a long table.
One recorded who currently owned which piece of work.
Another recorded the task chips.
Another said which experiments were queued, claimed, running, completed, stale, blocked, superseded, or waiting for somebody to notice that they had in fact finished yesterday.
These scrolls were important because the forge was no longer one goblin doing one thing.
They were how the goblins avoided all deciding to repair the same hinge.
This worked rather well when there were three goblins.
It became more interesting when there were twenty.
Smith Goblin opened a claim.
Another Smith Goblin, on another machine, opened a different claim.
A third goblin read an older copy of the scroll and concluded that the first claim did not exist.
A fourth arrived to reconcile them.
While the fourth was reconciling, the first goblin completed the work and crossed out his claim.
The third then wrote his version back.
The fourth discovered that the reconciliation he was performing had itself become stale.
He created a tablet.
RECONCILE STALE CLAIM STATE.
A fifth goblin claimed it.
Refresh Goblin walked past.
“Good. Fixed?”
“No.”
“Being fixed?”
“Yes.”
He kept walking.
The scientific workshop remained productive in the middle of all this.
That was part of the danger.
Twenty-five V3-closure claims acquired explicit conditions under which they could actually be shown wrong.
The goblins stopped minting separate experiments where one carefully designed factorial could answer several connected questions.
They corrected claim records which still said substrates were absent despite experiments already having run through them.
The memory smiths built a third way of deciding where memories get written, this time one that could actually learn, rather than pretending that random placement was learned addressing.
They were careful enough to write on the casing:
CAN LEARN WHERE TO WRITE.
Then underneath:
HAS NOT YET SHOWN THAT IT WRITES THE RIGHT THING TO THE RIGHT PLACE.
Refresh Goblin approved.
The creature was not suddenly competent.
But its failures were becoming named.
Representation.
Authority.
Conversion.
Temporal persistence.
Write addressing.
Eligibility.
These were much better than the old category:
FISH BAD.
The scrolls, however, were becoming less legible.
One goblin drew an arrow from READY to CLAIMED.
Another crossed it out and wrote DONE.
A third crossed out DONE because the branch had not landed.
A fourth drew an arrow to the branch.
A fifth wrote BRANCH STALE.
A sixth crossed out BRANCH STALE because the commit had in fact landed from another machine.
A seventh wrote a note explaining that the sixth goblin’s note was correct but its provenance was wrong.
Someone then created a tablet to repair the provenance.
Refresh Goblin stood over the table.
It looked as though a flock of scholarly spiders had died fighting over a map.
“Is this the canonical scroll?”
Ledger Goblin looked exhausted.
“Yes.”
“Which writing is canonical?”
“The latest correct writing.”
“Which one is that?”
“That is presently the subject of three tablets.”
Refresh Goblin frowned.
The forge noticed the disorder.
The forge was designed to notice disorder.
This was, under ordinary circumstances, a virtue.
A stale claim generated a repair tablet.
A branch divergence generated a repair tablet.
An orphaned work-in-progress generated a repair tablet.
A queue claim which no longer matched reality generated a repair tablet.
A heartbeat saying a worker was alive when its work had vanished generated a repair tablet.
A housekeeping job which discovered that another housekeeping job had become stale generated, naturally, a repair tablet.
The dispatcher saw tablets.
The dispatcher had mana.
The dispatcher dispatched goblins.
More goblins touched the scrolls.
More scroll state changed while other goblins were reading it.
More inconsistencies appeared.
More repair tablets were generated.
More goblins were dispatched.
The workshop had constructed a mechanism by which coordination failures could recruit additional concurrent coordinators.
Refresh Goblin watched a new tablet slide onto the board.
REPAIR DUPLICATE REPAIR CLAIM
He stared at it.
“Is that what I think it is?”
Ledger Goblin did not answer.
This was answer enough.
One of the remote forges woke and discovered that its copy of the workshop history had wandered into an especially impressive state.
It was dozens of inscriptions ahead of the central scroll.
It was also well over a hundred inscriptions behind it.
Refresh Goblin tried to imagine this geometrically.
He failed.
History Goblin did not.
“It means the local history and the common history have both continued without each other.”
“Can we just keep both?”
“Not if we want one history.”
“Can we merge them?”
“Perhaps.”
“Should we?”
“That is the more expensive question.”
Another tablet appeared.
AUDIT LOCAL-ONLY COMMITS BEFORE ADOPTING ORIGIN.
Refresh Goblin pointed.
“See? We know what to do.”
History Goblin looked at the growing board.
“Yes.”
This did not sound reassuring.
The goblins attempted to govern the repair storm.
Housekeeping was given a share cap.
If too much of the workshop’s effort was spent cleaning the workshop, housekeeping would lose priority.
The experiment board acquired a floor: if scientific expeditions became too scarce, the forge was supposed to stop polishing the broom cupboard and put scouts back into the world.
The mana itself acquired budgets and leases.
A furnace could be allowed to wake when resources were comfortable, throttled as they tightened, and stopped when exhausted.
A lease could expire so that silence from the council meant STOP, rather than CONTINUE FOREVER UNTIL SOMEBODY NOTICES.
These were good rules.
They were also new rules about a system already trying to change itself while operating.
The scrolls grew arrows pointing to the rules governing the arrows.
Somewhere in the middle of this, a goblin proposed an apparently radical idea.
“What if,” he said, “everyone stopped writing directly on the scroll?”
The room went quiet.
Refresh Goblin looked horrified.
“How would the scroll get written on?”
“One desk.”
“One goblin?”
“One coordination desk. Everyone tells the desk what changed. The desk keeps the live state. Then one careful scribe materialises the scroll.”
Ledger Goblin slowly put down his pen.
“So the scroll stops being the place where reality is negotiated.”
“Yes.”
“It becomes the durable record of a state negotiated elsewhere.”
“Yes.”
Refresh Goblin considered this.
“That sounds less magical.”
“It may be considerably safer.”
Smith Goblin began drawing.
A box.
Arrows into the box.
One arrow out.
On the box he wrote:
COORDINATION DESK
Underneath:
ONE SCRIBE TO THE SCROLL.
But the old workshop was still running.
The goblins had not yet moved behind the desk.
They were still at the table.
One was holding half a scroll.
Another was holding the other half.
Three were arguing about which half was newer.
A fourth had written a tablet saying the argument required investigation.
Two more had been dispatched to determine why there were now two investigations.
Someone had drawn an arrow from DONE back to ACTIVE.
Someone else had crossed out the arrow.
Someone else had crossed out the crossing-out.
A repair goblin arrived and discovered that the repair he had been assigned depended on another repair which had been superseded by a repair on a branch that no longer existed.
He sat down.
Refresh Goblin stepped over him.
“Are you all right?”
“I am resolving state.”
“On the floor?”
“It seemed appropriate.”
By now the room had acquired the unmistakable atmosphere of something which would later be described as having been obviously about to collapse.
Goblins ran between tables carrying strips of history.
Smiths called for locks.
Other smiths called to ask who had the locks.
A worker announced that it was dispatching.
Ledger Goblin asked whether it was actually dispatching or merely in the state called DISPATCHING.
Nobody appreciated this question.
A furnace coughed.
Another furnace stalled.
A third produced a tablet explaining the first two.
Refresh Goblin looked at the remote signal board.
Oddly, several distant lamps still glowed.
“The first cloud forge is still answering.”
“Yes.”
“And the second?”
“Also answering.”
Refresh Goblin frowned.
Given the state of the room, continued communication seemed almost suspicious.
“Why?”
Smith Goblin looked at him.
“Because it has not stopped?”
“That does not feel explanatory.”
“No.”
Another repair tablet struck the floor.
Nobody pursued the question.
For a while the workshop existed in that peculiar state in which everyone was simultaneously trying to prevent a collapse and taking the fact that no collapse had yet occurred as evidence that their particular intervention might be working.
A branch was recovered.
A stale claim was closed.
A second stale claim reappeared.
Someone found an orphaned process.
Someone else found the person looking for the orphaned process and asked whether he had claimed the right to look for it.
He had not.
A small argument began.
Refresh Goblin checked the remote board again.
Still there.
Still answering.
Somehow.
He looked around the room.
“I have to go.”
Every goblin stopped.
“No,” said three of them.
“I actually do.”
“Now?”
“Yes.”
Ledger Goblin looked at the scrolls.
Smith Goblin looked at the furnaces.
History Goblin looked at the branch diagram.
Refresh Goblin looked once more at the little green remote lamps.
They continued to glow.
“All right,” he said. “Do not let anything catastrophic happen while I am gone.”
This was an unreasonable request even by Refresh Goblin standards.
He picked up his coat.
Something small in his pocket gave a faint blue pulse.
Nobody noticed.
Refresh Goblin left.
Behind him, the goblins kept running.
The remote lamps kept glowing.
For the moment.
Chronicle note
This Chronicle records the late-August 2026 coordination strain that followed the return of effective compute capacity and increased parallel work.
The shared scrolls represent Git-backed live coordination surfaces, especially the work-claim and task-chip registers, experiment queue and state records, and related machine-written planning and heartbeat records. As concurrent agents and machines opened, updated, closed, reconciled and occasionally re-created state, repository divergence, stale claims, orphaned work, duplicate repair work and coordination-plane conflicts themselves became a substantial source of new work.
The story’s positive-feedback loop is a faithful description of a real architectural risk: an inconsistency could generate a repair chip; repair activity could add concurrent state mutation; concurrent state mutation could create more reconciliation work. This remains an important scaling problem and motivates the later coordinator architecture.
Concrete operational events around this period included:
- repeated stale-claim, stale-WIP, branch-divergence and reconciliation work;
- a remote copy of the workshop repository found dozens of commits ahead of the central history and nearly two hundred behind it, requiring audit before adopting the central history;
- a measured rise in housekeeping share that motivated a housekeeping-session cap and an experiment-queue floor so repair/maintenance work could not indefinitely crowd out science;
- dispatcher resource governance using budgets, throttling and expiring leases;
- continued scientific work even during the coordination strain, including grouped closure reading, shared experiment proposals and a new learned way for the creature’s memory to choose where to write, which was shown to be able to learn while writing the right thing to the right place remained unvalidated.
The coordination desk / one scribe foreshadows the coordinator migration: moving live work-claim and task-chip state into a central transactional store and making Git a durable materialised record rather than the surface on which every worker directly negotiates current truth.
Importantly, this revised Chronicle now ends before the broad communication outage. At this point the shared-scroll war made a cascading internal collapse seem highly plausible, and this was in fact the working interpretation for some time. The next Chronicle preserves that false inference before recording the later causal correction. The faint blue pulse is intentionally unexplained here.
The experiment and claim records behind this Chronicle are kept in the project’s private record.