Viewgraph · 5 frames

Federation across Semantic Spaces

How RSM, Wellzai, and Musewoods are proposed to share identity without sharing storage: cross-space references by RID, Atlas traversal, and transfers that keep the RID.

Viewgraph5 frames

Federation across Semantic Spaces

Federation

Shared identity, independent knowledge

Spaces keep their own databases, software, and governance while sharing registered authority and resolution.

RSM ID Learning Center

rsmid.org

Document 08 v1.1 §10.1RSM ID Learning Center · informative material01 / 05
01 / 05
Read as text
  1. FederationShared identity, independent knowledgeSpaces keep their own databases, software, and governance while sharing registered authority and resolution.Source: Document 08 v1.1 §10.1
  2. Initial topologyOne registry and resolver, three independent spacesEach Locus node keeps its own content and revisions; the registry keeps identities and bindings.A shared resolver backed by one identity registry reaches three independent Locus nodes, for RSM, Wellzai, and Musewoods, each with its own database.Source: Document 08 v1.1 §10.4; Document 09 v1.1 §8.1 — proposed; no node is deployed
  3. Cross-space referencesA relationship names both ends by RIDWellzai references RSM's concept and a Musewoods fieldnote without copying either.The Wellzai document 451.7K4M9Q2X8D5P0R6T extends the RSM concept Formation, 451.5VJC3VFV46EVR73V, and references the Musewoods fieldnote Code Meets Soil, 451.5Z7MCTTCHRBCBS2S. Each lives in its own space.Source: Document 08 v1.1 §7.4, §13.2; Document 09 v1.1 §8.2 — identifiers illustrative
  4. ExplorationAtlas traverses by RID and preserves authorityAggregated descriptions stay attributed to their sources; identity is the deduplication key.Reconcile by RIDResults from several spaces combine on the canonical RID.Keep the sourceAggregated data is never treated as Atlas's own canonical knowledge.Never merge on similaritySimilar descriptions stay separate without a verified equivalence.Source: Document 08 v1.1 §10.3, §10.5 — Atlas is proposed
  5. TransferA resource can move; its RID does notThe registry commits a new binding and keeps the old one in history.An authorized administrator requests a transfer by RID. The registry verifies delegation and policy, prepares the new Locus, and commits the new binding. Resolvers then reach the same RID at the new location, with the old binding preserved in history.Source: Document 09 v1.1 §8.3; Document 08 v1.1 §9.4

Sources and provenance

Normative basis

This viewgraph is an informative explanation. Where it and the specifications differ, Documents 08 and 09 v1.1 govern.

What it contains

Document 08 v1.1 · normative
Grounded directly in Document 08, the controlling standard. Cited by section.
Document 09 v1.1 · reference implementation
Guidance from Document 09, the proposed reference implementation. Subordinate to Document 08; its technology choices are not requirements.
Interpretation
Explanation or design rationale written for this Learning Center. It does not add requirements.
Hypothetical example
An illustrative scenario. Its identifiers are examples or fictional; none has been issued.
Proposed, not operational
Something the specifications propose — a host, a prefix, a federation, a service — that does not exist yet.

Related

Pathway: Federation · For everyone · Revised 2026-10-09 · Content ID viewgraph.federation-across-spaces (a page identifier on this site, not an RID)