ADD 3.0.0 — Direction · Build · Verify

ADD 3.0 is a method for building software with AI agents without losing track of what's true — and this release's whole design fits in one sentence: rules written as prose get routed around; rules enforced by the engine hold.

The engine is a NO-EXEC notary over plain markdown in .add/: you approve a direction once (the freeze, cryptographically sealed), the agent builds to green, a receipt records a real test run (exit code, passing test IDs, content hashes of every in-scope file), and a gate refuses a PASS that is unbriefed, unbound, stale, tampered-with, or security-sensitive without a human on record.

Measured, on the record (n=3, single-engine campaign, committed in-repo): 5 of 7 planted ambiguities handled safely in every rep, requirement coverage 1.0, regressions 0, $3.00 mean per run — and the two stable misses are published too. The claim is auditability, not correctness.

📖 Launch post: https://pilotspace.github.io/ADD/announcements/introducing-add-30/
🧾 The adversarial audit (we tried to cheat it): https://pilotspace.github.io/ADD/announcements/2026-08-11-we-tried-to-cheat-our-own-dev-method/

Try it in ten minutes

npx @pilotspace/add init        # or: pip install pilotspace-add && pilotspace-add init

Then open Claude Code, type /add, and describe a feature. Coming from 2.x: add upgrade archives your old bundle whole — nothing deleted.

Full changelog: add-method/CHANGELOG.md