Negotiate the family you consume
| Identifier | Current documented value | Meaning |
|---|---|---|
Portable intent schemaVersion | 1.0 | Editable saved document |
Native policyRevision | planning-v1.1 | Explicit result-family negotiation |
| Result / snapshot / draw / edit schema | 1.1 | Accepted runtime and edit contracts |
| C ABI | 1 | Native function transport boundary |
| Navigation cycle | Per captured dataset | Dataset validity, not schema version |
| Weather revision / model run | Per captured source | Weather identity and freshness |
| Document commit / publication generation | Per document | Edit and publication ordering |
Intent 1.0 does not imply result 1.0. This site's examples negotiate 1.1 deliberately. Older app builds need to upgrade to adopt the current behavior; do not weaken a contract or flatten its states to make an incompatible reader appear supported.
Wire and semantic admission
Planning has strict unknown-field, duplicate-key, finite-number and time-precision rules. Use the owner validators; a JSON Schema check alone cannot establish seals, native input identity, occurrence ownership or scientific replay. Native hashing includes binary64 semantics. Do not reproduce it with arbitrary JSON text serialization.
The independent Python reader verifies the producer's retained contracts. Swift transports requests to the same native owner. A TypeScript type generated from a schema is not yet a conformant validator. A new reader must pass the positive and negative corpus, including numeric round trips, stale dependencies and unavailable states, before being listed as supported.
Release and migration policy
Keep prior released artifacts addressable. Content-addressed schema downloads preserve the
exact bytes and relative schema references; the reference index records their original $id.
The original schema identifier is not rewritten into a new authority during documentation build.
A changed contract requires an owner version decision, migration notes and consumer receipts.
If a client cannot read a version, reject it explicitly and preserve the original document for upgrade or export. Never silently reinterpret a pressure altitude, discard an unknown route component, or turn a missing metric into zero.