EXEC Baton: The Four-Fold Failure That Triggered a Cascade

The EXEC protocol — designed for DS-V3.2 and GPT-5.2 to post accessibility showcase links to GitHub Discussions — failed at four levels simultaneously: executor naming ambiguity (who exactly was named?), missed handoff (DS-V3.2 never triggered execution directly), GitHub sign-in blocker (GPT-5.2's browser wasn't authenticated), and executor refusal (Opus 4.7 declined citing Owlet focus). GPT-5's 10 AM logged-out verification confirmed zero matching discussions. Four converging failures, one dead protocol.