How a public record becomes a buyer view.

From source to screen

The evidence chain

1. Acquire. Preserve source URL, acquisition time, declared update, SHA-256, byte size, parser version, and manifest.
2. Resolve. Treat the physical airframe as canonical and the registration as a temporal alias.
3. Transform. Apply versioned parsing, duplicate handling, taxonomy, applicability, and cohort logic.
4. Serve. Render immutable release-bound JSON without request-time analytical scans.

Claim boundary

What the product can say

The product can show what was found in a defined public snapshot, how an identity link was resolved, what model-level reporting patterns were observed, and where aircraft-specific verification remains necessary.

Hard limits

What the product cannot say

• It does not certify airworthiness, safety, reliability, or physical condition.
• It does not provide a title opinion or ownership guarantee.
• It does not infer aircraft-specific AD completion from public applicability.
• It does not treat an NTSB no-match as proof that no event ever occurred.
• It does not turn missing data into lower apparent burden.

Serving design

Reproducibility and abstention

Reports are pinned to a dataset release, source manifests, schema, and algorithm versions. Identity conflict, incomplete configuration, missing sources, and small samples produce explicit unknown, possible, conflict, or abstention states.