Compare releases

Compatibility

Compatibility

v125.0.0

Verify the enclosing artifact before extracting or trusting any embedded payload Proof-bearing KKSv1.0/KaiSigil coordinates and exact prior heads order authoritative appends Human-readable projection derived from Kai Earliest verified Identity Record/Seal Kai coordinate wins Projects the admitted original creation coordinate across profile, wallet, and World First admission only, then append forever; known proof paints immediately Append, compare-and-swap, distribution, indexing, replay, and recovery Authorized grantor binds the role; each event carries fresh actor proof Referenced proof objects are opened and verified before counting Deadline, predecessor lifecycle head, actor proof, evidence, and Kai causality are required Spendable proof-native Phi projected from sealed proof Named legacy funded rail One current owner, one spendable membership Coordinated exact 125.0.0 graph; compatibility range >=125.0.0 <126.0.0 Versioned lawful-action routes bind application identity and registered redirect origins Every non-2xx HTTP response rejects in SDK and MCP Known identity, ownership, media, and history paint without weaker hydration Package, database, deployment, Git, Docs, and attestation facts are recorded separately

v126.0.0

SDK, MCP and AI skills use 126.0.0; current integrations require >=126.0.0 <127.0.0. New admissions use the exact v126 registry; historical targets retain their original registry identities. Original bytes, creation coordinates, ownership history and registry digests remain unchanged. Existing versioned SDK exports, MCP tool identifiers, KKSv1.0 and Signature V4 retain their established names. The v126 schema directory binds the current registry while preserving established wire schema identifiers; v125 schemas remain available for historical records. @receiz/sdk/function-inventory exposes the full callable export catalog without adding that data to the universal runtime entry point. The additive registry successor migration is required before the existing hosted admission functions accept v126. Complete known published Showcase truth remains visible while a newer publication is pending.

Migration

Migration

v125.0.0: The SDK/MCP SQL compatibility migration is required only for hosts that applied the September 5 rollback. Production applied 20260905164450v125lawfulactiontransportrestore.sql: it restores the existing law-registration, action-admission, value-append and lawful-value-reader functions. It preserves stored source history and does not restore profile/PBI, creator, temporal-allocation or wallet-publication prerequisites. Do not replay the eight historical migrations below. See the [verified SQL record](v125.0.0-sql-compatibility-verification.json).

v126.0.0: On September 8, 2026, the release operator supplied SQL results confirming all three recent v126 migration outcomes are present: