[WSJF-3] Planner step: classify email type before extraction #19

New issue

Open

opened 2026-06-27 10:46:15 +02:00 by bullitt · 0 comments

bullitt commented

2026-06-27 10:46:15 +02:00

Owner

Context

Article's three-agent system: Planner expands scope, Generator implements, Evaluator tests.

Problem

Our AI prompt jumps directly to extraction without understanding the email type. For ambiguous emails, this leads to wrong status mapping.

Proposal

Add a lightweight classification pre-step (could be rule-based or cheap model):
- Is this a shipping notification? (vs. order confirmation, return, etc.)
- What carrier?
- What stage? (confirmation, shipped, in-transit, delivery, delivered)
Feed classification context into extraction prompt for better accuracy

WSJF: 3

## Context Article's three-agent system: Planner expands scope, Generator implements, Evaluator tests. ## Problem Our AI prompt jumps directly to extraction without understanding the email type. For ambiguous emails, this leads to wrong status mapping. ## Proposal - Add a lightweight classification pre-step (could be rule-based or cheap model): - Is this a shipping notification? (vs. order confirmation, return, etc.) - What carrier? - What stage? (confirmation, shipped, in-transit, delivery, delivered) - Feed classification context into extraction prompt for better accuracy ## WSJF: 3