Understand source qualification

Stage 0 pilot, reviewed 23 September 2026. In Workspace, open Data, filter by source or scientific type, and inspect an upstream dataset. For Wells, choose Datasets to inspect the collection rather than an individual record.

The Source qualification section shows:

• Fidelity assessment: not assessed, assessed with no detected loss, or assessed with reported loss. Always read the scope; preserving bytes is not scientific approval.
• Scientific profile / source schema / mapping version: the interpretation and exact source shape used by the reader. They are separate versions.
• Historical reads: whether the reader can request exact upstream versions or only the current source. Replaced SQL/file content may no longer be retrievable.
• Retained snapshot: a recorded retention claim, not permission to share data.

Expand Assessment evidence and limitations to see the method and unresolved meaning. An older source report shows Not assessed. A missing schema/version shows Not recorded; the interface does not guess.

Reading a source does not authorize retaining or redistributing it. Existing project and source authorization still apply. An expired sign-in or denied source must be restored before inspection; a cached report does not bypass the check.

Unknown units or depth references remain visible. A missing reference record can allow inspection while preventing an operation or destination publication that needs resolved context. No conversion is inferred from the label shown in a form.

This foundation does not add multi-asset approval, retained-package sharing, general OSDU publication or native application telemetry. See availability. Try the synthetic independent-reading demo and read the developer contract.