Action item tier
The classification a meeting action item gets that determines whether the agent fires it automatically, queues for approval, or always asks. Three tiers: auto (fires now), approval (queued, fired on user OK), always-ask (queued with explicit lock).
Why it matters
A meeting recap with action items has to decide what happens next. Some actions are clearly safe to fire automatically (sending the recap email, adding the meeting to your calendar). Some need explicit user approval (sending an email to a senior person, drafting a contract). Some should always require explicit per-action confirmation (moving money, making commitments on someone else's behalf).
The tier system formalizes the decision. Each action gets a tier; the user's behavior depends on the tier. Without tiers, the agent either auto-fires too much (creating mess) or queues everything (creating overhead).
How Ajeris handles this
Action items in the recap pipeline are tier-classified during the recap generation. Auto items fire immediately. Approval items are queued; the recap email lists them with numbers; the user replies "do 1, 2, 4" via the approval parser. Always-ask items are queued with a lock icon; they require per-item confirmation. Queued actions expire after 24 hours.
