Build blueprint
Inbox Micro-Router
An email client companion assigning folder, urgency, next-action, and safe automation eligibility.
- Problem
- Email rules fail on semantics, while generative inbox agents are costly and overpowered.
- Why Jev
- Each message creates multiple small parallel decisions with no need for generated text.
- Architecture
- Message + relationship state → parallel Choice/Score questions → local rules → label or queue.
- Current alternative
- Filters, priority inbox classifiers, and LLM assistants.
- Jev advantage
- Can classify every inbound message and reclassify threads after replies.
- Unknowns
- Provider access, sensitive content handling, and multilingual quality.
Why this confidence: Well-bounded decisions and a feasible shadow-mode MVP.
This is an authored hypothesis derived from the research corpus. Nothing here demonstrates product demand, or that Jev performs well on this particular workload. Run the validation experiment before building past the MVP.
Sources
Limitations
- Provider access, sensitive content handling, and multilingual quality.
- This is a research hypothesis, not evidence of product demand or Jev performance in this workflow.
Supporting research
- Cascade router PlausibleA cheap decision chooses whether to use rules, a small model, a premium model, a specialist, or a human.
- HA-Jev ObservedA Home Assistant custom integration exposing Jev evaluations as sensors and automation actions.
- Routing, classification, verification, and workflow control are the dominant early mental models. PlausibleThose categories recur in the collected launch discussion and align with the documented output primitives.
- Parallel decision matrix PlausibleOne state is evaluated against many named questions, replacing repeated prompt/parse cycles.