24 lines
1.1 KiB
Markdown
24 lines
1.1 KiB
Markdown
# ADR 0006: Source lineage and independence
|
|
|
|
Status: Accepted design; implementation scheduled for 0.5.
|
|
|
|
Corroboration must describe the direct provider, upstream dataset, transformation,
|
|
and snapshot. Two providers that copied the same upstream assertion do not count
|
|
as independent evidence merely because their URLs differ. Unknown lineage stays
|
|
unknown.
|
|
|
|
Version 0.4 preserves provider-native provenance and never combines popularity or
|
|
same-domain evidence into ownership confidence. Version 0.5 will add explicit
|
|
lineage fields and independence-aware corroboration without rewriting history.
|
|
|
|
## Rejected alternatives
|
|
|
|
Counting provider names as independent evidence rewards copied datasets. Guessing
|
|
lineage from matching text creates another unsupported inference. Dropping a
|
|
source because lineage is unknown destroys useful conflicting evidence.
|
|
|
|
## Compatibility
|
|
|
|
The v0.4 policy does not award quorum from source count, so absent lineage cannot
|
|
inflate reviewer authority. Future lineage fields must be additive provenance;
|
|
old assertions remain byte-identifiable and are never rewritten as independent.
|