Documentation · Verification
Verification closes the definition, not the world
Source manifests, schemas, corpora, formal bindings, content identities, and deterministic artifacts verify one tracked Candidate definition.
What the repository closes
Verification checks the tracked semantic source manifests, active protection profile, stable claims and required modeled-proof bindings, positive and negative capability corpora, non-circular content identities, and deterministic artifact generation as one closed graph.
Where evidence lives
| Path | Role |
|---|---|
spec/ | Canonical schemas, registries, policies, bounds, lifecycle, and source manifests. |
conformance/ | Synthetic positive and negative definition-level cases with requirement coverage. |
formal/ | Declared ideal-model proof sources and bindings under recorded assumptions. |
artifacts/ | Deterministically generated Candidate bundle projection. |
Evidence has a precise limit
A passing source-integrity suite does not prove SDK implementation, Provider behavior, device custody, cross-language interoperability, external audit, package release, publication, deployment, support, or operation. Those claims require independent evidence in their owners.
No private implementation projection. This public documentation does not identify or link private SDK work, local receipts, accounts, environments, or operational systems.
Review the exact source
For a material claim, follow its chapter source link and inspect the canonical file at the selected repository revision. The human-readable pages help navigation; they do not supersede machine authority.