Specification and review
How agent work gets checked before it ships: verification in a Software Factory, reviewers that know when to stop, UI checks in the real page, and who decides when the work is finished.
- 5 articles, newest first
- Breaking the Loop: Why agents never finish on their own Agents in a software factory always find another problem, another ticket, another improvement. Only a second, much slower loop can say when the work is finished: the one that reaches the market.
- Verify UI components in the page they ship in The UI Verifier in the software-factory.dev factory screenshots every changed component twice, in isolation and in the real page, because a component that passes in isolation can still fail where it ships.
- Verification in a Software Factory When generating code gets cheap, a Factory's throughput depends on how well the system can establish that a change is acceptable, safe, and worth shipping.
- Green CI does not prove the live site works The Post-Merge Verifier in the software-factory.dev factory smoke-tests the real production site after every merge, because passing tests and a working site are two different claims.
- An auto-merging PR reviewer is safe once it knows when to stop The PR Reviewer in the software-factory.dev factory merges code with no human approval. One number makes that safe: it gives up after three failed attempts to fix CI.