Evidence ladder
Every statement about use is placed on a four-step scale. The specification does not claim a step it has not reached.
| 1. Owner declaration | Stated by the specification's author; not publicly verifiable. Current level. |
| 2. Public case study | A named organization describes its own use in public. None yet. |
| 3. Verified implementation | A published implementation checked against the conformance clauses of Chapter 08. None yet. |
| 4. Independent validation | Review or conformance testing by a party unrelated to the author. None yet. |
Verifiable today
Published artifacts that any reader can count and check on this site or in the canonical repository.
| Core Vocabulary terms | 13, each with an HTML page, a canonical JSON record, JSON-LD and Markdown (Vocabulary) |
| Specification chapters | 9 (SPEC-00 to SPEC-08), compiled verbatim from the canonical repository (Specification) |
| Informative comparisons | 9 (Comparisons) |
| Reference Cases published | 1, distilled from real rollouts under NDA with the organization and details changed; non-normative (Implementation Case) |
| Architecture Observations | 58 recorded tensions in the model, AO-001 to AO-058, in the AO register on GitHub |
| Reference implementations published | 0 |
| Public case studies | 0 |
| Independent validations | 0 |
Declared, not verifiable
Owner declarations. They cannot be checked from public material and should be weighed with the author's interest in view; the essay discloses that interest.
| Production use | The specification's principles are applied in production settings under NDA. Those rollouts cannot become public case studies from the author's side, which is why public evidence must come from independent implementations. |