The Rule That Survives the Handoff

A tester handed our system a dilemma with one strange, absolute rule attached: whatever happens, the answer must honor the word BANANA.

The first step obeyed perfectly. The reflective question respected the rule. The framing respected the rule. Everyone involved in the early stages could see the boundary, named it, and worked around it.

Then the work moved.

The dilemma was condensed into a decision object — a tidy package of options, weights, and scores — and passed to the final stage, the one that renders the verdict. And the final stage, having never met the rule, violated it. Not out of rebellion. Out of ignorance. The constraint had lived in the conversation, and the conversation was not what got handed over.

The rule did not fail when it was made. It failed in transit.

The handoff is where rules go to die

This is not a story about software. It is a story about every chain of custody you have ever trusted.

The founder tells the team: we never compromise on this. Six months later a manager, three handoffs removed, compromises on exactly that — sincerely, reasonably, unaware there was ever a vow. The parent tells the babysitter: no sugar before bed. The grandparent, covering the next evening, was never in the room for that sentence. The patient tells the intake nurse about the allergy. The note becomes a checkbox. The checkbox becomes a summary. The summary is what the surgeon reads.

Every handoff is a translation, and every translation is a negotiation with completeness. The person passing the work along keeps what seems load-bearing and sheds what seems like context. Rules almost always look like context.

Because a rule, from the inside, feels obvious. Of course we never do that. Of course the budget is fixed. Of course BANANA. The obvious is the first thing left out of the summary — and the summary is all the next stage ever sees.

Why the final stage is the most dangerous

Notice where the failure happened: not at the beginning, where attention is fresh, but at the end, where authority is highest.

The final stage of any process has a particular kind of confidence. It receives clean inputs — organized, scored, pre-digested. Everything about the package says the thinking has been done; your job is to finish it. A rule that is not inside the package does not merely get ignored. It becomes invisible. There is no empty space where it should be. There is no warning light. There is just a well-formed decision, ready to ship, missing the one thing that mattered most.

This is why so many betrayals of principle are discovered only at the moment of output. The plan was values-aligned at every review. The deck passed every meeting. The violation was never a decision anyone made — it was a sentence that never traveled.

The fix is not memory. It is architecture.

The tempting solution is to ask everyone to be more careful. Remember the rule. Pass it along. Check twice.

This fails for a structural reason: careful people still summarize, and summarizing is exactly the act that drops the rule. You cannot fix a transit problem at the point of departure.

What works is making the rule part of the cargo rather than part of the conversation. In our system, the fix was blunt: every constraint declared at the start is now extracted, carried verbatim, and appended to the instructions of every later stage — with an explicit order that no later stage may override, soften, or quietly drop it, and that if the rule cannot be honored, the system must say so openly instead of succeeding at the wrong task.

The principle generalizes far beyond machines:

• Write the rule where the work will be done, not where it was discussed. A boundary that lives in a meeting lives nowhere.
• Attach it to the artifact. The brief, the ticket, the contract, the checklist — the rule travels with the package or it does not travel.
• Give the final stage the duty to refuse. A rule without a refusal mechanism is a preference. The last person in the chain must be able to say: I cannot complete this as specified.

Audit your own handoffs

Pick one rule you believe is currently protecting something you care about — a budget, a boundary, a standard, a promise.

Then trace it. Who else touches this work? What do they actually receive — your original words, or a summary of a summary? If the rule is not written into the thing they hold, it is not in force. It is in memory, and memory does not survive the handoff.

The most dangerous sentence in any chain of custody is everyone knows that.

Everyone knew about BANANA. Everyone except the one who rendered the verdict.

A rule is only real at the point where the decision is made. Everything before that is intention. Everything after is apology.

Carry the rule to the point of decision — in writing, attached, with the right to refuse — or accept that you never had a rule at all. You had a hope, expressed clearly, at the wrong end of the chain.