Exception Basket

Define ordinary bounds and route everything outside them to a visible human review queue.

Your family's shared calendar mostly runs itself. Practice pickups shift, dentist appointments move, and nobody needs a meeting about it. Then one Tuesday your co-parent quietly rebooks a weekend that touches the custody schedule, the change sails through like any other, and you find out standing in an empty driveway. The routine path worked fine. The edge case is what burned you.

An exception basket means you define what counts as ordinary and route everything outside those bounds to a visible human review. The cue is a stable normal path with edge cases that are varied or consequential. Set it up in three steps: write down the ordinary bounds (routine schedule shifts proceed automatically), name the exceptions that must get flagged (anything touching custody, health, or a major commitment), and create the visible queue, even if that is just a rule that flagged changes require a conversation before they take effect. When it works, routine changes flow without friction and the dangerous ones reliably surface. Two tuning rules: lower the threshold as stakes rise, and track both misses and pointless escalations, because a basket that flags everything gets ignored and one that flags nothing is decoration.