Seednote

Locus

The proposed engine of a Semantic Space

The proposed engine that serves authoritative resource knowledge for Semantic Spaces.

RSM ID Learning Center2 min read

Locus is a proposed lightweight semantic engine that can operate a Semantic Space. It stores resources, metadata, relationships, revisions, and provenance, and it evaluates policy and federates as its deployment profile requires. What it does not do is define identity: a conforming Locus consumes the RID, RRN, RSN, and resolution contracts supplied by RSM Core.

That separation keeps the system honest. Knowledge stays with the space that is responsible for it, served by whatever engine runs that space; identity stays with the registry and its shared rules. A space can change engines without changing a single identifier.

Example

In that demonstration, the Wellzai node keeps the Outcome Formation Model paper and its revisions. When the paper is edited, Locus records a new revision; the paper's RID does not change. If the Musewoods node moved to a new endpoint, the registry would record a new binding and every reference by RID would keep working.

A common misconception

“Locus is the Semantic Space.” Locus is the building; the space is the institution. A space is a governed logical resource with its own RID and RSN, and the Locus process serving it is a binding that can change.

Locus operates a Semantic Space. Atlas explores across many Locus-served spaces. Together they make federation practical.

In the specification

Locus responsibilities: Document 08 §10.2. Identity and knowledge separation: §7.3. Language independence: §12.2. Proposed topology: Document 09 §8.1.