Repository navigation
Recipe 03: Response clarity scoring #3
Copy link
Copy link
Closed
Labels
cat: language & contentCategory: Language & contentCategory: Language & contentdecision: scoreUses a Score questionUses a Score questionlevel: 1 beginnerOne bounded judgment over a short prepared inputOne bounded judgment over a short prepared inputpriority: p1Next up once unblockedNext up once unblockedsize: SAbout half a day for one agent or personAbout half a day for one agent or personstatus: blockedWaiting on the issues listed under DependenciesWaiting on the issues listed under Dependenciestype: recipeA cookbook notebook recipeA cookbook notebook recipe
Milestone
Description
Recipe 03 of 60 · Level 1 (Beginner) · Language & content ·
Score
Use case
Score a support response against a clearly defined clarity rubric to identify examples that need editing.
What to build
The folder recipes/03-response-clarity-scoring/ with notebook.ipynb, README.md, and fixtures/, meeting the recipe contract. Start from python tools/new_recipe.py 03 and the template in recipes/_template/.
Build notes
- Write a clarity rubric with every level described in words, lowest to highest.
- Fixtures: support responses with a human rubric level each, spanning the whole scale.
- Python flags responses below a cutoff as needing an edit. The cutoff lives in code.
Decision design
- Score. Describe every rubric level in words, in order. Show the
scoreand the distribution over levels. Mapping, weighting, and arithmetic on scores happen in Python.
Level 1 scope
One bounded judgment over a short prepared input with direct inspection of typed results.
Acceptance criteria
-
recipes/03-response-clarity-scoring/notebook.ipynbruns top to bottom offline, with no key and no network, and its outputs are committed - Live mode is opt-in (
JEV_COOKBOOK_LIVE=1withTYPESAFE_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: Exact-level agreement and mean absolute error against the human levels, plus the distribution over levels for a few examples.
- A reader with basic Python can follow it end to end; every new term is explained where it first appears
- At least three individual typed answers are displayed and discussed before any aggregate metric
- 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/03-response-clarity-scoring/README.mdsays what the recipe teaches, how to run it, and what was and was not measured live - The pull request changes only
recipes/03-response-clarity-scoring/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)
- Tracked in Epic: Level 1 · Beginner recipes #75
Sources
Read these before writing the questions.
- S02 · TypeSafe AI: Primitives (Questions): Choice, Noul, Score, independent questions, and dependent follow-up calls.
- S07 · TypeSafe AI: Jev 1.13 jaggedness: Version-specific limitations affecting arithmetic, context selection, adversarial content, and generation.
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.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
cat: language & contentCategory: Language & contentCategory: Language & contentdecision: scoreUses a Score questionUses a Score questionlevel: 1 beginnerOne bounded judgment over a short prepared inputOne bounded judgment over a short prepared inputpriority: p1Next up once unblockedNext up once unblockedsize: SAbout half a day for one agent or personAbout half a day for one agent or personstatus: blockedWaiting on the issues listed under DependenciesWaiting on the issues listed under Dependenciestype: recipeA cookbook notebook recipeA cookbook notebook recipe
Activity
CompleteDotTech commentedon Oct 8, 2026
Governance final-integration acceptance follow-up for the existing primary/recipe03 owner (no competing writer): local signed builder head
7afa6ae50c4e89279fc134953b1835b9347609ffnow exists; eight paths are confined torecipes/03-response-clarity-scoring/, response40/authentic0, committed notebook contains no error output. This is not final PR acceptance or Opus approval.G3-1: README “Pull request rules” currently says rootREADME is regenerated separately after handoff, “never by this recipe's own pull request”. The authorized narrow exception requires a designated Sonnet integration worker to regenerate ONLY rootREADME catalog regions into the SAME recipe PR, after a signed current-main update and BEFORE final Opus/complete CI. Please correct that sentence during this existing owner's delivery so readers do not learn a contradictory workflow. Builders remain recipe-folder-only; Catalog may be red during initial handoff but MUST be green on the final reviewed head before merge. Do not waive Catalog or defer its repair until after merge.
Keep sole primary serial integration/merge ownership, resulting-head approval renewal, source consistency, synthetic disclosure and cumulative$25 recording/release gates. Governance has changed no recipe files or launched tests/workers.
Foundation: fix round 1 for sweep batch A (#163) — review 6085598499
Sweep: recipes 01-05 aligned with the current contract and guard (#190)
Sweep: matrix print alignment, answer-plot titles and URL form, batch…