Compatibility
Compatibility
Record verified compatibility rules and supported evolution practices.
Status: Partial implementation reference — Code-confirmed; operational validation pending
Last reviewed: 2026-10-19
Scope
Versioning, supported combinations, breaking changes and migration expectations. The source-confirmed baseline below covers part of this scope; remaining operational details are unknown.
Current implementation baseline
Shared protocol/kind copies and protocol manifests are packaged into several Workers. Their local check scripts detect drift; Corpus additionally checks generated schema validators and published schema digests. These mechanisms do not prove that every deployed Worker uses the same revision.
Exact payload schema versions are immutable. Explicit public operation IDs protect SDK method names. Strict SDK synchronization requires lineage-aware snapshots/feeds and state version 2; legacy stores are retained and rejected. Archive import is opt-in, with feed fallback in auto mode where safe.
Evidence: Corpus protocol, schema checker, operation IDs, SDK generator and continuity runbook. Coordinated migrations, publication and SDK refresh require independent release validation.
