REPOSITORY ANALYSIS

atomic

An optional Jev decision backend in the Atomic coding Agent for bounded structured choices such as routing.

E2 · source reviewedPublic material or source evidence was reviewed. A fixed-version source review requires checking a pinned revision; this is not a reproduction, performance endorsement, or safety guarantee.
Stars
820
Forks
113
License
—
Last commit
2026-09-24

What Jev does here

Sends predefined questions to Jev and decodes answers for callers; regular models still generate code.

Separates structured decisions from text-generation interfaces.

The verified scope is an optional structured-output provider, not that Atomic uses Jev by default or for every feature. LICENSE includes an additional UI-attribution condition above stated business-size thresholds. It is not standard MIT; read the license text.

What task does this project fit?

Turn schema-bound choices into typed workflow results while handling large candidate sets.

Material analysed:

From input to action

  1. Compile the workflow's choice questions.
  2. Use one request when within provider limits; otherwise partition and retain candidates.
  3. Validate distributions and decode final selected keys into the result schema.

Implementation details that matter

Large choices become a tournament

inferJev can partition candidates, keep ranked survivors and run additional rounds. One high-level structured-output call may therefore involve multiple inference requests and a changed comparison context.

Inspect the supporting source ↗

Validation rejects inconsistent choice distributions

The parser checks probability keys, bounds, mass and whether choice is a highest-probability option. Structural validation cannot recover a relevant candidate eliminated in an earlier round.

Inspect the supporting source ↗

When to choose it

Useful for explicit workflow control where schemas and interruption matter. For very large candidate sets, evaluate tournament recall and call cost against a retrieval-first alternative.

How to inspect it yourself

Read planRound, packRequests and inferJev together. Check cancellation between rounds and verify that retainForFinal preserves any required escape candidate.

Limits of this review

  • No Atomic workflow or provider call was run.
  • Tournament ranking is not equivalent to evaluating every option together in one model context.
Primary material used in this analysis