release: implement site registry v0.5
All checks were successful
Standalone registry checks / check (push) Successful in 5m58s
All checks were successful
Standalone registry checks / check (push) Successful in 5m58s
This commit is contained in:
parent
967d7ab45f
commit
557ba7cd69
40 changed files with 3331 additions and 158 deletions
|
|
@ -1,15 +1,17 @@
|
|||
# ADR 0006: Source lineage and independence
|
||||
|
||||
Status: Accepted design; implementation scheduled for 0.5.
|
||||
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.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.
|
||||
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
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue