Skip to content
JJev AtlasField notes
The atlasStart hereClaimsProjectsPatternsIdeasMapEvidenceLibraryFor agents
Search⌘K

J Jev Atlas / Independent research

165 posts · 9 claims · 31 hypotheses

Back to top ↑

An independent field guide to system-one models

The Jev research atlas

165 posts mapping the claims, experiments, architectures, and open questions around intelligence that decides.

Explore the index01Claims902Projects603Patterns604Ideas3105Documents8

Browse by signal

  1. 01Technical Explanation31
  2. 02Project28
  3. 03Performance20
  4. 04Code10
  5. 05Announcement8
  6. 06Cost8
View all evidence →

01 Field synthesis

Intelligence that decides, mapped.

What Jev is, what TypeSafe claims, what developers have actually built, and where the architecture gets interesting.

Read the full report →
165unique posts
63retained sources
9claims tracked
31build hypotheses
Claims ledgerStatus
  1. 01Jev exposes constrained decision primitives for Boolean probability, choice distributions, and ordered scores.Demonstrated
  2. 02TypeSafe reports Jev as materially faster than LLM workflows on its own evaluations.Vendor Claim
  3. 03TypeSafe reports a low input-token price and no metered output-token charge for Jev.Vendor Claim
View all 9 claims →
Research corpus
165posts
indexed
✦
This hypothesis was pickedfor validation

MEDIUM confidence / indie fit 10 of 10

Inbox Micro-Router

An email client companion assigning folder, urgency, next-action, and safe automation eligibility.
Open the idea

Find a thread

Search across every research layer.

Claims, projects, product ideas, source posts, and long-form synthesis are indexed together.

⌘K
ClaimJev exposes constrained decision primitives for Boolean probability, choice distributions, and ordered scores.The public API documentation defines `noul`, `choice`, and `score` response shapes.ClaimTypeSafe reports Jev as materially faster than LLM workflows on its own evaluations.The launch material reports large latency multiples; X discussion mostly repeats those figures.ClaimTypeSafe reports a low input-token price and no metered output-token charge for Jev.Published pricing is echoed across launch discussion, but remains mutable vendor pricing.ClaimTyped output removes free-form parsing but does not make wrong decisions impossible.The API contract constrains output types; correctness and calibration are separate empirical properties.ClaimRouting, classification, verification, and workflow control are the dominant early mental models.Those categories recur in the collected launch discussion and align with the documented output primitives.

Agent interface · MCP

Don’t make your agent scrape the atlas.

Connect it directly to the same normalized claims, projects, patterns, opportunities, evidence status, and sources that power this website.

Connect an agent →

The research run

What this evidence set cost.

Three capped collection passes gathered the launch-period conversation, then a local pipeline classified and synthesized the retained material.

01

Collection

resources returned
00 requests
02

Deduplication

unique posts
1650 capped runs
03

Estimated API spend

total collection
$0.00$0.000 / post

Costs are estimates based on provider pricing at collection time. They cover X API retrieval only, not analysis or development time.

02 Located work

What people have actually built.

Public repositories, demonstrations, and integrations—kept separate from proposals and launch copy.

01

HA-Jev

Decision models can act as a semantic layer inside an existing event-driven rules engine.

Open ↗
02

typesafe-mcp

The probability-bearing result can be preserved through agent infrastructure instead of flattened to prose.

Open ↗
03

MAGI System on Jev

Cheap typed judgments invite ensemble and quorum experiments, though correlated errors still need measurement.

Open ↗
04

Goblin HR

Keeping selection probabilistic and execution deterministic makes the boundary easy to inspect.

Open ↗
05

Axon Work integration

A decision model can be invisible infrastructure beneath a workflow product.

Open ↗
View the project index →

About & methodology

How a noisy launch conversation became a navigable atlas.

The pipeline preserves sources, separates evidence levels, and keeps unanswered questions visible next to conclusions.

  1. 01

    Jev Research Report

    The complete view: evidence, developer activity, architectures, limitations, and opportunities.

  2. 02

    Jev Foundations

    Facts, vendor claims, independent observations, opinions, speculation, and unknowns.

  3. 03

    Research Claims

    Important claims with status, evidence, counterarguments, sources, and open questions.

  4. 04

    What People Are Building

    Located projects and demonstrations, kept separate from proposals and speculation.

  5. This is a launch-period, English-only, query-conditioned sample. Heuristic scores organize attention; they are not objective quality labels. The local dataset contains 0 processed records.