release: implement site registry v0.4 trust pipeline
This commit is contained in:
parent
2861337a45
commit
e26efc19fa
67 changed files with 10698 additions and 640 deletions
24
docs/adr/0006-source-lineage.md
Normal file
24
docs/adr/0006-source-lineage.md
Normal file
|
|
@ -0,0 +1,24 @@
|
|||
# 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.
|
||||
Loading…
Add table
Add a link
Reference in a new issue