Provenance tracking

Scope agreed before anything gets built.

The first question is always who counts as in scope. Matching produces confident pairs and probable ones, and only the first are treated as matches. What arrives is a file whose every column has a written definition.

  1. Criteria translation

    Finding the nearest countable equivalent when a requirement has no direct expression in the available fields.

  2. Change-only refresh

    On a repeat build, reporting what actually moved instead of re-delivering the whole file.

  3. Matching

    Reconciling what you hold against what is current, with disagreements surfaced rather than silently resolved.