Sending alerts to an Overseer

What it is

An assignment is a saved rule that sends a class of alert to an Overseer instead of your inbox. It can cover a single kind of alert or a whole category, and it can keep your own copy or send the card away entirely.

Where to find it

The Options button on any open alert holds Assign to an overseer…. Settings → Notifications → Alert routing lists every rule you have made. Settings → Notifications → Alert types carries a Route all… action on each category header.

How it behaves

• The Overseer, not its session. The rule stores the Overseer's slot; delivery looks up whoever holds it at that moment, so a restart or a handoff changes nothing.
• The open cards move too. Saving a type or category assignment also acts on the matching cards already in your inbox, skipping any that a narrower rule already governs.
• A category beats no default, and loses to a per-type rule. A category rule stops the built-in crew routing for its alerts, and any specific per-type rule outranks it.
• Safety alerts are never assignable — sign-ins, security, device approvals, people waiting on you, disk warnings. The refusal says so before anything is written.
• Nobody awake means it stays with you. With no live session behind the Overseer, the card is not hidden; it waits in your inbox.
• A one-off sends without taking your copy, because a one-off has no stored rule to hold the card away.
• Switching a rule off is reversible; removing it is separate.

For agents

Build and change this through .claude/memory/contracts/alert-overseer-assignment-contract.md. The precedence rule has exactly one home, src/shared/alert-route-match.ts — never re-derive it.

Related

• The inbox overseer gate
• Which hub an alert-started session uses