Core implementer
Read all six in order. The later specifications assume the distinctions established by the earlier ones.
Normative specifications
From worldview
to executable proof.
These six documents are the normative foundation of the Regenerative Systems Model. They are rendered directly from the canonical Markdown in rsm/docs.
01Begin here · NormativeRegenerative Systems Model — A Living Outcome-Forming EcologyConcept Paper v2.0
docs/01-rsm-concepts-paper.mdRead02Depends on 01 · NormativeRSM Subject Model v1.0Regenerative Systems Map — Normative Conceptual Specificationdocs/02-rsm-subject-model.mdRead03Depends on 02 · NormativeRSM Semantic Model & Taxonomy Architecture v4.0Regenerative Systems Model — Normative Semantic Specificationdocs/03-rsm-semantic-model-taxonomy.mdRead04Depends on 03 · NormativeRSM Canonical Model & Protocol Specification v2.0Regenerative Systems Model — Normative Canonical and Interaction Specificationdocs/04-rsm-canonical-model-protocol-specification.mdRead05Depends on 04 · NormativeRSM Runtime & Federation Architecture v2.0Regenerative Systems Model — Normative Operational Architecture Specificationdocs/05-rsm-runtime-federation-architecture.mdRead06Depends on 05 · NormativeRSM Reference Implementation & Conformance Specification v2.0Regenerative Systems Model — Normative Executable Conformance Specificationdocs/06-rsm-reference-implementation-and-conformance.mdReadReading paths
Application developer
Concept, Subject, Canonical and Protocol define the objects and operations your application will encounter.
Integration engineer
Canonical and Protocol, Runtime and Federation, and Conformance define authority, disclosure, connectors and reconciliation.
Ontology author
Subject and Semantic Model define how meaning is extended without creating new kernel classes.