Recipe 25: Change evidence review #25

Recipe 25 of 60 · Level 3 (Intermediate) · Workflow & service operations · Noul

Use case

Check whether a proposed change includes sufficient implementation, validation, and rollback evidence so a deterministic checklist can identify review gaps.

What to build

The folder recipes/25-change-evidence-review/ with notebook.ipynb, README.md, and fixtures/, meeting the recipe contract. Start from python tools/new_recipe.py 25 and the template in recipes/_template/.

Build notes

• Three independent Nouls: sufficient implementation evidence, validation evidence, and rollback evidence.
• A deterministic checklist combines them and lists the review gaps.
• Include change records that mention a rollback plan without describing one.

Decision design

• Noul. Write each proposition as a statement that is true or false. One independent question per label or concern, sent together in one request. Noul has no confidence field, so each threshold is chosen from examples and evaluated.

Level 3 scope

Multiple judgments or stages, structured evidence, deterministic composition, and task-level evaluation.

Acceptance criteria

• recipes/25-change-evidence-review/notebook.ipynb runs top to bottom offline, with no key and no network, and its outputs are committed
• Live mode is opt-in (JEV_COOKBOOK_LIVE=1 with TYPESAFE_API_KEY) and uses the same question definitions as the offline run
• Fixtures are synthetic, include the hard cases named in the build notes, carry gold labels, and pass the fixture validator
• Every response fixture records its provenance, and the notebook states which mode it ran in
• Evaluation: Precision and recall per proposition, and accuracy of the gap list.
• The deterministic composition lives in a Python function with tests in tests/
• Evaluation is at task level, not only per question
• No statement about Jev's quality, latency, or cost appears without recorded live inference; in a synthetic run, metrics are labelled as pipeline checks
• recipes/25-change-evidence-review/README.md says what the recipe teaches, how to run it, and what was and was not measured live
• The pull request changes only recipes/25-change-evidence-review/ and CI is green

Dependencies

• Blocked by Foundation: CI executes every notebook offline and validates fixtures #69 (CI executes every notebook offline and validates fixtures)
• Builds on Recipe 06: Multiple topic labels #6 (Multiple topic labels). Merge those first and reuse their patterns; do not copy their fixtures.
• Tracked in Epic: Level 3 · Intermediate recipes #77

Sources

Read these before writing the questions.

• S02 · TypeSafe AI: Primitives (Questions): Choice, Noul, Score, independent questions, and dependent follow-up calls.
• S03 · TypeSafe AI: Confidence: Distribution-derived confidence and task-specific thresholds informed by observed outcomes.
• S04 · TypeSafe AI: How to build with TypeSafe: Narrow semantic judgments integrated with workflows, deterministic logic, and side effects controlled by code.

Out of scope

• Changes to shared code, the catalog, or the root README. If the shared package is missing something, open a foundation issue and link it here.
• Real side effects of any kind. Actions are simulated.