release: implement site registry v0.4 trust pipeline

This commit is contained in:
Nic Weyand 2026-09-13 12:22:05 -04:00
commit e26efc19fa
Signed by: nicweyand
SSH key fingerprint: SHA256:2te+ycJIQON/Wo/dH6+ZkFSQ4HnHWpetV2azx9E65dQ
67 changed files with 10698 additions and 640 deletions

View file

@ -0,0 +1,23 @@
# ADR 0002: Separate names, website edges, and observations
Status: Accepted, 2026-09-13.
A name binding, entity-to-property edge, and crawler observation have separate
identities and decisions. A resolver must admit the matched name and the selected
website edge. Observations enter evidence bundles but never create ownership,
identity, or regional roles.
This prevents a new alias from inheriting an existing route and avoids invalidating
an unchanged route when unrelated entity metadata changes.
## Rejected alternatives
One decision over the whole entity made harmless label changes invalidate every
route and let an injected alias inherit old authority. Promoting observer signals
directly would turn redirects or self-authored metadata into ownership claims.
## Compatibility
Legacy review rows remain auditable under the explicit compatibility policy.
Strict v0.4 resolution requires separate name and edge votes. V2 edge fingerprints
exclude unrelated entity revision metadata while retaining it in provenance.