<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reins on Architect PARK JUN WOO</title><link>https://www.parkjunwoo.com/tags/reins/</link><description>Recent content in Reins on Architect PARK JUN WOO</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 05 Jun 2026 20:00:00 +0900</lastBuildDate><atom:link href="https://www.parkjunwoo.com/tags/reins/index.xml" rel="self" type="application/rss+xml"/><item><title>reins — Keep Only the Domain in a Quest CLI; Make the Ratchet a Framework</title><link>https://www.parkjunwoo.com/tech/reins/</link><pubDate>Fri, 05 Jun 2026 20:00:00 +0900</pubDate><guid>https://www.parkjunwoo.com/tech/reins/</guid><description>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&amp;rsquo;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 &amp;lsquo;why you lost and what to change to win.&amp;rsquo;</description></item></channel></rss>