Addressing Overview

Context Nest uses the contextnest:// URI scheme to address documents, sections, tags, and folders within a vault.

URI format

contextnest://[namespace/]path[#anchor][@checkpoint]

URI	Resolves to
`contextnest://nodes/architecture`	The architecture document
`contextnest://nodes/architecture#data-flow`	The "Data Flow" heading
`contextnest://nodes/architecture@5`	Architecture at checkpoint 5
`contextnest://engineering/`	All documents in the engineering folder
`contextnest://tag/api`	All documents tagged `#api`
`contextnest://search/rate+limiting`	Full-text search results
`contextnest://platform/infra/networking`	Cross-namespace reference

Use contextnest:// URIs in your document bodies to create cross-references:

For the API design, see [Architecture](contextnest://nodes/architecture-overview).

These links are tracked in context.yaml as relationship edges and used to compute hub documents.

Append @N to pin a URI to a specific checkpoint:

contextnest://nodes/architecture@5

This resolves to the version of the document that was current at checkpoint 5, not the latest version.

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:
URI ResolutionResolution is the process of converting a contextnest:// URI into a document or set of documents.
Core ConceptsContext Nest is built on a small set of composable concepts. Understanding these gives you the full picture of how vaults work.
Context IndexThe context.yaml file is the machine-readable manifest of a Context Nest vault. It is auto-generated by the CLI and serves as the primary entry point for…