Case study · located work
SemIf (formerly OpenJev)
An independent open-weights reproduction of Jev's runtime-defined typed-decision interface, running a locally hosted 4B model (e.g. Qwen3.5-4B) on a consumer GPU with a browser WebGPU demo, committed benchmark runs, and row-level output data.
ObservedTheoLeeCJ
- Problem
- An independent open-weights reproduction of Jev's runtime-defined typed-decision interface, running a locally hosted 4B model (e.g. Qwen3.5-4B) on a consumer GPU with a browser WebGPU demo, committed benchmark runs, and row-level output data.
- Jev’s role
- None — this project does not call TypeSafe's Jev API. It reproduces the interface pattern (typed options read as native logits instead of generated text) with an open model the builder controls, and its own site benchmarks against Jev only as a published external reference point.
- Architecture
- Runtime state + criteria + typed options → local open model forward pass → option logits read directly (no sampled answer token) → probabilities.
- Why it matters
- Both the GitHub README and the openjev.com site state plainly, unprompted, that the project is independent and not affiliated with or endorsed by TypeSafe — it was renamed from OpenJev to SemIf, evidence the interface pattern itself, not TypeSafe's model or brand, is what's being reproduced.
Code boundary
Jev answers the bounded questions described above. Thresholds, retries, side effects, and anything that must be reproducible stay in the surrounding application code. The research record does not capture this project’s exact question set or threshold values; read the linked source before copying the architecture.
Sources
Limitations
- A located repository or demonstration does not establish production reliability or independent validation.
Reusable pattern and related records
- Decision quorum PlausibleMultiple typed judgments are aggregated through voting or confidence-aware stopping.
- Webhook Decision Bus Authored HypothesisA developer service mapping each event to typed route, priority, and action decisions.
- Typed output removes free-form parsing but does not make wrong decisions impossible. DemonstratedThe API contract constrains output types; correctness and calibration are separate empirical properties.
- Decision sidecar PlausibleA typed judgment service sits beside ordinary code; code owns effects and safety boundaries.