92 posts on engineering, architecture, and technical craft.
AI can generate plans and status that look complete while the goal is unmet. ADD makes evidence-backed exit criteria the contract, the dynamic goal-loop the engine, and an artifact — not a self-reported 'green' — the proof a milestone is actually done.
12 min readAI can flood prospects with personalized-looking outreach that is off-ICP, mis-priced, or non-compliant. ADD clamps the what — ICP, claims, pricing authority — and frees the how, then verifies by reply and win rates instead of by how persuasive the copy reads.
13 min readA field study of ai-proxy, a multi-tenant AI gateway built end-to-end with ADD: 23 milestones, ~120 tasks, six days, zero waivers. What the method felt like in production and how the LLM behaved when scope was clamped.
12 min readThe frozen contract is ADD's one human gate — the interface, data shapes, and error codes, locked and checksummed before the agent builds. Why it is the single approval that earns the agent its autonomy.
12 min readThe step that closes the loop: Observe production behavior and fold the spec delta back into the next Specify. How ADD keeps documents living while old-school artifacts rot — and how the method improves itself.
11 min readWhere ADD sits among its neighbors: the lineage it inherits from TDD, DDD, BDD, and contract-first design, and how it differs from spec-kit and GSD by continuing past Verify to Observe and folding the loop closed.
13 min readADD's first two steps kill fast waste before a line of code exists: Specify (Must do, must Reject with error codes, the After-state) and Scenarios (concrete happy, edge, and failure examples in domain language). Pin the what.
11 min readTests-first, pointed at an AI agent: write a red suite that asserts observable behavior, then turn the agent loose with one instruction — make every test pass, change nothing in the tests or the contract. Red to green.
11 min readVerify by evidence, not by reading the diff. ADD's earned-green: an adversarial refute-read that tries to break the result, because AI code is frequently plausible and wrong. Trust through proof.
13 min readAI made writing code nearly free and quietly broke the SDLC. AI-Driven Development — five competencies, eight steps — constrains what an agent builds while freeing how it builds, proven across a 23-milestone production gateway shipped in six days.
26 min read