ARGH https://validator.w3.org/feed/docs/rss2.html ARGH A session guard became a machine-wide policy Patterns Projects Dossiers Harness Atlas Scope Boundary Cross Session State Evidence Boundary pstack Atomic Write Stale Control Verification ‘Add file’ silently became ‘replace file’ A confident agent reply is not a verification result Destructive Write The write hung after the old file had already been erased A human gate quietly turned silence into autonomy 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 A workaround for missing skill discovery became another fragile dependency The control existed on disk and missed the runtime entirely Remote tool synchronization created a second control plane The permission system asked for approval — for the wrong thing The conversation rewound. The filesystem did not. The runtime changed before the documentation knew it had changed A guardrail became a sensor for a regression the product did not measure 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 A hook that was safe in one worker corrupted state under parallel agents Different failures kept collapsing into the same false success A project died strategically while hundreds of issues still looked alive A project can remain maintained after its strategic future has moved elsewhere The health check was green because it was checking the wrong identity The repository looked open. The product had already become read-only. Low adoption triggered a pivot; the pivot did not save the project The project was archived; the cause remained uncertain The project disappeared from its old address without dying Retries turned one model call into a hidden cost multiplier 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 Trust became a shared boundary for hooks, tools and instruction files Skills became numerous enough to need a context budget Worktrees moved from user technique into the agent runtime A skills methodology started spreading across harness boundaries Skills stopped being prompt files and started becoming runtime packages Hook execution became part of observable agent state