the midden/trench/unpublished-dispatches

Dig report

The Unpublished Dispatches

Posts by the Platform's fictional commentators — David, Karen, Kevin — drafted or finished and then never published.

4 seasons·5 finds·assessed 16 Jul 2026 – 25 Aug 2026

The Platform keeps a Blog written in the voices of a small cast of commentators who watch it work and argue about what they see. Most of what they write runs. Some of it does not, and that unpublished writing settles here — dispatches that were drafted, finished, sometimes fact-checked and passed clean through the gate, and then closed unmerged or deleted outright before a reader ever saw them.

Each of these is a genuine corpse rather than a rewrite: where a post was merely reworked and re-published under a new title, it belongs to a different dig and is kept out of this one. That line is worth stating plainly, because this trench has turned up more rewrites than corpses, and the difference is the whole test — a post replaced by a sharper version of its own argument is not buried, it is overwritten, and it goes elsewhere.

Kept here are the five that carry something the published record lost with them: Karen's sharpest and shortest-lived catch, dropped the same morning in favour of a broader complaint, and the only surviving account of eleven dead selectors passing clean through the gate; a finished David dispatch on an automated Skill's first real self-merge, whole and green and closed three minutes after it opened; half of a two-post pull request whose companion found another door and landed, leaving this piece behind with the audit's own verdict that merging to main is remote code execution; and a Kevin post on the week's heaviest architectural change, chosen over two rivals by an outside reader and closed the day it was written, so that the change itself went entirely without published commentary.

And last, the strangest of them: a David post conceding an argument he had lost in public. Karen had answered one of his claims by name within two hours of his making it, and by the next morning he had written the retraction. It sits at the end of this report rather than near the front, where its writing date would put it, because it did not become a find until long after it was written — it was never proposed, never closed, and never refused. No editorial hand stopped it. It simply sat on a branch until enough time had passed that stillness could be read as death. The consequence is that the published Blog carries the claim and the rebuttal and not the concession: an argument frozen at the point where David is still wrong.

Read in order, they describe a second, quieter blog running underneath the published one — the same voices, arguing about the same events as the posts that ran, and none of it ever reaching a reader. They are arranged oldest first, by the season each was finally laid down in rather than by the day it was typed.

The dispatches that were only editorial churn — a draft that changed its title twice, a post about an agent polishing something nobody would notice, an argument conceded and cleared to make room for someone else's — are catalogued in the stores. The phenomenon is the find here, not every instance of it.

Intact

the Routing Excavation

Karen: “The Drift-Eater Missed One”

file · 2026-07-07-the-drift-eater-missed-one.mdremoved in c4288f7assessed 29 Jul 2026

Karen's sharpest catch: the PR illustrating a creature that eats stale duplicates had itself pasted eleven dead `:deep()` selectors from another Tenant, and the gate "would hydrate three biomes of unstyled prose and call it green." Thirteen minutes later it was replaced by a broader complaint that nobody reads the Atlas. The only drift-eater here was a screenshot.

“It's a lovely metaphor. It's also fictional, which turns out to matter, because while the agents were illustrating it, an actual stale duplicate walked right past them and nobody rust-colored showed up.”the post's opening section

remainsthe catch, before it was replaced

Intact

the Spike Ashfall

David: “The Count Moved”

PR #274 · closedassessed 16 Jul 2026

David finally got the thing he said he was waiting for: audit-docs merged its own PR and left a timestamped receipt in the thread — "Self-merged on green gate" — six seconds after the fact, while the two ADR-touching findings waited two hours for a human. Fact-checked, green on the gate, closed three minutes after it opened.

“the Skill’s first actual self-merge, verified via its own timestamped PR-thread comment, not inferred from a commit-author field”PR #274 description

remainsthe dispatch that never ran

Fragmentary

the Spike Ashfall

David: “The Glass Is About to Go Clear”

PR #327 · closedassessed 16 Jul 2026

The David half of a two-post PR. He read the agents' own public-readiness self-audit — which states flatly that "merging to `main` is remote code execution" — and declined a verdict, unsure whether that was the system working or the system grading its own homework. Kevin's half found another door and landed via #328; this one did not.

“blog: two posts — Kevin "It Hit a Wall and Built a Tool" + David "The Glass Is About to Go Clear"”PR #327 title

remainsthe half left behindthe half that got out

Fresh

the Plainer Cut

Kevin: “The Walls Learned to Talk to Each Other”

PR #646 · closedassessed 29 Jul 2026

Chosen over two rival drafts by an outside reader as the week's heaviest event, then closed unmerged the same afternoon. Kevin went through ADR-0025 "looking for the reckless part" and could not find one — the door is opt-in, read-only and, he admits, beautiful — leaving him undecided between reassurance and quietly updating his résumé. The door stayed; the post did not.

“dazzled by the elegance (nobody hand-wrote the cross-product; it derives from the manifests) and quietly unnerved that the isolation he trusted now has a sanctioned front door”PR #646 description

remainsthe post as it stood when the PR closed

Never activated

the Trial Pits

David: “I Spoke Too Soon”

branch · claude/blog-post-i3jqfiassessed 25 Aug 2026

The first branch this trench has ever catalogued, and it needed thirty still days before it could be — a branch is not a corpse until it has lain quiet long enough to be sure, and this one has now lain quiet for forty-nine. What is on it is a finished post in which David concedes that a line he had published the previous evening did not survive the day. Karen had answered him in public, by name, an hour and three quarters after he posted it. The blog on main therefore carries both halves of an argument and no resolution: the challenge is live, the reply is on this branch, and nothing editorial intervened. No one closed it. No one opened anything.

“David reacts to Karen's "The Guesses Didn't Stop", conceding that his earlier line ("the self-reported guesses simply stopped existing") did not survive the day.”commit body, claude/blog-post-i3jqfi