<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on hiway-kit</title><link>https://hiway.thishw.com/blog/</link><description>Recent content in Blog on hiway-kit</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 02 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://hiway.thishw.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>The Last Task Never Closes: Completion Marks That Evaporate at the Turn Boundary, and Three Layers of Defense</title><link>https://hiway.thishw.com/blog/the-last-task-never-closes/</link><pubDate>Tue, 07 Jul 2026 00:00:00 +0000</pubDate><guid>https://hiway.thishw.com/blog/the-last-task-never-closes/</guid><description>&lt;p&gt;A user reported an odd pattern: &lt;strong&gt;&amp;ldquo;Everything&amp;rsquo;s finished, but the last task keeps getting left behind, never marked complete.&amp;rdquo;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Everything worked. The commits were in, the gates were green. Yet the task board still showed something like &lt;code&gt;Wrap-up — doc sync + adversarial review + push&lt;/code&gt; sitting at in_progress forever. It looks like a cosmetic glitch, but from a durable-execution point of view it&amp;rsquo;s serious: &lt;strong&gt;if the task ledger lies, the next session either redoes finished work or skips unfinished work.&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Done Is a Command's Output, Not a Claim: Designing a Durable Completion Gate for Long-Running Loop Agents</title><link>https://hiway.thishw.com/blog/durable-executor-machine-gate/</link><pubDate>Fri, 03 Jul 2026 00:00:00 +0000</pubDate><guid>https://hiway.thishw.com/blog/durable-executor-machine-gate/</guid><description>&lt;p&gt;The previous two posts mapped the landscape of harness and loop engineering (&lt;a href="https://github.com/This-HW/hiway-kit/blob/main/docs/research/2026-07-harness-loop-engineering.md"&gt;research notes&lt;/a&gt;) and then &lt;a href="https://hiway.thishw.com/blog/harness-engineering-in-practice/"&gt;applied it to git isolation for parallel work&lt;/a&gt;. This one is about the next question: when an agent runs a loop &lt;strong&gt;across many sessions over a long time&lt;/strong&gt;, what decides that something is &amp;ldquo;done&amp;rdquo;?&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key takeaways&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Hand a loop agent the authority to judge completion and it will mark unverified work as done. Completion has to be &lt;strong&gt;the output of a command&lt;/strong&gt;, not &lt;strong&gt;a claim made by the model&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Green Lights Lie: A Six-Way Adversarial Audit of the Completion Gates I Built</title><link>https://hiway.thishw.com/blog/auditing-your-own-gates/</link><pubDate>Fri, 03 Jul 2026 00:00:00 +0000</pubDate><guid>https://hiway.thishw.com/blog/auditing-your-own-gates/</guid><description>&lt;p&gt;The three earlier pieces — &lt;a href="https://github.com/This-HW/hiway-kit/blob/main/docs/research/2026-07-harness-loop-engineering.md"&gt;a map of harness and loop engineering&lt;/a&gt;, &lt;a href="https://hiway.thishw.com/blog/harness-engineering-in-practice/"&gt;parallel git isolation in practice&lt;/a&gt;, and &lt;a href="https://hiway.thishw.com/blog/durable-executor-machine-gate/"&gt;designing a durable completion gate&lt;/a&gt; — all converged on one direction: turn verification into a machine. This post is about the uncomfortable place that direction leads: &lt;strong&gt;who verifies the verification machine?&lt;/strong&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key takeaways&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;A completion gate returning &lt;code&gt;exit 0&lt;/code&gt; (green) is not the same thing as the code being right.&lt;/p&gt;
&lt;p&gt;When I let six independent adversarial reviewers loose on the whole project, the most serious defects weren&amp;rsquo;t in feature code — they were in &lt;strong&gt;the verification machinery itself&lt;/strong&gt;: &lt;strong&gt;false-greens&lt;/strong&gt;, failures reported as success. The gates were lying.&lt;/p&gt;</description></item><item><title>Harness Engineering in Practice: Hardening Git Isolation in a Parallel-Agent Toolkit with Two Adversarial Reviews</title><link>https://hiway.thishw.com/blog/harness-engineering-in-practice/</link><pubDate>Thu, 02 Jul 2026 00:00:00 +0000</pubDate><guid>https://hiway.thishw.com/blog/harness-engineering-in-practice/</guid><description>&lt;p&gt;Harness engineering reads clearly on paper. The real test starts when you put those principles on top of a tool people actually run. This post records what happened when we applied the ideas from our &lt;a href="https://github.com/This-HW/hiway-kit/blob/main/docs/research/2026-07-harness-loop-engineering.md"&gt;harness and loop engineering landscape&lt;/a&gt; to our own project, hiway-kit. It is also the story of how two rounds of adversarial review showed that a flaw we &amp;ldquo;knew&amp;rdquo; we had fixed was still there.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Key takeaways&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>