SaSameKnowledge
Search knowledge⌘KStart with SaSame
publisheddocumentationdocumentation

How is the SaSame Knowledge Platform structured?

Knowledge, runtime and publication boundaries.

Collection
documentation
Updated
2026-07-30
min read
2
Version
v1
Verified summary

One canonical Knowledge Database feeds the website, search, API, MCP, Markdown projections and future PDF outputs through versioned adapters.

01

Canonical knowledge

Documents, versions, relations, authors, citations, papers, observations, tags, categories and languages share one versioned model.

02

Projection model

Markdown is an editable projection. HTML, search indexes, API responses, MCP results and PDFs derive from canonical knowledge.

03

Release isolation

Development is independent. Production changes only through a verified blue/green switch with rollback evidence.

EX

Examples

2
  1. 01

    A paper relation surfaces supporting evidence, documentation and learning material.

  2. 02

    The admin publishing flow in Publishing writes to a separate external runtime state, which every release reconciles back against this canonical database rather than treating the two as independent sources of truth.

RF

References

1
NX

Continue exploring

4
research01

Research

SaSame publishes methods, measurements, datasets and papers about the registry-runtime gap and the operational MCP ecosystem, with limitations and provenance preserved.

evidence02

Evidence

Evidence records what was observed, when, how and with which limitations. It does not automatically prove safety, quality, ownership or endorsement.

api03

API

Use the read-only Knowledge API, search endpoint or MCP retrieval tools, all backed by the same document and relation model.

archive04

Archive

Historical products, architectures, pricing and research are preserved with explicit lifecycle labels so the record remains auditable without confusing it with the current model.