How Tracer reaches a conclusion

Tracer separates what the records show from what they cannot support. The same method drives the public demonstration, an own-data scan, and an organization verdict.

1. Read existing records. Tracer starts with delivery records that already exist. The public demonstration uses a published synthetic Jira export; the own-data scan explains its processing boundary before accepting input.
2. Apply deterministic rules. The connector maps known record shapes, then the data-quality gates check only their declared rules. A parse failure or missing required value becomes a named finding.
3. Keep the source attached. Every finding carries its source system, source record, query time, and extraction rule so a reader can inspect how it was produced.
4. Withhold unsupported conclusions. When required evidence is absent, Tracer reports Not computable and names the blocking record and field instead of filling the gap.

What this method establishes

It establishes what Tracer's declared rules found in the supplied records, when they were read, and which source supports each finding.

What this method does not establish

It does not turn an absent record into proof, infer business outcomes from a traceability result, or treat the synthetic demonstration as evidence about a visitor's project.

See the public claim ledger for each published claim's scope, limitation, review date, and automated gate.

A LumiraGroup product.