Build blueprint
Micro-Approval SDK
An SDK and embeddable UI for approve/deny/escalate flows backed by typed probabilistic decisions.
- Problem
- Product teams repeatedly rebuild confidence thresholds, fallback queues, and audit logs around AI decisions.
- Why Jev
- The API can expose Jev probabilities directly while code owns threshold and action semantics.
- Architecture
- Domain adapter → Jev questions → versioned threshold policy → approval widget/audit store.
- Current alternative
- Custom prompt-and-JSON glue in every product.
- Jev advantage
- Turns safe partial automation into a reusable software pattern.
- Unknowns
- How generic the state adapters and calibration UI can be.
Why this confidence: A small, open-source developer tool that makes the core architecture tangible.
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
- How generic the state adapters and calibration UI can be.
- This is a research hypothesis, not evidence of product demand or Jev performance in this workflow.
Supporting research
- Probabilistic predicate + deterministic action PlausibleJev supplies fuzzy predicates while TypeScript, policies, and workflows execute constrained actions.
- HA-Jev ObservedA Home Assistant custom integration exposing Jev evaluations as sensors and automation actions.
- Cheap decision calls could make tens or hundreds of semantic judgments per event economical. SpeculativeThe product design follows from published pricing and parallel question primitives, not independent production evidence.
- Confidence gate PlausibleAutomation proceeds above a threshold; ambiguous cases go to another check or a person.