Semantic Substrate

Inquire

The tabular-data position for provenance — where origin tracking meets the structured record.

A substrate coordinate naming provenance at the data-table level — the position for systems that attach origin metadata to structured records, rows, and datasets.

Coordinated sets this position belongs to — the coverage it extends. Counts are the live cluster size in the graph.

Primary home

Provenance cluster93

Also appears in

Ledger cluster22

Architectural context

Provenance · Cross-Vertical · 2 compound moats. Architectural surface: Provenance.

Layer position: Substrate (L1)

LedgerProvenance

Why this is canonical

The table is the universal data primitive: rows, columns, records. Attaching provenance to the table names the layer at which origin tracking becomes embedded in structured data — not just in files or pipelines, but in the record-level granularity that analytics, compliance, and AI training all operate at. This is a data-layer framing for provenance.

Where it fits

A few directions this coordinate opens —

Data catalog and lineage
Provenance at the table and column level — embedding origin metadata directly into the structured data assets that analysts, models, and compliance teams consume.
Data catalog vendors, analytics infrastructure builders
AI training data governance
Origin tracking for the tabular datasets used in AI training — enabling per-record provenance that survives transformation and sampling.
AI data infrastructure companies, MLOps platform vendors

Illustrative, not exhaustive — held as a transferable canonical position, open to the buyer's own use.

← More in Provenance