Adopt one explicit contract at a time
- Choose the family in the catalog, including its maturity and owner.
- Identify whether your client reads, writes, evaluates or renders the object.
- Pin the family version and retain the original source bytes where the contract requires it.
- Run the owner's valid and invalid corpus through the actual reader or writer.
- Test persistence, asynchronous ordering and resource expiry in your host.
- Record the supported operations and release receipt before enabling writes.
Planning clients
Use intent 1.0 with negotiated 1.1 results. Keep native key generation and edit admission centralized. Save with a coordinator, publish snapshot and draw atomically, and reject stale work. Native execution currently requires a source build or an existing host integration; there is no public package-manager SDK or general HTTP planning endpoint promised here.
Older app builds must upgrade to adopt current behavior. Preserve incompatible documents for upgrade or export; do not erase fields to force acceptance.
Navigation, weather and track clients
The existing owner types and adapters are the starting point. The shared library catalog provides consistent vocabulary and records known gaps. A family marked internal or audited needs a concrete portable-contract and consumer validation pass before interoperable writes are advertised. Documentation publication alone does not migrate these clients.
Consumer receipt
Record family/version, reader/writer operations, source revision, validator command, fixture revision, tested runtime and any lossy conversion. A generated binding without runtime and round-trip evidence belongs in an experimental row, not a supported SDK table.