RSMONE

Regenerative Systems Model

One shared model.
Many sovereign systems.

RSM is open semantic and operational infrastructure for systems that need to discover, reason, commit, coordinate, observe and learn across organizational and ecological boundaries.

Explore the specifications ↗See how RSM works
6 normative specifications1 governed semantic model∞ extensible domains
PersonOrganizationCommunityLiving systemPlaceMaterialFormationInstrumentDigital agentOutcomeRSMshared meaning
MeaningAuthoritySpace + timeOutcome
Semantic modelCanonical stateProtocolRuntimeFederationConformance

Why RSM

Real outcomes do not live inside one application.

RSM exists because real outcomes do not form inside one application, one workflow engine, or one organization. They form across a living ecology of people, places, institutions, materials, instruments, capabilities, commitments, observations, evidence, and learning.

A different foundation

Designed around the distinctions that matter.

RSM is intentionally small at the core and rich at the edge. Its job is not to encode the whole world. Its job is to keep meaning, authority, possibility and consequence from collapsing into each other.

01

Meaning before matching

RSM gives independently governed systems a shared semantic grammar before asking them to coordinate.

02

Authority before action

Possibility, recommendation and projection remain separate from commitment, formation and canonical state.

03

Space + time are native

People, places, living systems, materials, capabilities and outcomes can be understood in geographic and temporal context.

04

Federation without surrender

Participants remain authoritative for their state while interoperating through common semantics and protocol.

05

Intelligence without privilege

Graph, vector and model systems can reason broadly without acquiring canonical authority.

06

Proof over promise

Conformance is executable: valid transitions succeed and invalid semantic collapses must fail.

From possibility to consequence

RSM preserves the whole outcome-forming lifecycle.

Desire is not outcome. A candidate configuration is not a formation. Activity is not proof of consequence. The lifecycle keeps those transitions visible.

01Intent
02Discovery
03Configuration
04Gap
05Pathway
06Commitment
07Formation
08Activity
09Observation
10Outcome
11Biography
Derived / reasoning Canonical / reality boundary

The normative foundation

Six documents. One architecture.

The specifications progress from worldview to executable proof. Each owns a distinct architectural boundary and later documents depend on, rather than redefine, the earlier ones.

01
Normative

Regenerative Systems Model — A Living Outcome-Forming Ecology

Concept Paper v2.0

docs/01-rsm-concepts-paper.md↗02
Normative

RSM Subject Model v1.0

Regenerative Systems Map — Normative Conceptual Specification

docs/02-rsm-subject-model.md↗03
Normative

RSM Semantic Model & Taxonomy Architecture v4.0

Regenerative Systems Model — Normative Semantic Specification

docs/03-rsm-semantic-model-taxonomy.md↗04
Normative

RSM Canonical Model & Protocol Specification v2.0

Regenerative Systems Model — Normative Canonical and Interaction Specification

docs/04-rsm-canonical-model-protocol-specification.md↗05
Normative

RSM Runtime & Federation Architecture v2.0

Regenerative Systems Model — Normative Operational Architecture Specification

docs/05-rsm-runtime-federation-architecture.md↗06
Normative

RSM Reference Implementation & Conformance Specification v2.0

Regenerative Systems Model — Normative Executable Conformance Specification

docs/06-rsm-reference-implementation-and-conformance.md↗

Architecture

Canonical meaning at the center. Specialized infrastructure at the edges.

PostGIS does not define Place. A graph database does not define Relationship. A vector index does not define truth. An LLM does not define authority. Every technology serves the Model through explicit ports.

Explore the technology architecture ↗
SearchGraphSpatialVector
FederationReasoning
RSMcanonical
meaning

For developers

Build on RSM. Do not build around it.

Application / Agent / Connector
        |
        v
     RSM Protocol
        |
        v
   Runtime Services
        |
        v
 Canonical + Semantic Core
Developer starting point ↗

For integrators

Keep your systems. Share enough meaning to coordinate.

Connect an ERP, LIMS, farm-management platform, certification system or agent through explicit identity, semantic mapping, provenance and protocol boundaries.

Existing system↔RSM Connector↔RSM Network
Integration architecture ↗

RSM One

One interoperable model for many independently governed systems.

Start with the why. Follow the architecture. Prove the implementation.

Read the normative specs ↗Start building