The lineage-layer position for tracing the full ancestry of any outcome.
Every outcome has a history — a chain of decisions, data, and agents that produced it. This name holds the infrastructure that makes that history legible.
Coordinated sets this position belongs to — the coverage it extends. Counts are the live cluster size in the graph.
Architectural context
Outcome · Cross-Vertical · 2 compound moats. Architectural surface: Lineage. Cross-cutting: Outcome.
Layer position: Cross-cutting
Why this is canonical
'Data lineage' is an established data engineering concept; extending it to 'outcome lineage' names an emerging and necessary function as AI systems produce consequential outputs: the ability to trace any outcome back through its full causal history — data inputs, model decisions, agent actions, and human interventions.
Where it fits
A few directions this coordinate opens —
Illustrative, not exhaustive — held as a transferable canonical position, open to the buyer's own use.