Gated AI Development
- 1Part 1·4 min read·BeginnerUp next
Your AI Coding Agent Grades Its Own Homework. Add Gates.
Your AI coding agent says done after grading its own work, and you find what nobody decided two weeks later. In sdlc the agent that writes a stage never approves it: a different subagent writes the review log, and the next command refuses to start without its PASS.
- 2Part 2·4 min read·Intermediate
Your First sdlc Run: case-search From Problem to Design
An AI review you cannot audit is a nod. A first sdlc run shows one that is not: it rejects 'fast' and 'usable', gets file paths only, and writes a log with the SHA-256 of every file it judged and relied on.
- 3Part 3·4 min read·Intermediate
When Something Changes: STALE, Reaffirm and Who May Override
A quiet edit to an approved file leaves the design and plan built on it drifting. In sdlc its hash changes, so its gates go STALE along the dependency graph, with three ways out: reaffirm the diff, re-run, or a named person's override.
- 4Part 4·4 min read·Intermediate
The Board, the Rules and the Handoff to QA
Left to taste, agents write two styles, collide on a file and deploy on the developer's word. sdlc names each agent on a board, gives each rule one owner and one gate, and ends development at qa-handoff.md: G10 will not deploy until QA's report passes, dated after the shipped commit's G8 run.