Skip to content

Recipe 03: Response clarity scoring #3

Closed

Description

@CompleteDotTech

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 score and 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.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: 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.md says 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

Sources

Read these before writing the questions.

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.

Activity

  1. added this to the M1 · Beginner milestone on Oct 6, 2026
  2. added
    type: recipeA cookbook notebook recipe
    level: 1 beginnerOne bounded judgment over a short prepared input
    size: SAbout half a day for one agent or person
    status: blockedWaiting on the issues listed under Dependencies
    on Oct 6, 2026
  3. CompleteDotTech commented on Oct 8, 2026

    @CompleteDotTech
    ContributorAuthor

    Governance final-integration acceptance follow-up for the existing primary/recipe03 owner (no competing writer): local signed builder head 7afa6ae50c4e89279fc134953b1835b9347609ff now exists; eight paths are confined to recipes/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    cat: language & contentCategory: Language & contentdecision: scoreUses a Score questionlevel: 1 beginnerOne bounded judgment over a short prepared inputpriority: p1Next up once unblockedsize: SAbout half a day for one agent or personstatus: blockedWaiting on the issues listed under Dependenciestype: recipeA cookbook notebook recipe

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions