ARGH https://validator.w3.org/feed/docs/rss2.html Harness Atlas Patterns ARGH Projects Checkpoint Mcp The skill file was correct. The runtime skill was not. Project Trajectories Dossiers The second fix found the boundary the first fix missed The hook prevented stopping — then started deciding what the agent was allowed to do A cosmetic schema change silently removed a routing capability Private subagent messages improved confidentiality and weakened auditability The control existed on disk and missed the runtime entirely Remote tool synchronization created a second control plane A workaround for missing skill discovery became another fragile dependency The runtime changed before the documentation knew it had changed A guardrail became a sensor for a regression the product did not measure The permission system asked for approval — for the wrong thing The conversation rewound. The filesystem did not. The filesystem said one thing. The model saw another skill set. A branch name looked like the future until its divergence showed it was a fossil Hooks evolved from observers into policy enforcement Different failures kept collapsing into the same false success The health check was green because it was checking the wrong identity A project died strategically while hundreds of issues still looked alive The source was fixed. The installed control stayed stale. Resume restored the conversation but not enough execution state Hooks became a dedicated runtime control layer rather than a scripting afterthought Hook execution became part of observable agent state Trust became a shared boundary for hooks, tools and instruction files Skills became numerous enough to need a context budget The project’s center of gravity moved from product features toward agent protocol architecture A skills methodology started spreading across harness boundaries A common protocol did not create a common security model Skills stopped being prompt files and started becoming runtime packages Hooks are becoming the enforcement bus of agent systems Delegation became its own control plane Conversation recovery is separating from execution recovery Merged, released, installed and observed-fixed kept turning out to be different states The system built to explain the agent became the resource failure Unavailable data was flattened into ‘nothing found’ The agent finished the work and still failed the user The agent remembered the past and forgot what it still owed The test was green because it never crossed the seam users depended on A safety outage risked becoming permission Parallel agents are forcing workspace isolation into the harness Instruction files are becoming a cross-harness compatibility surface The harness is becoming the product Codex