S.MISCAST.I — Interface failure

Every part works fine on its own, but meaning, ownership, or quality dies in the gaps between them.

You and your co-parent are both competent. The kid is fed, loved, on time. Yet every Sunday exchange, something drops: the antibiotic schedule, the field trip form, the fact that she barely slept. Each household runs fine. The damage happens in the 90 seconds at the door, where context is supposed to transfer and does not.

Interface failure is the diagnosis for exactly this shape: every part works on its own, but meaning, ownership, provenance, or quality dies in the gaps between parts. The cue is repeated surprise after a transfer, or two capable people producing a bad joint result. To use it, walk the chain and ask one question at each handoff point: where exactly does context, ownership, or quality disappear? Name that seam, not the people on either side of it. What changes when the diagnosis lands is your target: instead of asking anyone to try harder, you redesign the transfer itself, usually with an explicit handoff that states current state, next need, and owner. Do not apply this label when one component is genuinely failing at its own job; fixing the seam around a broken part just wraps the problem in better packaging.