Recipe 24: Incident priority composition #24

Recipe 24 of 60 · Level 3 (Intermediate) · Workflow & service operations · Score

Use case

Score reported business impact and urgency against separate rubrics so Python can map the scores to defined categories and apply a fixed service-priority matrix.

What to build

The folder recipes/24-incident-priority-composition/ with notebook.ipynb, README.md, and fixtures/, meeting the recipe contract. Start from python tools/new_recipe.py 24 and the template in recipes/_template/.

Build notes

• Two Score questions in one request: business impact and urgency, each with its own rubric.
• Python maps each score to a category and applies a fixed priority matrix. The matrix is data, not prose.
• Show a ticket where the two scores pull in different directions.

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 3 scope

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

Acceptance criteria

• recipes/24-incident-priority-composition/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: Agreement of the final priority with gold, and of each score with its gold category.
• 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/24-incident-priority-composition/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/24-incident-priority-composition/ 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 03: Response clarity scoring #3 (Response clarity scoring). 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.