RFC: Core-resolved product manifests - #610
Open
filvecchiato wants to merge 1 commit into
Open
Conversation
8 tasks
The core reads a product's root manifest from dotNS and answers whether one product grants another a scope, so `manifest_grants_scope` returns a real answer instead of always refusing. Hosts neither fetch manifests nor decide what a grant covers. Resolution derives the node, finds the resolver through the dotNS registry and reads the `manifest` text record, reusing the gateway helpers and the pinned-block transport the identity lookup already drives. That transport moves out of identity.rs into runtime/dotns_lookup.rs, since both readers need it. A resolved manifest is cached in CoreStorage and honoured for one day. That lifetime is a revocation bound: a record edit carries no signal, so a withdrawn grant takes effect when the manifest is next read. Every reason a grant cannot be established answers the same — unresolvable name, no manifest, failed fetch, narrower scope — so a cross-product call cannot probe which products exist, and an unreachable chain withdraws grants rather than assuming them.
filvecchiato
force-pushed
the
feat/core-manifest-resolution
branch
from
September 4, 2026 16:11
e732261 to
482afe2
Compare
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The core resolves each product's root manifest from dotNS and answers whether one
product grants another a scope. Hosts neither fetch manifests nor decide what a
grant covers, so a grant means the same thing wherever a product runs.
Resolution derives the node, finds the resolver through the dotNS registry and
reads the
manifesttext record, reusing the gateway helpers and thepinned-block transport the identity lookup drives. That transport lives in
runtime/dotns_lookup.rs, shared by both readers.A resolved manifest is cached in
CoreStorageand honoured for one day. Thelifetime is a revocation bound rather than a performance knob: a record edit
carries no signal, so a withdrawn grant takes effect when the manifest is next
read.
Every reason a grant cannot be established answers the same — unresolvable name,
no manifest, failed fetch, narrower scope — so a cross-product call cannot probe
which products exist. An unreachable chain withdraws grants rather than assuming
them.
Based on #454, which carries the adjudication seam this fills.
Verification
truapi-servertests, whole workspace greencargo +nightly fmt --checkand workspace clippy cleanCoreStorageKey::ProductManifestvariant and the wire schema hashA user's own denial is not consulted yet — nothing prompts for cross-product
access, so there is no stored denial to read. The check belongs with the prompt
that creates one.