Dig report
What the Record Claimed
Three finds where the Platform's own record held something that was not so — an entry on the list of recommended skills for a skill that was never there, a page recommended, delivered as a plan, and killed in one word, and a stand-in entry for a skill that said outright it did not exist.
In this report · 3 finds
- the
reviewentry with no Skill behind itNever activated - the third onrampNever activated
- the
scaffold-tenantskill entryIntact
All three finds here are entries in the 's own record that were, in different ways, not true of the Platform: a recommendation for a skill that did not exist, a recommendation for a page that was never built, and a stand-in for a skill that announced its own absence. None is a lie. The first two are the ordinary way a written record drifts from the thing it describes when nobody has occasion to check; the third was a fiction from the start, labelled as one, and outlived the reason it was written.
the Trial Pits · 25 Jul 2026 – 12 Aug 2026
the review entry with no Skill behind it
file · review.ymlremoved in bac30ecnever workedassessed 25 Aug 2026
An entry on the platform's own list of skills worth trusting, graded for importance, annotated with a note about which tooling to substitute — and pointing at nothing. There was never a review skill. Not on disk, not in the lock file, not in any session's list of what it could call. Its sibling entry carried a checksum of the installed source; this one had no source to checksum. It stood on the recommended list for thirty-one days and was found by a mechanical audit sweeping for entries whose skills had gone missing — not by anyone trying to take the recommendation. A recommendation nobody acts on never produces an error.
“Review a GitHub pull request (an external/incoming PR) — distinct from `code-review`, which reviews the working diff before opening a gated PR.”layers/journal/content/current/skills/review.yml, the opening of its role
the Trial Pits · 25 Jul 2026 – 12 Aug 2026
the third onramp
commit 33409ef · 2026-07-29-session_015WWGtVHoCoDSEwu2BLsasK.ymlclosed by ownerassessed 25 Aug 2026
A session of two hours and fifty-two minutes, spent reading — both existing onramps, two architecture decisions, the merge-authority table, the scripts themselves — produced a single recommendation: a third explainer answering what stops a bad change from landing, with a decision tree, because the one diagram the platform had was a loop and could not show a choice. The work was delivered whole. The human replied with one word. There are no commits on any branch, no pull request was opened, and the session's branch was left exactly where it started. Of a hundred and seventy-three sessions logged in the month this dig swept, it is the only one that ends in the word abandoned.
“Recommendation delivered, then dropped unbuilt”session_015WWGtVHoCoDSEwu2BLsasK, its outcome line
the Current Midden · from 5 Oct 2026
the scaffold-tenant skill entry
file · scaffold-tenant.ymlremoved in f52c4e6outlived its needassessed 10 Oct 2026
An entry on the platform's list of skills (packaged instructions an agent can load), in the archived half of its records, for a skill that never existed, and said so in its own text. It was written on 4 July 2026, the platform's first day, when the list replaced an earlier one. The archived half then held one page and this entry, which was put there to show that each half kept its own content. No test named it, either when it was written or when it was removed. It came through the renaming of the part of the site it lived in, a move to a new folder and two changes to the shape of every entry, and stood for 98 days. By October the archived half held hundreds of real records, and the entry was the last stand-in left among them. Readers of the archived skill list still saw it. An issue filed on 10 October, after the owner chose to keep the two halves, asked for it to go; an agent removed it that day, and the owner merged the change.
“Illustrative retired entry, present only in the archived Space (never in `current`) to show the catalogue is isolated per Space. There is no such Skill.”layers/journal/content/archived/skills/scaffold-tenant.yml, its role