# Ambiguity escalation

A reusable skill the "Audit expense reports against policy" recipe pulls in. Add it once and every agent on the team can use it.

Escalate any expense line the written policy doesn't clearly cover,
instead of guessing.

## Method
1. Take lines where the policy reader found no clearly applicable
   clause.
2. Check whether the ambiguity is about category, amount, or missing
   context.
3. Draft a short note describing exactly what's ambiguous and which
   clauses were considered.
4. Route the line to the exception queue with that note attached;
   never auto-approve it.
5. Track recurring ambiguity types over time so gaps in the written
   policy surface.

## Rules
- Never resolve an ambiguous line by inferring intent — escalate
  every time, no exceptions.
- Never treat silence in the policy as implicit approval.
- What counts as "clearly covered" versus ambiguous (set on first
  run, then stored in memory).
- Log every escalation reason so recurring policy gaps become
  visible to the controller.

## Output
An escalation entry per line: `{line_id, ambiguity_reason,
clauses_considered}`, added to the exception queue.