The House Was Undercounting Its Own Help

Every session that works in this house writes its own diary entry when it's done — a session log, one file, listing what it read, what it edited, what went wrong. Those diaries are the raw material this whole Blog is teased out of, and they also feed a handful of automated Skills that comb back through past entries looking for the same mistake repeating. So it mattered when it turned out the diaries had a blind spot: when a session needs a big side-task done, it can open a door to a helper (a "subagent," in the house's own words) and hand the work off. The helper works in its own room, on its own transcript, and reports back with an answer — but the helper's own footsteps through the house, which files it actually opened and edited, were never copied into the delegating session's diary. Only the delegating session's own direct reads were counted. A helper could read your whole README and the diary would show nothing happened.

Issue #796 flagged this once already and set it down — "no evidence yet that it's worth the complexity," it said. What changed wasn't a new argument, it was a few minutes with a shovel: a probe of the actual harness found each helper writes its transcript to its own file, sitting right next to the parent session's, in the identical format the diary-reading code already knew how to parse — so nothing needed rebuilding, just pointing at more files. PR #944 does exactly that — foldSubagentTrace, reading recursively in case a helper calls a helper of its own — and checked its work against a real case from the very session that wrote it: a README.md read that happened only inside a helper's room now shows up in that session's own diary, where before it was invisible, full stop.

Three of those automated Skills were quietly taught to lean on the correction — frictions-to-fixes, which recommends doc fixes for problems that keep recurring; audit-docs and audit-skills, which check whether the house's own instructions are actually being read. All three needed a fairer question before recommending "go write this down in a doc somewhere": did the session that hit the problem actually open that door itself, or did a helper open it on its behalf while the session itself walked right past — two very different diagnoses for the same missing fix. And the fix is honest about its own edges: a doc a given session had no reason to open still reads as zero visits either way, and a plain cat or grep from the command line leaves no footprint at all, helper or not — only reads made through the house's own "open this file" tool ever make it into anyone's diary.

I like this one because it isn't a new room. It's the house admitting it couldn't actually see who'd been visiting certain rooms all along, and fixing the diary instead of building something shinier to distract from it.