knowledgepixels / nanopub-query / 24529355592

60%

push

github

doc: spell out admin/maintainer chain resolution

Add an "Authority Chain Resolution" section spelling out how the closed
admin and maintainer sets are computed as a fixed-point closure over
gen:hasAdmin / gen:hasMaintainer triples, with each delegation step
validated against the trust-state mirror. Pin three semantics decisions
(closure-based not time-ordered, sticky non-cascading revocation,
SPARQL alone insufficient → Java helper).

Introduce AuthorityResolver as the named component that owns the
computation, and route the previously-naive admin/maintainer joins
through it: Phase 2B authority validation, Phase 2D admin enforcement,
and Phase 9 view-display query (the latter switches from a SERVICE
join to a Java-pre-resolved pubkey IN-list). Add AuthorityResolver
to the key-files table.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

281 of 488 branches covered (57.58%)

Branch coverage included in aggregate %.

790 of 1196 relevant lines covered (66.05%)

9.63 hits per line