AI Agent
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.
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.
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.
filefunc × Hono — From 60 Lines to 18: Code an Agent Reads in One Pass
I refactored Hono — a production framework with 23k stars — using filefunc. All 4,419 tests passed. Then I measured: the median lines an agent reads to grasp one concept dropped 71%, from 60 to 18. File count isn't the point — read length is.
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.