All checks were successful
Standalone registry checks / check (push) Successful in 5m58s
26 lines
1.2 KiB
Markdown
26 lines
1.2 KiB
Markdown
# ADR 0006: Source lineage and independence
|
|
|
|
Status: Implemented in 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.5 adds explicit source-manifest lineage and exposes it in evidence and
|
|
evaluation without rewriting legacy history. It preserves provider-native
|
|
provenance and never combines popularity or same-domain evidence into ownership
|
|
confidence. Current admission quorum is made only from authenticated reviewers,
|
|
groups and physical keys, so copied source assertions cannot increase authority.
|
|
|
|
## 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.
|