URI Resolution
Resolution is the process of converting a contextnest:// URI into a document or set of documents.
Floating resolution (default)
A URI without a checkpoint pin resolves to the latest published version:
contextnest://nodes/architecture
→ architecture v4 (current)
Pinned resolution
A URI with @N resolves to the version current at checkpoint N:
contextnest://nodes/architecture@5
→ architecture v2 (as of checkpoint 5)
The resolver reads .versions/context_history.yaml to look up the document_versions map at the specified checkpoint.
Source node resolution
When a URI targets a type: source node, resolution returns the source document itself (frontmatter and markdown body). Hydration — executing the described tool calls — is a separate step performed by the agent.
A link to a source node is a reference to the source's instructions and framing, not a guarantee that live data will be fetched.
Resolution order
- Check the URI for an authority component (namespace). If present and federation is enabled, route to the external registry.
- Normalize the URI to canonical form.
- If pinned (
@N), look up the version from the checkpoint history. - Resolve the path to a document, folder, tag set, or search result.
- Return only published content (unless explicitly requesting drafts).
Related pages
- Addressing OverviewContext Nest uses the contextnest:// URI scheme to address documents, sections, tags, and folders within a vault.
- Cross-Vault FederationFederation enables cross-namespace URI resolution — referencing documents in other vaults.
- URI FormatThe contextnest:// URI scheme follows RFC 3986 conventions. Implementations must normalize URIs before resolution:
- PromptOwl DocumentationWelcome to the documentation for PromptOwl and Context Nest — the open protocol and hosted platform for giving AI agents structured, versioned, governed…
- Add DocumentsThis creates nodes/api-design.md from a frontmatter template as version 1, and regenerates the index. Tags accept a comma- or space-separated list; you…