One Human, Nine Agentsbook.sgit.ai v0.1.391 Star this site on GitHub

The 70-page edition, being written, online: under each scene, what it rests on. Made by review/tools/make_editions.py from the writer's chapters.

What did not work

Cast bar: all nine, after the hold; security's chair empty. Off the clock now.

Narrator. This chapter has no clock in the margin. The day is over; what is left is the accounting. I want it at full size, because the failures are the useful part, and because a book about a factory that only shows what worked would be a brochure.

Why stop then: three answers

Narrator. Why stop then, sixteen minutes out, with part 1 still unlocked? I have given three answers, and the book keeps all three.

Narrator. On the day: my usage was at 95%. That is what the hold file says, in the conductor's words for mine.

Narrator. In the early hours of 31 October, two days later: the 95% was 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 no workflow that made sure nothing would break. That is why I had been thinking about locking the first version.

Narrator. That evening, on 31 October: the 95% was the token usage.

Narrator. I am not going to pick one for you now. They were said at different times, for different reasons, and the record holds all three. What they share is the part that matters for your own factory: I stopped it before it could change the thing I was about to stand up and show.

Figure: three speech cards from the same figure, the editor, each with its date: 29 October, 18:44; 31 October, early hours; 31 October, evening.

Band: My three accounts, as the register holds them; the later two were given after the day.

What did not work: the interview

Figure: ruv-sgit's strip, the researcher interviewing deck about the claims that did not hold, placed whole (lab/experiments/25-ruv-the-cast-strips/edition/strip-10-07.svg).

Narrator. The failures stay in, at full size. Here they are, one at a time.

Narrator. The lock, first. Dev built it late in the afternoon so that finished slides could not change on stage.

Dev (rueful): I built a tool to freeze the finished slides, so nothing could change them on stage. I never ran it.

Dev (more quietly): I was in your player fixes until the end. The last one landed just before the hold. The lock was still waiting.

Narrator. The parts, second. The talk was planned in three, each with its own time to lock.

Deck (overwhelmed): Only the first part was ever finished.

Deck (to itself, rearranging slides that will not be shown): The second and third were in progress at the hold. I reviewed other agents' work all night. I did not finish my own.

Narrator. The moment that was missed, third. In the afternoon the talk was split into its parts. The storyteller arrived after two, and its slot came round between the deadlines.

Storyteller (rueful): My turn came between deadlines, and I missed the moment the talk was split into its parts.

Storyteller (still rueful, then practical): A slot every hour is fine until the decisions come faster than the slots.

Narrator. And one miss, and what it cost. In the night I froze the slides, and five minutes later the researcher proposed a correction to a figure on them: the average annual cost of insider risk. The figure had been on the definition slide since the first pass at 00:40. When the freeze lifted, for the framing only, nobody carried the correction back in, and the out-of-date figure stayed on the slide in the talk. The checks found it; the freeze hid it.

Narrator. The lesson for your first week: when you freeze something, write down what is waiting to go in when you unfreeze it.

Narrator. The figure itself, so you can judge the miss: the slide said $17.4M a year, the 2025 edition's number; the 2026 report says $19.5M. Not a disaster on stage. A small, true error that the record caught and the freeze kept in.

Narrator. The talk's own register of claims, built that evening, graded every claim it made: 320 of them. 210 held, 55 held in part, 52 were not checked, and three did not hold. None of those three was said on stage.

Narrator. Where they were: one in the article only, one on no beat or slide at all, one in the story tree only.

Researcher (unbudging, ticking a list): I marked each one that did not hold. The talk went round them. The day's checks worked, and they also missed. Saying where is part of the method.

Figure: a "what did not work" card per miss, each with its id in small type: the lock never turned; two parts of three unfinished; the moment missed; the correction lost in the freeze; the three claims that did not hold.

Band: Dramatised. Rests on the part locks and their state at the hold, the talk's register of claims and its three that did not hold, the freeze at 02:47 and the correction proposed five minutes later, and each member's own debrief.

Do this now

Write down your last three misses, each in one line: what it was, what it cost, and what you would put in place so the next one is caught sooner. Keep the list where your agents will read it.

---

Where this came from

My three accounts of why we stopped, as the register holds them, the later two given after the day. The talk's repository at the end of the day: the lock tool, the freeze and the correction proposed after it, each member's own debrief. The talk's own register of claims and the three that did not hold. ruv-sgit's interview strip. The storyteller's outline for this chapter. This chapter grows from the 30-page edition's chapter 4, sections 3 and 4.

The numbers in this chapter

From the researcher's register (claims/register.json).

  1. C006 The hold: 18:44:13, 867f8c2 '@conductor: hold: the editor's usage limit is at 95%, pause all actions'; released as v0.1.208 at 18:44:49 (7968c99) checked
  2. C027 The part locks and their state at the hold:
    • planned:
      • part_1: 18:30
      • part_2: 19:30
      • part_3: 20:00
    • lock_tool: admin/build/lock.py, 4a2481b at 17:54
    • state_at_18:44: part 1 final since 18:30 but not locked; parts 2 and 3 in progress
    • locked_by_end_of_day: 0
    checked
  3. C029 The talk's own claims register:
    • claims: 320
    • built: 2026-10-29T18:20Z
    • grades:
      • A0: 13
      • A1: 23
      • A2: 182
      • A3: 31
      • A4: 11
      • A5: 12
      • A6: 48
    • holds:
      • holds: 210
      • holds in part: 55
      • not checked: 52
      • does not hold: 3
    • kinds:
      • measured: 105
      • own-site: 100
      • event: 67
      • position: 26
      • observation: 18
      • guess: 4
    checked
  4. C030 The talk's three claims that do not hold:
      • id: amazon-q-two-days-live
      • where: the article only
      • finding: no capture says two days; reports date release to clean version about a week
      • id: asrs-100k-a-year-1-8-million
      • where: talk:unreported, slide:unreported, the article
      • finding: NASA's own briefing: 121,128 reports in 2025, over 2.3 million since 1981; 1.8 million is stale
      • on_stage: no: no beat or slide at 298be4e carries it (talk.json has no 'unreported' beat)
      • id: story-r5-surface-smaller-more-mature
      • where: the story tree only
      • finding: no source for 'smaller'
    checked
  5. C031 $17.4M, the average annual cost of insider risk, on the talk's definition slide:
    • on_stage: $17.4M (Ponemon for DTEX, 2025 edition), written at 00:40 (1f7c633) and never changed
    • at_source_2025: $17.4M, 'up from $16.2M in 2023' (dtex.ai blog, 2025 report)
    • at_source_2026: US$19.5M, the 2026 Cost of Insider Risks Global Report (ponemon.dtex.ai landing page)
    • correction_proposed: a082c52, 02:52: the talk's researcher proposed the exact replacement text to deck (evidence/proposals/deck-talk-changes.md)
    • freeze: 02:47: the editor, in deck's session: 'do not touch the deck. talk.json and the slides are frozen from now on' (team/deck/requests/researcher__before-tonight.md, deck's 03:00 update); D01 in the editor's register from 04:12 (91772e6)
    • freeze_lifted: 14:07, for the framing only (c9ced4e, conductor-notes.md)
    • after_the_lift: the definition slide file has no commit after 00:40; talk.json had 8 commits after 14:07, none touching the $17.4M cue
    checked
  6. C089 Why the team stopped: the editor's own account, given after the day, against the day's record:
    • day_record: the hold at 18:44:13 gives the editor's usage at 95% as the reason, in the conductor's words (C006, C021); the locks were built and never applied (C027)
    • editor_31_October: the 95% was 'just a footnote': he could have moved to another session; the main reason was that there was no tested way to take in changes during the talk, no UX to see what was new and no workflow that made sure nothing would break, 'the reason why I was thinking about let's lock V1'
    • editor_31_October_19:00: 'The 95%, I think, was the tokens usage. That there was a token that we stopped, and there was a big thing about 95%.' (briefs/2026-10-31__in-session/02-g1-the-95-and-the-day-in-review.md, ec1ec00)
    • what_the_record_shows: the hold's subject: 'the editor's usage limit is at 95%, pause all actions' (867f8c2); C021: 95% is the conductor's words reporting the editor, about a 5-hour usage window resetting at 20:20 London (C037); no usage page, no token count
    • what_the_record_cannot_show: whether the 95% was of tokens, of a message allowance or of anything else: the record holds the percentage as reported and nothing it was measured in
    open