Viewgraph · 5 frames
The complete RSM ID architecture
How the RID, RRN, Identity Record, registries, resolver, Semantic Space, and Locus fit together — and which of them hold identity, and which hold knowledge.
Viewgraph5 frames
Architecture
One identity system, not a fourth identifier
RSM ID is the integrated system. The RID identifies; RRN and RSN name; the registry preserves; the resolver connects.
RSM ID Learning Center
rsmid.org
Identity
Identifiers meet in the Identity Record
A referent gets one permanent RID; registered names and authority bind to it in one durable record.
Rendering diagram…
Issuance, names, lifecycle, authority, and bindings — not the resource body.
Resolution
The resolver connects identity to knowledge
A policy-aware resolver locates the authoritative Semantic Space; Locus serves its representations and relationships.
Rendering diagram…
The registry never becomes a content database. Knowledge stays with the Semantic Space that governs it.
Registry
Four logical registries, separately defined
They may share one implementation at first; their contracts stay distinct for future federation.
Globally unique RID prefix allocations.
Authenticated namespace controllers and delegated authority.
Permanent RID records and lifecycle mappings.
Semantic Space identities, capabilities, and resolution endpoints.
Reference implementation
One way to build it, not the standard itself
Document 09 proposes an API, a core library, and a federation adapter in front of three Locus nodes.
Rendering diagram…
Go, SQLite, and these components are Document 09's proposal. Document 08 controls the identity contract.
Read as text
- ArchitectureOne identity system, not a fourth identifierRSM ID is the integrated system. The RID identifies; RRN and RSN name; the registry preserves; the resolver connects.Source: Document 08 v1.1 §2.0
- IdentityIdentifiers meet in the Identity RecordA referent gets one permanent RID; registered names and authority bind to it in one durable record.A resource referent receives a permanent RID. The RID, a registered RRN, and a registered authority with its delegation all feed the RSM Identity Record, which is kept in the RSM ID registry.The record holds identityIssuance, names, lifecycle, authority, and bindings — not the resource body.Source: Document 08 v1.1 §2.0, §5.3.1
- ResolutionThe resolver connects identity to knowledgeA policy-aware resolver locates the authoritative Semantic Space; Locus serves its representations and relationships.The RSM ID registry is consulted by a policy-aware resolver, which locates the authoritative Semantic Space. An RSN names that space, and Locus serves its authoritative representations and relationships.Source: Document 08 v1.1 §2.0, §6.3, §7.3
- RegistryFour logical registries, separately definedThey may share one implementation at first; their contracts stay distinct for future federation.Prefix RegistryGlobally unique RID prefix allocations.Authority RegistryAuthenticated namespace controllers and delegated authority.Resource Identity RegistryPermanent RID records and lifecycle mappings.Space RegistrySemantic Space identities, capabilities, and resolution endpoints.Source: Document 08 v1.1 §5.2
- Reference implementationOne way to build it, not the standard itselfDocument 09 proposes an API, a core library, and a federation adapter in front of three Locus nodes.Applications, agents, and Atlas call the RSM Identity API and resolver, which uses the core identity library and a federation adapter. The adapter reaches separate RSM, Wellzai, and Musewoods Locus nodes.Source: Document 09 v1.1 §1.1, §1.2 — proposed; nothing here is deployed
Sources and provenance
Normative basis
- Document 08 v1.1 — Section 2.0RSM ID — system boundary and normative composition
- Document 08 v1.1 — Section 5.2Registry hierarchy
- Document 08 v1.1 — Section 6.3Logical resolution sequence
- Document 08 v1.1 — Section 7.3Identity and knowledge separation
- Document 09 v1.1 — Section 1.1Reference architecture
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.
- Proposed, not operational
- Something the specifications propose — a host, a prefix, a federation, a service — that does not exist yet.
Related
Pathway: Understanding Identity · For everyone · Revised 2026-10-09 · Content ID viewgraph.rsm-id-architecture (a page identifier on this site, not an RID)