Compatibility and deprecation

Read the machine-verifiable matrix

cargo run -p pliego-cli --locked -- sdk compatibility --format json

The output conforms to pliego.sdk-compatibility-matrix.schema.json and records tested hosts, language toolchains, browser surfaces, tooling protocols, and deprecations. An integration is supported only at the boundary and version listed by that matrix.

Distinguish stability tiers

experimental

May change without a compatibility window and is never enabled implicitly

preview

Versioned and tested, with breaking changes allowed in a new preview protocol

stable

Preserves the contract for the documented compatibility window

Require an executable migration path

1. 01

   Publish

   Record the deprecated contract and its replacement in the matrix

2. 02

   Prove

   Give the replacement equivalent conformance coverage

3. 03

   Wait

   Keep at least one later OpenSDK protocol version before removal

4. 04

   Migrate

   Publish documentation and a diagnostic that identifies the replacement

Security fixes may disable unsafe behavior immediately, while the contract identifier remains visible with a security note until the next protocol release.

Keep the contract provider-neutral

The public compatibility authority is the celiumsai/pliegors repository: schemas, WIT packages, Rust types, fixtures, and conformance reports. A deployment product may consume those contracts, but no private service is required to implement or validate OpenSDK.