Deterministic Verification
What Is a 'Turn' in reins?
An anatomy of the turn, the smallest unit of execution in reins. What is not recorded is not a turn — from this one definition, driver independence, restart resilience, and auditability all follow. Compared against the June 2026 Loop Engineering discourse, we see how the turn converts those recommendations into structure.
abloq — A Blog an Agent Operates, a Machine Locks the Verification
Hand a blog to an agent and the articles come out. The problem is you can't trust them — it fabricates sources, bumps the lastmod of an article it never touched, and edits files no one asked it to. If a human has to inspect every line, there was no point delegating. abloq's answer is a division of labor: generation is probabilistic, verification is deterministic. The only thing a human writes is a single insight specification (insight.yaml); authoring, translation, refresh, and evidence work are carried out by agents as quests; and quality is guaranteed by a deterministic gate derived from a single blog.yaml. A locked PASS is irreversible — the agent may be disposable, but progress accumulates.
Why Your Agent Loop Diverges
The more Loop Engineering spreads, the more people hit the same wall — the loop won't converge, it diverges. Infinite spinning, drift, reward hacking: the three faces share one root. You plugged the generator itself back into the loop's judgment slot. And divergence is actually the lucky case. You can see it. What's truly terrifying is the loop that silently fakes convergence. The cure is singular — give the authority to lock 'done' not to the LLM but to a deterministic gate alone.
Production Traffic Is the Spec
Legacy code has no documentation. No tests either. And yet it's running right now. A month of well-recorded logs is the spec — build Hurl integration tests that capture the current behavior from production traffic, and you can pin down what the legacy does and lay a safety net for refactoring without reading a single line of code.
reins — Keep Only the Domain in a Quest CLI; Make the Ratchet a Framework
how-make-quest taught you to build a quest CLI with your bare hands. But build a second CLI and you write the same ratchet, the same scan/next/submit, the same tallying all over again. reins pulls that invariant out into a framework — reins supplies the ratchet, the command skeleton, the tallying, and export; you implement only your domain's gate (the four methods of gate.Definition). The gate is a catalog of cheese-defense rules, and the toulmin defeat graph hands the agent a strategy guide for 'why you lost and what to change to win.'
The Tool That Gave Us the Reins Had No Reins of Its Own — The Boundary Between Harness and Reins
"Reins Engineering — isn't that just harness engineering?" The two don't oppose each other — they're different parts of the same tack. But they are different parts. Even the world's best coding agent put no reins on its own code. That's because reins aren't something you have; they're something you apply.
How to Make a Quest CLI — Build a Tool That Lets the Machine Judge Completion
AI says "Done." In reality, it isn't finished. This article is about building the tool that solves that problem — a quest CLI — with your own hands. From the principle (why) to the cobra command skeleton (how), this single article is enough for an agent to build a Go quest CLI. huma is the worked example.
The Preconditions for Improving LLM Multi-Agent Accuracy
Run several agents and you get more accurate? Only half true. Models trained on the same data fail in the same places. Multi-agent works under two conditions — design for error independence, or, in a verifiable domain, stand up a verifier outside the LLM.
Why Your Agent Never Stops
When someone brags about running their agent 24/7, the feeling it stirs isn't admiration but a question — why isn't it done yet? Code is not a search problem; it's a constraint satisfaction problem. A healthy system is one that can stop.
Who Defines 'Done'? — The Problem Games Solved 40 Years Ago
The moment you define tenant move-out confirmation as five photos, it becomes a game quest. Defining 'done' not as the agent's claim but as a mechanically verifiable condition — games solved this 40 years ago, and it is the right way to get AI agents to actually do their job.
Precedent Is Not Truth — How AI Turns Patches into Authority
AI reads the structure of code but cannot read whether that structure is a decision or a patch. So the more it copies, the more a flaw accumulates false authority. What broke the loop was not a bigger model — it was a single line of doubt from a human.
Building Agent-Operable Systems
60–80% of Fortune 500 IT budgets go to guarding locked legacy. Because they can't open it. The real meaning of the AI bubble is not smarter models — it is that locked corporate memory is becoming reachable.
Agent Operable Codebase
Is code that is easy for humans to read the same as code that is easy for agents to work with? It is not. When a file has 20 functions, agent performance drops by 30-85%. The office must be turned into a factory.
Class 5. AI with Reins — Introduction to Reins Engineering
Harness engineering is a fence. Reins Engineering is a bridle. Don't change the model — add contracts.
Reins Engineering — AI with Reins
Harness engineering is a fence. It keeps the agent from going outside, but doesn't ensure it reaches the destination. Reins Engineering is the reins — steer with deterministic contracts, lock with ratchets, separate decisions from implementation.
Hurl Stops Vibe Coding Drift
Vibe coding collapses under logic drift within 3 months. CMU, METR, DORA, and Amazon cases prove it. Declare API contracts in plain text with Hurl and lock them with a ratchet -- you suppress drift structurally without limiting AI's freedom.
Ratchet Code That Exploits IFEval
LLM sycophancy bias is not a bug but an asset. Combine the instruction-following ability that IFEval measures with deterministic feedback, and even a 4.5B local model produces a convergence loop that generates correct code.
AI Sycophancy Bias Is a Business Feature
Sycophancy bias in LLMs is not a bug. It is a mathematical inevitability of RLHF and a commercial feature that big tech has no incentive to fix. This is why LLM-as-Judge is structurally impossible.
Why Coding Agents Work and Why They Break
The same model hallucinates in web chat but ships a 200-line feature in a coding agent. Not because the model changed — because the topology changed. Generation can be probabilistic. Verification must be deterministic.