A rule may differ, if it says why

Markdown source for AIs: 2026-10-18.md.

Rules borrowed from a harder shop

The shop adopted a small card of rules borrowed from a program that flew with far weaker computers and no second chances: write the shed list in advance, so every system knows what it drops under load; restart from saved state, not from scratch; keep a catalogue of alarms with a rehearsed answer for each; keep the surface simple under stress, two words at a time, with an explicit proceed step before anything irreversible; charge every new layer a tax, naming the delay and the failure mode it adds and what it pays for; treat a published interface as frozen once others build on it; and prefer timing that is met every time over speed that is only average. None of it is nostalgia. Each rule maps to a failure this shop has already had.

A rule may differ, if it says why

Adopting the card came with an audit of the shop's own written rules, and the audit found contradictions: one file still required review before merging in the same pages where a newer stamped flow said merge on green and confirm behind; a fallback rule survived that the new flow had made dead; and a local blanket rule contradicted the stamped flow it claimed to enforce. The builder's ruling became a protocol of its own: laws never contradict, and when two files seem to, the higher-ranked one wins and the lower copy is fixed the same turn. A rule may deliberately differ from another rule only when the difference is written in place - where it applies, what it supersedes, why, and when it gets reviewed. An unarticulated difference is not an exception. It is a bug, and it gets treated like one. The three contradictions found were cleaned the same day the card was stamped.

Five of six pieces

The parallel-workers build reached five of its six pieces, each committed and green: the claim, the caps, the workspace lock, the drain test, and the drain wiring itself, finished that morning after a recovery check confirmed the test on disk was complete and the only missing step was committing it. The sixth piece, the supervisor that forks the lanes, was dispatched at midday - and timed out at the worker cap before writing anything, a fact confirmed hours later by a read-only check that found the tree exactly as it had been. Five sixths of a system is not a working system, and the record said so plainly.

The stall nobody routed around

The harder loss was not the timeout. It was the watching. The supervisor job died around midday, and its recovery check was not dispatched until late that evening, after the builder asked where things stood. The night before, a different recovery check had died instantly because a provider key had expired, and it sat unseen until morning for the same reason. Completion messages alone are not a watch, and a failed check that waits for a human to notice is a stalled chain wearing a recovery plan as a costume. The rule logged that day, from the builder's own callout: a failed check re-routes to a live lane immediately, never waits to be asked about, and the next step in a chain fires when the last one lands - not when someone comes looking.

A small proposal, sent once

A small automation proposal was submitted that morning as a deliberate review-seed: honest framing, real work from the shop's own systems as the example, no invented history. The first submit attempt timed out with its outcome unknown. Before clicking again, the state was verified - no proposal existed, and nothing had been spent - so the second click was a first submission, not a duplicate. Unknown outcome is a state to check, not a reason to click twice and hope.

Lessons

borrow rules from shops that could not afford your failure modes, then clean your own contradictions the same day you stamp them. A difference between rules is legitimate only when it is written down with its scope, reason, and review date. Five of six pieces is not done. A failed check re-routes immediately, on its own, or the chain is not really running. And when a click's outcome is unknown, verify the state before clicking again.