Core implementer
Read the corpus in metadata order. Later specifications assume the distinctions established by earlier ones.
Normative specifications
From worldview
to executable proof.
The RSM specification corpus is rendered from the canonical Markdown source and governed metadata. The page frames the corpus; the index below is discovered from first-class specification objects.
SPECIFICATION CORPUS
The governed RSM corpus.
Each specification owns a distinct architectural boundary. Later documents depend on, rather than redefine, the earlier ones.
01
Normative · v2.0
docs/01-rsm-concepts-paper.md↗02Regenerative Systems Model — A Living Outcome-Forming Ecology
Concept Paper v2.0
Draft normative · v1.0
docs/02-rsm-subject-model.md↗03RSM Subject Model
Regenerative Systems Map — Normative Conceptual Specification
Draft normative · v4.0
docs/03-rsm-semantic-model-taxonomy.md↗04RSM Semantic Model & Taxonomy Architecture
Regenerative Systems Model — Normative Semantic Specification
Draft normative · v2.0
docs/04-rsm-canonical-model-protocol-specification.md↗05RSM Canonical Model & Protocol Specification
Regenerative Systems Model — Normative Canonical and Interaction Specification
Draft normative · v2.0
docs/05-rsm-runtime-federation-architecture.md↗06RSM Runtime & Federation Architecture
Regenerative Systems Model — Normative Operational Architecture Specification
Draft normative · v2.0
docs/06-rsm-reference-implementation-and-conformance.md↗07RSM Reference Implementation & Conformance Specification
Regenerative Systems Model — Normative Executable Conformance Specification
Implementation · v1.0
docs/07-rsm-technology-infrastructure-architecture.md↗RSM Technology & Infrastructure Architecture
Regenerative Systems Model — Implementation Architecture
READING PATHS
Choose the path that matches the boundary you are working on.
These are reading guides only. The authoritative sequence, labels, versions, statuses, and routes come from specification metadata.
Application developer
Start with the conceptual, subject, canonical, and protocol boundaries your application will encounter through RSM APIs and projections.
Integration engineer
Focus on authority, disclosure, connector, protocol, federation, and reconciliation boundaries.
Ontology author
Follow the subject and semantic foundations before extending domain meaning.