Pathway D of 5

Federation

How do independently governed spaces share identity without sharing a database?

Semantic Spaces, Locus, Atlas, cross-space references, provenance, and why similar descriptions never merge identities on their own.

Steps

  1. Journal

    From Identity to Federation

    A concept in the RSM space, a research paper in Wellzai, and a fieldnote in Musewoods reference each other without sharing a database. This Journal follows that chain through citation, exploration, transfer, and restriction to show how persistent references, provenance, and authority let federation work.

    Technical · Document 08 v1.1 — Section 4.4 and 15 more

  2. Seednote

    Semantic Space

    An independently governed logical knowledge environment, with its own RID and RSN.

    For everyone · Document 08 v1.1 — Section 2.6 and 3 more

  3. Seednote

    Locus

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

    Technical · Document 08 v1.1 — Section 10.2 and 3 more

  4. Seednote

    Atlas

    The proposed explorer of federated Semantic Spaces.

    For everyone · Document 08 v1.1 — Section 10.3 and 2 more

  5. Seednote

    Federation

    Independently operated Semantic Spaces connected by shared identity and resolution.

    For everyone · Document 08 v1.1 — Section 10.1 and 3 more

  6. Seednote

    Provenance

    The recorded origin and history of an identity, a name, or an assertion: who did what, under which authority, and when.

    For everyone · Document 08 v1.1 — Section 12.1 and 4 more

  7. Viewgraph

    Federation across Semantic Spaces

    How RSM, Wellzai, and Musewoods are proposed to share identity without sharing storage: cross-space references by RID, Atlas traversal, and transfers that keep the RID.

    For everyone · Document 08 v1.1 — Section 7.4 and 8 more

  8. Fieldnote

    Why semantic equivalence is not identity equality

    Why RSM ID never merges identities on similarity, sameAs claims, or shared source files — and what an authorized equivalence decision needs instead.

    Technical · Document 08 v1.1 — Section 10.5 and 4 more

All pathwaysNext: Pathway E, Real-World Applications