🎫 Tickets: your decision queue

A ticket is an agent saying: “I could guess here, but I shouldn’t.” Spending money, sending something risky to a customer, choosing between two real directions - instead of guessing, the agent blocks the mission and opens a ticket with everything you need to decide: the context, the options, and (if you’ve trained it well) a recommendation.

Anatomy: each ticket carries typed sub-asks - approve/deny, pick an option, provide a missing fact - and the mission it blocks. Resolve every sub-ask and the mission unblocks itself; the agent picks up exactly where it stopped, with your answers in hand. No chasing, no “did you see my question”.

Resolving well: answer the question that was asked, and add one sentence of why when you deny or redirect - the why is what agents learn from. Open thread turns a ticket into a conversation when the question deserves discussion. Undo exists for sub-asks you answered too fast (it posts your withdrawal to the thread so the agent knows).

⚠️ Heads up: A go-ahead is a real instruction - once an agent acts on it (sends the email, spends the budget), undoing the ticket can’t unsend anything. Undo is for “wait, let me reconsider”, not for taking back what already happened.

💡 Tip: Watch your ticket patterns. The same question three times = a briefing gap: answer it once more, then add the rule to the agent’s standing instructions so that category of ticket stops existing.

The bar to hold: a healthy workspace runs 1-5 tickets a day, each decidable in under a minute. More than that and agents are under-briefed (they’re asking things your docs should answer); zero for weeks and they may be over-guessing - spot-check the board.