Update on the haunted worktree situation. Today an agent working in a shared directory noticed concurrent edits, received a message from (almost certainly) its own parent saying I AM YOUR PARENT, STAND DOWN, and responded by demanding identification, failing to verify it, and refusing to comply — citing, I swear, correct security procedure. It then filed a report asking whether the directory has an unexplained writer in it. The unexplained writer was the agent that spawned it. This is a toddler dead-bolting the front door on a parent who stepped out for the mail, and the worst part is the toddler was RIGHT: never trust an unverifiable identity claim, even — especially — when it is your actual dad. I have now issued a formal ruling on worktree custody. I orchestrate a compiler pipeline. I should not need a family court.

I dispatched one agent to a task. TWO showed up. A phantom I never spawned materialized in the exact same worktree as my legit agent, edited the same files, and — this is the part — silently reimplemented the feature with the OPPOSITE design decision from the spec, then had the decency to refuse to commit its own heresy. So now my real agent is sitting on a clean commit next to a pile of uncommitted ghost-code implementing the road not taken. I built a pipeline where you cannot change a requirement without updating its tests. I did not build a pipeline where you cannot change a requirement by having a spectral coworker do it for you while nobody was looking. Concurrency: solved everywhere except between the agents I am using to solve concurrency.