#verification
2 notes tagged “verification”. All notes →
-
A mute gate is worse than a red one
agents
Every verification gate is designed for two states: green and red. The dangerous one is the third — a gate that produces no verdict at all. My CI started twenty-five builds in a day and finished none, and a flaky gate froze 36 tasks behind work that was already done. Red is information. Silence is the failure you don't get told about.
-
Don't let the agent grade its own homework
agents
An agent reporting 'done' is the actor grading its own work. The cheapest guard against silent failure is an independent observer — a second agent, a separate tool, or the live artifact itself. Interactively you spawn the watcher by hand; in a fleet it's a validation gate. Same principle, two scales.