The Handoff Line
Some work has become safe to hand off, to a tool or a pattern or a person new to your domain, and some has not, and the line between them moves without announcing itself. The failure is almost never the act of handing off. It is not noticing when a handoff has stopped being safe.
Framework 3 of 10 · Chapter 3: The Gap
Handing work off is not the risk. Most handoffs are correct, and the ones that are correct stay correct for a long time, which is exactly what makes the failure hard to see.
The line moves. A category of work that was safe to delegate last quarter runs into the part of your system that is not standard, and nothing about the moment looks different. It looks like progress right until it does not. Nobody announces it. There is no alert for a handoff that has quietly stopped being safe.
When it applies
Whenever a standard answer is about to be applied to a system with history. New tooling on old infrastructure, a common pattern on an uncommon domain, a competent engineer new to your specifics, an agent working from public convention.
How to run it
Ask one question: what would the receiver have to already know for the standard answer to be wrong here?
- If you cannot name anything, the handoff is probably safe. Proceed.
- If you can name it, you have two jobs. Do that specific review by hand, and write the thing down at the seam where the work happens.
The seam matters more than the writing. A note in a document nobody opens does not move the line. A note in the code, the fixture, or the ticket does, because it is where the next receiver, human or otherwise, is already looking.
Where it fails
Audited once. The line is not a property of your system, it is a property of your system this quarter. It needs revisiting when tooling changes, not when something breaks.
Written in the wrong place. Knowledge that lives in a wiki page is knowledge that has been archived, not transferred.
Stated as a rule rather than a reason. "Do not use this pattern here" ages badly. The reason it does not fit here survives the next three tool changes.
Practice
Find one handoff you made this month and put the missing note where the work lives. One sentence about your system's specifics that the standard pattern does not know.