Skip to content

Terminal-Sink Handoff

Handoff protocol — instantiates Mobile-Defect Reconfiguration

Delivers the mobile defect into a designated sink that absorbs it for good — the controlled place where the accumulated mismatch is retired instead of being left loose in the live system.

A mobile defect has to end somewhere. If it simply halts in place, the mismatch it carries is stranded in the working structure. The Terminal-Sink Handoff is the protocol that routes the defect to a designated sink — an absorber built to receive it — where its motion terminates and the mismatch is consumed or parked harmlessly. Its defining idea is that the endpoint is engineered, not incidental: the defect is handed off into something that can safely absorb it, and arrival at that sink is by design the arrest condition. This is the archetype's core move made literal — the flaw is not eliminated but relocated to a benign location and held there. The truest anchor is gettering in semiconductor fabrication, where impurities are deliberately driven to a sink away from the active region rather than removed atom by atom.

Example

A chip fab has mobile metal impurities — iron atoms, say — diffusing through silicon wafers; left in the device layer they destroy transistors. Rather than chase every atom out, the process uses gettering: it engineers a sink — a damaged, heavily-doped region at the wafer backside — and, during a thermal step, drives the impurities there. The Terminal-Sink Handoff is that final delivery. The mobile defect is routed to the gettering site, captured, and immobilised where it cannot reach the transistors; arrival at the sink is the condition under which its motion stops. The flaw was never eliminated — it was moved to a harmless location and pinned there, which is exactly enough.

How it works

  • Provision the sink. Stand up an absorber sized and shaped for the defect — a gettering layer, a dead-letter queue, a decommission bin.
  • Route to it. Steer the defect's path so it terminates at the sink rather than at some arbitrary spot.
  • Hand off and arrest. The sink captures the defect and its motion stops; the arrival is, by design, the terminal arrest condition.
  • Absorb or quarantine. The sink consumes the mismatch or parks it out of harm's way — the defect is not left loose in the live structure.

It governs the end of the journey, distinct from the mid-transit handoffs a defect makes between neighbours along the way.

Tuning parameters

  • Sink capacity — how much the absorber holds before saturating. Too small and it overflows back into the system.
  • Sink location — how far the defect must travel to reach a benign spot. Nearer is cheaper but may not be harmless enough.
  • Capture strength — how firmly the sink holds what it takes. Weak capture lets an absorbed defect re-emerge later.
  • Absorb vs. quarantine — whether the sink destroys the mismatch or merely parks it out of harm's way (retire vs. hold).
  • Drain policy — whether the sink is ever emptied and processed, or is a permanent resting place.

When it helps, and when it misleads

Its strength is giving the reconfiguration a clean ending: the accumulated mismatch has a designated, harmless destination instead of being stranded in the live structure — the archetype's relocate-don't-eliminate move, realised. It misleads when the sink becomes a graveyard: an unmonitored dead-letter queue nobody drains, or a gettering site that saturates and quietly re-releases what it held.[1] Because the defects were routed out of sight, the "handled" mismatch can accumulate unseen until the sink overflows — worse than never having moved it, because everyone believed it was resolved. The discipline is that the sink itself must be bounded and monitored: track its capacity, review or drain its contents, and never let "absorbed" silently become "hidden."

How it implements the components

  • terminal_sink_or_absorber — the engineered endpoint that receives and holds or consumes the defect.
  • arrest_condition — arrival at the sink is, by design, the condition under which the defect's motion terminates.

It handles the *planned terminal stop only; an unplanned mid-transit halt-and-hold belongs to Arrest-and-Hold Protocol. It does not reconcile the trail left behind the front (residual_state_reconciliation — Behind-Front Stabilization Pass) or provide the undo path (rollback_or_counter_defect_path — Counter-Defect Rollback Runbook).*

Notes

Distinguish two senses of "stop." This mechanism owns the terminal arrest — the defect reaches the sink it was always headed for and is absorbed. Arrest-and-Hold Protocol owns the emergency stop — freezing the defect wherever it happens to be when something goes wrong, without absorbing it. A sink handoff is a planned destination; an arrest-and-hold is an unplanned pause, and the two should not be conflated.

References

[1] The dead-letter queue is the software instance of a terminal sink: messages that cannot be processed are routed to a holding queue rather than lost. Its well-known hazard is going unmonitored — a queue nobody drains becomes a silent graveyard — which is why a sink must be bounded and watched. ↩