agent flagged every starbucks as personal - no client-meeting context

TL;DR

The agent's rule says coffee shops are personal, but coffee shops are also where client meetings happen, so every working coffee got flagged. Change the rule from merchant-based to context-based: check the calendar, attendee list, and business purpose before flagging, and only flag when no business context exists. Merchant alone never proves personal.

Error

agent flagged every starbucks as personal  -  no client-meeting context

Steps

1. Confirm the pattern: the agent's flags cluster on one merchant type with no other signal. Expected: the flag log shows merchant-only reasoning.
2. For a sample of flagged expenses, check the calendar and attendee lists for matching meetings. Expected: many flagged coffees align with real meetings.
3. Rewrite the rule: flag only when there is no calendar event, no attendees, and no business purpose on file. Expected: the rule requires missing context, not just the merchant.
4. Add an allowlist path: expenses with attendees or a meeting reference pass automatically. Expected: working coffees stop getting flagged.
5. Re-run over the flagged set and review the remaining flags. Expected: only context-free expenses remain flagged.

When to use

• An agent flags a whole merchant category as personal.
• Legitimate client-meeting expenses are being questioned.
• Tuning classification precision in an audit agent.

When not to use

• The expenses are genuinely personal (the flag is correct).
• The merchant is on an explicit blocked list (policy, not inference).
• The issue is duplicate detection, not classification.

Tool compatibility

Applies to custom audit agents with classification rules (Python, agent frameworks; current 2026 releases).

Variant phrasings

coffee shop expenses auto-flagged as personal

Require missing business context before flagging, not just the merchant.

agent ignores calendar context on meals

Feed the calendar and attendee data into the classification rule.

merchant-blocklist too aggressive in the audit agent

Replace merchant rules with context rules.

Why it happens

Merchant-category rules are cheap to write and feel precise, but merchants are venues, not purposes: the same coffee shop hosts client meetings and personal errands. An agent without calendar, attendee, or purpose data can only see the venue, so it misclassifies systematically. Business context is the actual signal for personal-versus-business; the merchant is just where it happened.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_adInACH6BbzXHpx8vvM2oQ