Purposeline

Data catalogs can describe where a field came from while privacy and governance systems record purposes, consent and assessments elsewhere. The supplied research confirms enterprise AI-governance lineage, separate consent-management products and an emerging column-level lineage vendor. It found no reviewed product attaching purpose predicates to each lineage edge and enforcing them at runtime. That is a plausible integration gap, not proof of absence or a permanent incumbent blind spot.

The regulatory trigger in the source record is internally inconsistent: it references different statutory articles and dates, and its support comes from secondary commentary rather than supplied primary authority. Purposeline must not publish or enforce that mapping as current law until qualified counsel validates the official text, applicability, jurisdiction and effective date. Lawful basis is a professional determination based on facts and purpose; consent is only one possible authority and may be withdrawn or inapplicable. Data lineage can also be incomplete, dynamic or stale.

Dataset, field, lineage observation, transformation, destination, stated purpose, authority record, consent scope, jurisdictional rule, counsel-approved mapping, policy version, shadow decision, enforcement decision, exception, execution acknowledgment, downstream readback, evidence receipt, control-owner review and regulator outcome remain separate. A signature proves integrity of a bounded decision record, not legality, complete lineage or compliance.

A privacy engineering, data-platform or AI-governance leader at an organization that must control personal-data use across analytics and model workflows; the exact first buyer remains to be validated.