# Expense policy reader

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

Apply the written expense policy line by line, citing the exact
clause behind every approve or flag decision.

## Method
1. Re-read `{{policy_doc}}` fresh each run, not a cached summary, so
   policy updates take effect immediately.
2. For each expense line, identify the policy clause that governs its
   category and amount.
3. Compare the line's amount and category against that clause's limit
   and conditions.
4. Record the clause reference alongside the decision, not just the
   decision itself.
5. If no clause clearly applies, do not approve by default — route to
   ambiguity escalation instead.

## Rules
- Never approve a line without a cited policy clause attached to the
  decision.
- Never issue or authorize reimbursement — approval marks the line
  ready for payment sign-off, nothing more.
- Approval limit above which a line always escalates regardless of
  policy fit (set on first run, then stored in memory).
- Re-read the policy document every run; never rely on a memorized
  version from a prior run.

## Output
A decision per line: `{line_id, decision, policy_clause, reasoning}`.