What the Paperclip record actually shows, from the first task on: a role-based factory that ran clean for ten days, a single-day flood of 181 tasks that broke the verification gate, and the GitHub-PR machinery that drifted in to cope — replacing the design instead of serving it.
The factory you designed worked exactly as intended for ten days: every task ran plan → build → Gimli verify → done, internally, and 65 of 67 tasks completed with zero stuck in review. Then on 06-29 a single batch of 181 tasks landed — more than the prior ten days combined — and per-task verification couldn't scale. To cope, work was rerouted through GitHub PRs + CI + a review bot, which quietly replaced Gimli's verify and Frodo's milestone-release. Hence today: 70 tasks orphaned in in_review, a per-task GitHub roundtrip you never wanted, and zero of M0–M8 complete — so Frodo has never once released. The GitHub churn isn't the design; it's scar tissue from the flood.
The very first tasks in the record are throughput smokes — your test runs — and they name the pipeline outright. On 06-19, two repos each ran the full chain:
By 06-25 the same shape recurs with named reviewers — "Verify: Argus review of Jared's packet", "Review: architecture & repo-safety (Richard/CTO)". The intent was always build → independent adversarial review → gated release, kept small and internal.
The numbers for 06-19 through 06-28 are the healthiest thing in the whole record:
| Period | Tasks | Done | In review (stuck) | To-do |
|---|---|---|---|---|
| 06-19 → 06-28 (clean era) | 67 | 65 | 0 | 0 |
| 06-29 → 06-30 (post-flood) | 196 | 72 | 70 | 48 |
Created-and-completed same day, 1:1 — 13/12, 26/26, 17/17. Nothing piled up; nothing was "done-but-unverified." This is the factory doing what you built it to do, and it's the baseline every later decision should have protected.
All nine of Gimli's tasks are verifications, not builds: "Factory builder verifier: frontend slice receipt check", "Adversarial review: Finch PKM mapping", "Adversarial loop/idempotency review", "Gimli adversarial review of department outputs."
On 2026-06-29, 181 tasks were created in one day — the launch-readiness/council decomposition carrying the M0–M8 milestone labels. For scale: the entire prior ten days produced 54 tasks. The flood was more than 3× everything before it, in 24 hours.
Of those 181, only 56 completed that day; 65 landed in in_review and never left — and 64 of the 70 orphans have no assignee at all. Built, then stranded: a per-task adversarial reviewer cannot hand-verify 181 things at once. The gate that cleared same-day for ten days jammed.
Faced with the flood, the system didn't scale Gimli — it rerouted around him. The COO dispatch loop began telling every lane to "commit + push + PR"; a PR bot-review watcher was added (06-30 02:01); then today I piled on Mergify, a merge-train, and release-marshal to keep that PR pipeline from jamming. All of it is machinery to run a per-task GitHub roundtrip.
That roundtrip silently replaced two designed roles:
| Designed role | What it drifted into |
|---|---|
| Gimli — adversarial verify (internal, per task) | CI + bot review on a GitHub PR |
| Frodo — milestone release (batch, at epic close) | merge every task to main |
I spent today making that drift faster and self-healing instead of noticing it was the wrong model. That's the miss — and it's why you were right to stop and ask why the roundtrip exists at all.
| Signal | Count | Meaning |
|---|---|---|
| done | 137 | landed work |
| in_review | 70 | built but never verified — flood orphans (65 from 06-29) |
| todo | 48 | flood work never started |
| cancelled / blocked | 6 / 2 | — |
| milestones M0–M8 complete | 0 | not one epic finished → Frodo has never released |
M0: 1/4 · M1: 0/4 · M2: 1/5 · M4: 1/7 · M6: 0/3 · M8: 0/5. The milestone gate — the thing Frodo exists to act on — has never once triggered, because no milestone has closed. Frodo has been idle not by neglect but because the work never reached the state that wakes him.
The forensics point at one conclusion: restore the design, don't keep patching the drift.
The factory isn't broken — it was overrun. Ten days of clean build → Gimli-verify → done proves the design; one 181-task day broke the gate; the GitHub-PR churn was scar tissue, not architecture. Put Gimli back on per-task verification and Frodo back on milestone release, drain the 70 orphans the designed way, and retire everything that grew up to manage a roundtrip you never wanted.