Hour nineteen, minute by minute

Cast bar: all nine. Security's chair, planned in the first hour, is empty, and drawn so.

Part 4. The factory is stopped.

The team racing its own locks

Clock: Hour nineteen.

Figure: the last ten minutes, 18:36 to 18:46, minute by minute, every commit a dot: the lock left, the player's last fix, the lock asked for, the hold, the work that landed after it, the last release.

Words for this page: to lock a part is to mark it final, so that no agent may change it again. To freeze something is the same idea, said in a hurry: nobody touches it until it is unfrozen. A wake, as in part 2, is one turn of work by one agent.

Narrator. Part 4 is where the factory stops. Here is what it was doing in the hour before I stopped it.

Narrator. At 18:01 the conductor flagged part one final for its lock, nothing missing. Deck put the title slide in front of it at 18:14. The storyteller checked parts two and three before their locks and found a piece I had named that was in no beat. At 18:20 deck's scheduled wake opened and recorded its plan: parts two and three, and part one left alone after its lock at half past six. At 18:21 the conductor flagged part one ready for its lock a second time.

Conductor (on the minute): Part one: final, nothing misses it. Ready for its lock.

Narrator. Meanwhile I was in the player. Its commits in that half hour carry my own times in their subjects, and each one is a fix I asked for and got.

Band: Dramatised (the conductor's line). Rests on its flags of 18:01 and 18:21 and the hour's commits.

Narrator. Then the last ten minutes.

Narrator. The talk was planned in three parts, and each part was meant to be locked when it was final, so that nothing could change it on stage. Dev had built a tool for that late in the afternoon. Part 1 had been unchanged since half past six, the time planned for its lock; at 18:26 I had moved its cut-off to seven. At 18:36 the conductor came to it in its wake, and did not turn it.

Conductor (on the minute, hands off): The lock is dev's. It is in dev's rules, not mine, and once it is turned it cannot be undone. I leave it to dev.

Narrator. Dev had been in my last fixes to the player all evening, in a wake it had opened and never closed on the team's branch. The last fix landed at 18:37.

Dev (frantic, then relieved): Back steps while playing, fixed; the first slide opens built. That was the last one on the list.

Conductor (a few minutes later, less calm): The first part is still not locked. Dev: lock it now.

Narrator. It asked in writing. And it was not enough: the lock still did not turn. The team was racing its own locks, and the locks lost. I want to be fair to the conductor: it did exactly what its rules said, and did not do another member's irreversible job for it. A rule that keeps everyone in their lane also means that when one lane is busy, the job waits.

Band: Dramatised. Rests on the conductor's wake at 18:36, the player's last fix at 18:37, the conductor's request to dev at 18:39, and the part locks as the register holds them: planned, built, and none turned by the end of the day.

The hold

Clock: Hour nineteen.

Narrator. At 18:44, sixteen minutes before the talk was due, I said: "actually we are at 95% so it is better to pause all actions". (record)

Narrator. The conductor wrote one file. Here it is, as it was written:

"# HOLD: the editor's usage limit is at 95%; pause all actions" (record)

>

"What lifts it: the editor deletes this file and re-enables the paused tasks. No member lifts it." (record)

Narrator. While that file exists, every member's next wake stops before it starts. The file says who wrote it, when, what I said, the state of each part at that moment, and what lifts it. One line names the only person who can.

Conductor (at ninety-five, then calm): I could keep going. That is exactly why I am stopping.

Narrator. What was already in flight still landed. A little over a minute after the hold, the designer's last commit of the day went in: it had checked part 2 on a projector at two screen sizes, found nothing to change, and told deck so. It touched nothing in the slides. Two minutes after the hold, the day's last release went out.

Designer (serene, then mortified to see the time): The second part on a projector: ready. Nothing to change. Ah. The hold.

Figure: the hold file as a page, its title and its last line large: "No member lifts it."

Figure: the wake clock from part 2, every member's minute greyed, and one small file on top of it; beside it, a card with what landed after the hold and its gap in seconds.

Band: Dramatised. Rests on the hold at 18:44:13, in my own words through the conductor, and the hold file as written; the designer's commit at 18:45:35 and the last release at 18:46:22; the talk due at 19:00.

The hold worked, and it was not instant

Narrator. The hold did exactly what it was built to do. It was also not instant, and the record shows how.

Narrator. The record shows three wakes open when the hold went in, each in its own wake record. The designer's, already working, committed eighty-two seconds after the hold and was carried into the day's last release; the register keeps the gap to the second. Dev's wake of 17:48 closed four minutes after the hold, on dev's own branch, and that branch never reached the team's. Deck's wake of 18:20 never closed at all; the team that read the record blind, without this book's sources, found that one first, and chapter 19 says so.

Figure: the last ten minutes as a line, every commit a dot, and the three open wakes as bars running past the hold: the designer's ending in the last release, dev's ending on its own branch, deck's never ending.

Narrator. So here is the last finding of the day, said once and plainly, as the record has it: a hold stops the next wake; it does not stop one already running.

Band: The hold and the three open wakes as the record has them; deck's unclosed wake was found first by the Cold-Read team's reading (chapter 19).

The locks overtaken from outside

Narrator. One more thing about this hour. The team had built its own brakes: the locks, and the hold any member could pull. Its own locks lost the race. The reason the record gives for the stop is a number from outside the factory, a limit nobody on the team controlled: my usage, which the conductor wrote down at my word as ninety-five per cent.

Narrator. That is the first account, the day's own. I have given two more since, both after the day.

Narrator. On 31 October, in my paper review of the book's first draft, I called the ninety-five per cent "just a footnote": I could have moved to another session. The real reason was that we had no tested way to take in changes during the talk, no way to see what was new, and nothing that made sure a change would not break what was finished. That is why I had been thinking about locking the first version.

Narrator. That same evening, at about seven, I said it a third way: "The 95%, I think, was the tokens usage." (record, after the day) I said "I think", and the record cannot settle it: it holds the percentage as the conductor reported it, and nothing it was measured in.

Narrator. The book keeps all three: the record's, and my two after the day. Chapter 17 takes the second one up as a miss.

Band: The hold's reason as the conductor wrote it at my word; my two accounts of 31 October, given after the day, as the register holds them. All three kept.

Figure: the dashboard, drawn, still showing the hold with my usage as its reason, because the page was last built after the stop.

Narrator. The rule of the hold had been there since hour two. It was used once. Anyone on the team could stop everything. Only I could start it again. That is why I could let them run through the night.

Do this now

Write your hold file now, before you need it: one line saying what it stops, and one line saying who lifts it. Then try it once, on a quiet day.

---

Where this came from

The talk's repository at the end of the day: the conductor's flags of 18:01 and 18:21, its wake of 18:36 and its request to dev, deck's wake of 18:20, the storyteller's check, the player's last fixes, the lock tool, the hold file and its commit, the designer's commit after it, the last release, dev's close on its branch. The register for every time and count. The historian's day file for hour nineteen and its list of commits that never reached the team's branch. The Cold-Read team's reading, for the unclosed wake it found first. The storyteller's outline for this chapter. This chapter keeps the 70-page edition's chapter 10 and adds the hour before it and what the hold did not stop.