Emerging Architecture Patterns
Decision sidecar
A typed judgment service sits beside ordinary code; code owns effects and safety boundaries.
- Evidence: source 1, source 2, source 3, source 4
- Caveat: The extra network hop must beat a local rule or classifier.
Cascade router
A cheap decision chooses whether to use rules, a small model, a premium model, a specialist, or a human.
- Evidence: source 1, source 2, source 3
- Caveat: Bad routing can erase all cost savings through failures and retries.
Confidence gate
Automation proceeds above a threshold; ambiguous cases go to another check or a person.
- Evidence: source 1
- Caveat: Thresholds require workload-specific calibration and monitoring.
Parallel decision matrix
One state is evaluated against many named questions, replacing repeated prompt/parse cycles.
- Evidence: source 1, source 2
- Caveat: Accuracy and question interactions under large batches remain unknown.
Probabilistic predicate + deterministic action
Jev supplies fuzzy predicates while TypeScript, policies, and workflows execute constrained actions.
- Evidence: source 1, source 2
- Caveat: Incorrect predicates are still operational errors even when outputs are valid.
Decision quorum
Multiple typed judgments are aggregated through voting or confidence-aware stopping.
- Evidence: source 1
- Caveat: Calling the same model repeatedly may produce correlated rather than independent evidence.