Skip to content

Recipe 17: Passage reranking #17

Closed

Description

@CompleteDotTech

Recipe 17 of 60 · Level 2 (Easy) · Search & retrieval · Score

Use case

Score retrieved passages against a question so Python can rank candidate evidence and retain each passage's source reference.

What to build

The folder recipes/17-passage-reranking/ with notebook.ipynb, README.md, and fixtures/, meeting the recipe contract. Start from python tools/new_recipe.py 17 and the template in recipes/_template/.

Build notes

  • One Score per question and passage pair against a relevance rubric.
  • Python sorts by score, breaks ties by retrieval order, and keeps each passage's source reference.
  • Baseline: the original retrieval order from a small lexical scorer written in plain Python.
  • The official TypeSafe re-ranking cookbook is related reading.

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

Context-sensitive matching, scoring, or verification with candidate sets and explicit uncertain or no-match outcomes.

Acceptance criteria

  • recipes/17-passage-reranking/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: nDCG and top-1 accuracy against the baseline order.
  • Candidate sets are assembled by Python and shown to the reader
  • The uncertain or no-match outcome is exercised by several fixtures and reported separately in the evaluation
  • 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/17-passage-reranking/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/17-passage-reranking/ 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 M2 · Easy milestone on Oct 6, 2026
  2. added
    type: recipeA cookbook notebook recipe
    level: 2 easyCandidate sets and explicit uncertain or no-match outcomes
    status: blockedWaiting on the issues listed under Dependencies
    on Oct 6, 2026
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: search & retrievalCategory: Search & retrievaldecision: scoreUses a Score questionlevel: 2 easyCandidate sets and explicit uncertain or no-match outcomespriority: p1Next up once unblockedsize: MAbout a daystatus: 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