Inbox

Everything waiting on a person. The sidebar shows a count for managers.

• Open questions: when an engineer's confidence in its next move is below the threshold, or it keeps failing and needs help, it stops and asks. Each shows the engineer, its confidence and the question. Owners and admins answer with Answer & resume, and the engineer carries on with that context. Members see "An owner or admin can answer this to resume the engineer." (In Slack, anyone who's a member can answer by replying in the thread.)
• Confidence threshold (managers): below this self-rated confidence, engineers stop and ask. Default 90%.
• Approval inbox: read-only list of what's waiting on a human (questions and gates), who started it, where it's routed, and recent decisions.
• Escalation policy (managers): what to do when a question or approval goes unanswered. Set Timeout (minutes) (0 = never escalate, the gate just holds), On timeout (Hold, Escalate: nudge a channel and keep the gate open, Auto-approve, or Auto-deny: block the task) and an optional Escalation channel (Slack channel ID). Save policy.
• Notification & approval channels (managers): channel routes. Choose a scope (Org default (all work) or Project / repo (owner/repo)), a kind (Any kind, Progress, Handoff, Needs help, Approval), and a Slack channel ID, then Add / update binding. The most specific rule wins: per-task, then project, then org default, then the most recently active channel. Leave it empty to keep the automatic behaviour.

Gotcha: with no escalation policy, an unanswered tool-approval card is declined automatically after 30 minutes; the engineer carries on without that tool if it can, and a note is posted where the card was.