Graph health
| Core terms | 13 |
| Relationships | 83 |
| Broken links | 0 |
| Orphan nodes | 0 |
| Duplicate identities | 0 |
| Governance candidates | 7 |
| Mutual reference pairs | 35 |
| Missing reverse references | 13 |
| Core Vocabulary projection coverage | 100% |
Mutual reference pairs are terms that reference each other, recomputable from graph.json; informational, no threshold. The earlier cycles count (44) had no published counting rule and is retired from 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 0.2, 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 | 17 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 | 30 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, 30 of 191 published JSON records carry the block, and the per-term and per-operation projections inherit it from the record they project. |
| Resolver coverage | 158 checked Every identifier registered in resolve.json has both an HTML resolver stub and an api/v1/resolve record. |
| Printed identifier coverage | 58 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. |
Computed over every published file in each class, not a sample: 463 files checked on 2026-09-07. 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.