Knowledge Observatory

Observatory

What this is

Not a decorative map, a place to inspect the state of the knowledge model. Health first; then map, explorer, retrieval inspector and per-term inspect.

Graph health

Core terms13
Relationships83
Broken links0
Orphan nodes0
Duplicate identities0
Governance candidates7
Mutual reference pairs35
Missing reverse references13
Core Vocabulary projection coverage100%

Mutual reference pairs are terms that reference each other, recomputable from graph.json; informational, no threshold. The cycles count (44) had no published counting rule and the generator that produced it no longer exists, so it is carried forward in health.json from 7 September 2026 and is not recomputed; it is not shown in this table. Missing reverse references are one-directional references, listed in health.json; informational, no threshold. Core Vocabulary projection coverage (formerly labelled Publication coverage) is the share of the 13 Core Vocabulary terms carrying all four projections, not a share of the repository: the tiers listed in health.json under unprojectedTiers (Core, Domains, Entities, Lifecycles, AI, Reference Architecture, most of Models, most of Memory, most of Language, Governance) are read on GitHub.

Projection parity

Specification HTML = JSON = Markdown: version 1.0, 9 chapters, identical chapter identifiers
Core Vocabulary 13 terms: HTML, JSON, JSON-LD and Markdown agree on definition, version and document identifier
Comparisons 9 records: HTML and JSON agree on summary, identifier and status

Checked after every build: health.json, projectionParity.

Publication health

Core Vocabulary term pages 13 checked Every term has an HTML page.
Core Vocabulary JSON records 13 checked Every term has a canonical JSON record.
Core Vocabulary JSON-LD 13 checked Every term has a standalone JSON-LD alternate.
Core Vocabulary Markdown 13 checked Every term has a Markdown projection.
Explain records 39 checked Every term resolves under all three of its identifiers.
API term records 13 checked Every term has an api/v1 record.
API neighbor records 13 checked Every term has an api/v1 neighbors record.
Inspect pages 13 checked Every term has an inspect view.
Comparison records 18 checked Every comparison has an HTML page and a JSON record.
Machine entry points 25 checked The discovery, manifest and index files are published.
Citation parity 52 checked The recommended citation is byte-identical in the HTML block, the JSON record, the JSON-LD node and the Markdown projection.
Ownership record 20 checked The publication publishes one Ownership assignment carrying the five properties Meta/Ownership.md requires, and every record that carries an ownership block points at that assignment and no other. This row does not assert that every published record names an owner: coverage is partial at this stage: the 20 records this check reads are the ones it can enumerate from the site's own indexes, and the per-term and per-operation projections inherit the block from the record they project.
Coined names resolve 8 checked Every name the published graph coins in its own namespace expands to a URI whose document defines it, so a machine client that expands the JSON-LD is not handed a type or a property that answers with nothing (`CAND-019`).
Resolver coverage 162 checked Every identifier registered in resolve.json has both an HTML resolver stub and an api/v1/resolve record.
Printed identifier coverage 65 checked Every identifier this site prints, in a labelled identifier field of a published page or in an identifier field of a published JSON record, is registered in resolve.json, so no identifier this site prints answers with not found.
Rendered figures match their records 18 checked Every count the /observatory page prints for a publication-health row, and the identifier count printed on /resolve, equals the figure in the record the page renders.

Computed over every published file in each class, not a sample, and recomputed on 2026-10-01: the total this sentence once stated was carried forward from a run nothing repeats, so it says the date the record carries instead. The rule each row applies is printed beside it. Record: publication-health.json.

Validation reports, regenerated with the site: graph-validation-report.txt, specification-validation-report.txt, vocabulary/validation-report.txt.

Machine views: health.json · publication-health.json. These invariants are the first thing to check after every build.