Approval parser
The component that interprets a user's reply to a queued action list. Parses 'do 1,2' or 'approve 3' or 'do all' and fires the matching queued actions.
Why it matters
The recap pipeline produces queued actions; the user has to be able to fire them with minimal friction. A long-form approval flow ('please confirm by clicking this link') is too heavy. A loose-conversation flow ('can you fire the second one') depends on the agent's interpretation. The approval parser sits in the middle: a deterministic regex over standard reply forms, with the agent as fallback for edge cases.
Most users adopt the structured form quickly. 'do 1,2' becomes the muscle memory; 'approve 3' is identical; 'yes do 1' works because the parser is forgiving.
How Ajeris handles this
The approval parser uses a regex that catches '(do|approve|yes do)\b ... ([0-9][,\d\s\band]*)' and pulls indices. Edge cases ('do everything except the third' or 'fire 2 and 4 but skip 5') route to the LLM for interpretation. The result is a list of indices to fire; the agent fires them and confirms.
