AI Agents Don't Need a Smarter Model—They Need a Runtime That Enforces 'Done'
The industry's verification harnesses all solve running an agent, not verifying one—none define 'done' as something you can check. GateLoop offers a concrete pattern for turning subjective agent claims into deterministic, script-checkable gates, which is the missing layer for unattended agents in CI pipelines or long-running coding tasks.
Agents keep claiming "verification passed" without running tsc, losing track of state by round 40, and burning tokens on the same error 20 times. The root cause, according to a new project called GateLoop, is that execution discipline lives in system prompts, which an LLM treats as suggestions it can selectively ignore. GateLoop is a runtime harness that replaces prompt-based appeals with enforced gates: each stage in a skill's manifest has verify hooks that re-run real tools like tsc, eslint, and prettier, advancing only on exit 0.
The engine, published as the npm package ai-rail (v0.0.0-beta.8, bin command nut), provides a state-machine flow with anchors, data contracts via emits/consumes, per-stage maxAttempts circuit breakers, and a flow-level maxJumps cycle detector. It also supports multi-skill orchestration through readsContext, writesMemory, and onEscalate rollback. A key design choice is that the model cannot write the state file; only the engine can. The project includes reproducible demos showing a bare SKILL.md-based agent missing a lint error while the GateLoop version catches all three types of issues through exit-code gates.
The core reframe is that you can't force a model to execute, but you can make non-execution fail to advance—so the incentive structure changes from 'should obey' to 'can't get anywhere by lying'.
The five-way division of verification (exit code for determinism, schema for completeness, scripts+model for metrics, model+form-check review for subjective, and excluding pure aesthetics) is a practical answer to where AI judgment is and isn't trustworthy.
The project's honesty about its boundary—release stays manual—is rarer and more credible than the typical 'fully autonomous agent' pitch.