Canonical & governance
Semantic resolver, identity, authority, policy, canonical repository and durable history.
Architecture
Build every architectural doorway now. Install specialized machinery only when it earns its place. RSM semantics stay stable while infrastructure evolves behind explicit ports.
Semantic resolver, identity, authority, policy, canonical repository and durable history.
Search, graph, spatial, temporal, vector and Biography views — rebuildable and non-authoritative.
Embedding, model and reasoning providers create Derived artifacts without crossing authority boundaries.
Protocol transport, discovery, selective disclosure, reconciliation and connectors across sovereign nodes.
Infrastructure serves the model
PostGIS≠Place
Neo4j≠Relationship
pgvector≠Truth
LLM≠Assertion
OIDC≠Authority
Kafka≠Event
Space + time
Place is foundational. PostGIS provides the initial spatial substrate while RSM keeps geometry, provenance, precision, validity and disclosure semantics explicit.
Valid time and recorded time remain separate so RSM can ask not only where, but where, when, and known as of when.
Architectural sockets
Initial adapters may all live in PostgreSQL. The contracts ensure graph, vector, model, broker or spatial infrastructure can be replaced without cutting through RSM Core.
Five milestones