Does lineage claim the map is complete?

No. A coverage view lists stores that are connected and stores that are still unknown. Gaps stay visible.

Where does the map come from?

Pipeline definitions, infrastructure definitions, query history, and job runs. Missing pieces are not invented.

Platform

A coverage view is the artefact. Completeness is not assumed.

How it moved

Edged 18 / 22 · gaps listed

Transforms and sources become edges. Not a claim that every table is modelled.

Stores and processors declared in infrastructure show up before someone remembers to inventory them.

Reads and writes that catalogs do not describe. Hints, never treated as complete.

Runtime evidence of how data actually moved. Missing jobs stay missing.

Rights scope. Erasure and access run on stores that are on the map. Unknown stores stay listed as unknown.
Vendors. A change in consent or a rights ticket follows the edges that exist. A store the map never saw is not messaged.

Inventory first: data discovery.

No. A coverage view lists stores that are connected and stores that are still unknown. Gaps stay visible.
Pipeline definitions, infrastructure definitions, query history, and job runs. The map is harvested from what already exists. Missing pieces are not invented.
Access and erasure run against stores on the map. A vendor that never appeared is not silently included. Backups that cannot erase are disclosed as retained.