Skip to content

Recipe 22: CMDB asset matching #22

Closed

Description

@CompleteDotTech

Recipe 22 of 60 · Level 2 (Easy) · Data quality & knowledge graphs · Choice

Use case

Link differently worded software asset descriptions to a canonical configuration-management record from a bounded candidate list or a no-match outcome.

What to build

The folder recipes/22-cmdb-asset-matching/ with notebook.ipynb, README.md, and fixtures/, meeting the recipe contract. Start from python tools/new_recipe.py 22 and the template in recipes/_template/.

Build notes

  • Python looks up a bounded candidate list of canonical records. Options are record identifiers plus no_match.
  • Fixtures vary vendor aliases, version formats, and edition names.
  • Include two records that differ only by major version.

Decision design

  • Choice. Options are a fixed set supplied by Python, including the fallback outcome this use case names. Show the choice, the per-option probabilities, and the confidence for individual examples before aggregating.

Level 2 scope

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

Acceptance criteria

  • recipes/22-cmdb-asset-matching/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: Link accuracy and the false-link rate.
  • 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/22-cmdb-asset-matching/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/22-cmdb-asset-matching/ 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
  3. added 3 commits that reference this issue on Oct 9, 2026
    3bed598
    700471e
    4299ca0
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: data quality & graphsCategory: Data quality & knowledge graphsdecision: choiceUses a Choice 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