Reference
Versions, schemas and implementation status
Match package, source, schema and runtime coordinates without mistaking one version number for complete capability qualification.
Read version coordinates separately
| Coordinate | Meaning |
|---|---|
| SDK / MCP / AI Skills 129.0.0 | Coordinated package release used by the application. |
| Constitutional ruleset 127.0.0 | The retained ruleset coordinate, not a package rename. |
| Schema generations v120/v122/v125/v126/v127 | Installed schema families keep their exact canonical IDs and references. |
| Application build/source revision | The implementation being assessed or deployed. |
| Actual host/device capability | Its current admitted operation and qualified environment; not implied by a package install. |
Use exact installed exports
Use package.json exports, public declarations and actual implementation when selecting an API. Browser-safe root/React interfaces and Node-only compiler/subject/device tools have different environments. The historical V120 subject adapter and modern V122/V125 subject creation have separate contracts even when distributed in the same release. Do not invent a versioned import or rename a schema to match the newest package number.
Preserve old sources
An upgrade retains exact existing originals, unknown namespaces, source closures and pending recovery coordinates. A weaker response or changed UI cannot erase a previously admitted source. Current supported receiving and custody rules determine whether another action can be executed. If the next environment cannot admit the original, preserve it and report that exact compatibility refusal instead of replacing the identity, reissuing value or rewriting proof.
Check coordinated source and schemas
npm run release:check
npm run typecheck
npm run receiver:check
npm run buildThe build validates package/lockfile/installed/native source parity. Public schemas are copied byte-exactly with canonical IDs, references and digest metadata. A valid schema describes structure and reference closure; the actual enclosing artifact, identity and financial verifier supplies admission authority.
Read dated evidence in context
A stored verification record describes the exact build and observation it names. Current implemented connection/source code governs present capability; older records preserve their historical observations without qualifying a later host. Local fixture success, production service availability, a real credited payment and physical-device custody remain separate evidence. A release-preparation document is not proof of a published tag or deployed feature. Re-run the affected operation/refusal/recovery matrix and retain its originals when an integration changes.
Implementation sources
Inspect the exact path.
Source links retain revision 6c5d582. Read the documented operation and assessment scope alongside its code.