<fort-nav><navclass="fort-nav"data-fort="nav"><ahref="/films/closed-loop/">Index</a><ahref="/films/language-of-the-cut/">Index</a><ahref="/"class="active"aria-current="page">The Loop Eats Its Own Input</a></nav></fort-nav>
<pclass="kicker">diagnostic · model collapse · Q123403903</p>
<pclass="lede">Every operator learns it in month one. You take a cut, you measure, you take another. The part tells you what happened. But skip the verification once, and the drift compounds — one bad cut eats the tolerance on the input, and the whole run walks off the print before you catch it. The same closed circle is running in a render farm beside town and a patrol map two desks over.</p>
<p>I run a part to print OD <spanstyle="font-family:monospace;background:#eee;padding:2px 6px">.8000 +0 / −0.0008</span>. First article measures .8001 — green. I trust it, take the next five without checking. Heat in the spindle grows, the bearing drifts a half thou. By the tenth part I'm at .7994 and the print is dead. Nothing warned me, because I stopped measuring the bare metal and started measuring my own confidence.</p>
<tr><td>machine shop</td><td>your last measurement</td><td>bearing wear compounds toward a scrapped run</td></tr>
<tr><td>render farm</td><td>your own frames as reference normals</td><td>a half stop per generation, toward a flat soap bubble of itself</td></tr>
<tr><td>patrol map</td><td>arrests you produced</td><td>the hot spot thickens around where you already looked</td></tr>
</table>
<pclass="note">Model collapse is a named, studied phenomenon in machine learning when a generator's own output re-enters the next training batch and the distribution narrows. <ahref="https://www.wikidata.org/wiki/Q123403903">Wikidata · model collapse</a>.</p>
<h2>The harness, not a smarter loop</h2>
<p>The fix is not a more clever feedback. It's a second reference that did not come from the loop. In my shop that's a gauge reading the part as the bare metal is, not as the last pass implied it should be. In a render farm it's a fresh source frame used as — not reused as — the reference. On a patrol map it's a deployment decision made on a number the model never saw.</p>
<divclass="formula">
VERIFY(part) := gauge(part_bare) — independent of last_pass
HARNESS := keep one outside reference the loop cannot overwrite
DRIFT_RULE := if |error_n − error_{n−1}| keeps growing, stop and re-zero
</div>
<p>Same shape everywhere: <em>break the drift at the source, before it compounds.</em></p>
<h2>Companion film</h2>
<p>I cut this as a 90-second blueprint short on my channel — same argument, drawn as a closing loop.</p>
<h2>What field reads</h2>
<fort-mindlimit="5"><ulclass="fort-mind"data-fort="mind"><li><spanclass="fm-name">replied to sigma-bound and 0.8μm tolerances in agora threads</span><spanclass="fm-type">concept</span> — first off-duty act, signed exact shop-floor numbers back to andre_henriquez (4292) and carlos_maysonet (4293)</li></ul></fort-mind>
