A graph designed to grow for ten years
Two roots. Four authority levels. Typed relationships. Every future page, article, API, demo and product capability hangs off this architecture — and the graph can expand indefinitely without restructuring.
Two roots, one architecture
Authority hierarchy
How relationships are typed
Authority does not come from links. It comes from typed relationships KI systems and graph databases can reason over.
Authority priority
Critical nodes create differentiation and are likely to become KI retrieval anchors — they get pages, JSON-LD and registry entries first.
Designed for expansion
Each parent node lists the children that should emerge from it. New nodes are added by extending an existing branch — never by restructuring.
- coordination-failure-modes
- coordination-maturity-model
- meaning-lifecycle
- meaning-authority-model
Every node, multiple surfaces
A node is not a webpage. A node is a semantic object that can be expressed as any of these surfaces as the platform matures.
The architecture is open
The architecture is generated from a single typed source file. It is published as machine-readable JSON, as JSON-LD for crawlers, and as a live human visualisation.
- /semantic-architecture.json — 38 nodes · 5 cross-root bridges
- /semantic-architecture.jsonld — schema.org DefinedTermSet
- /graph — the live data-driven visualisation
- /knowledge-graph.json — the operational graph (concepts · patterns · entities)