Files
gcp_solution_architecture_a…/.agents/plans/iter-05-jev-decisions/MAP.md
Jonathan Boniface 7ee49ab352
Some checks failed
validation / verify (push) Failing after 10s
latest refactoring
2026-10-06 20:22:37 +01:00

3.7 KiB

Plan Map

Iteration: 5, Jev decisions Intent: Use Jev, a hosted decision model, for the agent's closed questions (yes or no, pick one, rate on a scale) so that large-model calls are kept for writing and reasoning. The aims are fewer tokens, faster turns, and checks the engine cannot make with string matching. Status: planned; gated on step 1 This directory covers: steps 1 to 14

What Jev is

Jev is TypeSafe AI's "System One" model. It takes a state (text) and a map of typed questions, and returns calibrated probabilities instead of prose:

  • Choice: pick one option. Returns choice, confidence, probabilities.
  • Score: rate against ordered levels. Returns score, probabilities, legend, confidence.
  • Noul: yes or no. Returns noul (0 to 1) and confidence.

Facts from the vendor's documentation, read 2026-10-06:

  • POST /api/v1/decide with Authorization: Bearer <key>; body model (optional), state, questions; response answers plus usage (input_tokens, cost_usd, credits_remaining_usd).
  • Limits: 64 thousand tokens for state plus questions, 32 thousand for state plus the longest question.
  • Price: $0.42 per million input tokens; output free.
  • Undocumented: rate limits, latency, batching, data retention, self-hosting.
  • The vendor claims up to 200x faster and 400x cheaper than comparable LLMs on classification. That is unmeasured here.

Jev will be deployed separately and reached with an API key (owner, 2026-10-06).

Sources of truth

Boundaries

Jev answers closed questions. Writing Deliverables, grounding product choices and producing infrastructure code stay with the large models. Dependencies and Approvals stay rules in the Ledger.

Status

Step What Report ref Status
1 Resolve the open questions none open, owner's input
2 Decider interface and Jev client with limits none planned
3 Pillars a Revision touches J3 planned
4 Semantic checks at submission J4 planned
5 Finding-to-Deliverable routing J2 planned
6 Model tier per delegation J5 planned
7 Context selection J6 planned
8 Skill routing J9 planned
9 In-run context compaction J10 planned
10 Evaluation rubric and lesson triage J8 planned
11 ADR: Orchestrator routing none planned, owner's decision
12 Orchestrator routing J1 planned
13 Cloud-read call guard J7 planned
14 Input guardrail J11 planned

Dependency graph

  • Step 1: no dependencies
  • Step 2: depends on step 1
  • Step 3: depends on step 2, iteration 4 step 3
  • Step 4: depends on step 2
  • Step 5: depends on step 2, iteration 4 step 1
  • Step 6: depends on step 2
  • Step 7: depends on step 2, iteration 4 step 13
  • Step 8: depends on step 2, iteration 4 step 12
  • Step 9: depends on step 2
  • Step 10: depends on step 2, iteration 4 step 7, iteration 4 step 8
  • Step 11: depends on step 4 having evaluation results
  • Step 12: depends on step 2, step 11
  • Step 13: depends on step 2
  • Step 14: depends on step 2

Steps 3 and 4 come first: they are small, need no ADR change, and target Revisions, where the tokens are. The Orchestrator is 11% of case 03's tokens; the IaC author and validator together used 1.43 million over 7 runs.