How this backlog got built
Twenty Thinking pieces, built by parallel agents in isolated worktrees and merged through one shared registry file, including the batch that got built twice and the draft that almost named a competitor's model by brand.
Every piece in this registry, including this one, went through the same process: pulled from something real, drafted in voice, built by an agent in its own isolated git worktree, checked, merged into one shared file. The backlog started as a markdown table — slug, topic, source, status — with one rule: no invented filler, every row traces to a shipped PR, a saved note, an actual git log. Where the source was thin, the instruction was to write around the gap, not manufacture specifics. Verification before merge was mechanical: typecheck, lint, tests, a build, plus one check specific to this site — grep every draft for AI product brand names, since a site tied to a job at a company with its own model can't name a competitor's. It caught something real: one of twenty drafts named a specific LLM by brand three times, carried straight through from source material that had quoted it verbatim, caught before merge. The one real integration failure: two independent agent batches, neither aware of the other, built the same four pieces at once — one on-disk name in lowercase, the other uppercase. Nothing in either worktree could see the other; it surfaced only when the second batch's file listing came back already full of work that looked like its own. The fix wasn't a smarter agent — it was a habit, check what's running before starting a new batch. The tracker says what was planned. The registry says what shipped. Believe the registry.