Evidence type
The specific field on a lineage map edge stating exactly how the claim behind that edge was verified, a config file, a query log entry, an interview, a hash check, or an honest "Suspected, unconfirmed"; the field this entire topic's method is built around interrogating.
Defined in 2 GAGE programs, which carry 3 distinct definitions of it. The wording above is taught in AI Data Governance: The Data Chair.
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
The specific field on a lineage map edge stating exactly how the claim behind that edge was verified, a config file, a query log entry, an interview, a hash check, or an honest "Suspected, unconfirmed"; the field this entire topic's method is built around interrogating.
One of four categories of substantiation this topic requires behind any mitigation claim: a test log, a red-team note, a moderation sample, or a technical control description with a named responsible owner.
The specific proof behind a lineage claim, such as a pipeline configuration file read directly, a query log entry, an interview with a named role, or an inference from indirect signals. The evidence type field is what separates a defensible lineage claim from a guess.
Where it is taught
The exact lessons this term appears in. The first 7 topics of every program are free with a free account.
- The lineage map: your estate's first honest picture of where its data actually comes from · The Estate Survey, AI Data Governance: The Data Chair
- Your lineage map under attack: the red team finds the gap you papered over · Adversarial Data Governance, AI Data Governance: The Data Chair
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.