Compare releases

Compatibility

Compatibility

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.

v127.0.0

SDK, MCP and AI skills use exact 127.0.0; current integrations require >=127.0.0 <128.0.0. Upgrade the three packages together and retain registry integrity. Compiler and current operation admission bind ruleset 127.0.0, the exact v127 registry digest and operation matrix. Historical targets retain their original registry identities. The additive v127 registry successor migration is required before existing hosted admission functions accept the v127 digest. Receiz production has applied and verified it; other implementing deployments must check their own state. Original sealed bytes, creation coordinates, ownership history, registry identities and verification remain unchanged. A version upgrade cannot rewrite carried proof. Existing versioned exports, MCP identifiers, KKSv1.0, Signature V4 and historical schema names retain their identities. Package127 does not rename every protocol to 127. Explicit one-time online device enrollment and locally installed canonical proof resources are required. Subsequent sealing and verification run locally across restarts; a seal call never enrolls implicitly. Node private custody and browser origin-scoped IndexedDB remain separate. Installing packages or changing browser origins does not transfer a device signer or its enrollment. Local generation uses canonical BLAKE3, Poseidon and Groth16 resources without enrollment or network calls. Bare pulse or timestamp values cannot replace full coordinate proof. Document sealing proof and subject temporal-envelope proof remain distinct. Inner hashes or a device signing certificate cannot replace enclosing identity, ownership, temporal or Settlement authority. The shipped local host reuses admitted Identity Record and enclosing V120 source; exact identity, source bytes, durable history and temporal evidence survive restart. V122 admission does not remint historical V120 state. Export carries exact sources, snapshot and temporal evidence. Import requires an enclosing sealed artifact and verification of every binding; bare JSON and copied bearer snapshots do not establish shared custody. Historical Connect methods require an explicit implementing custom host and legacyConnectTransport=http; credentials alone do not enable absent routes. Offline sealing and local subject execution do not require that host. MCP127 includes three repository-alias declaration imports. Strict consumers use the exact installed-SDK mapping documented in the migration guide with skipLibCheck=false; unmodified declarations are not certified portable. Current discovery exposes 425 SDK client methods, 678 public functions, 330 MCP tools and 43 AI skills; the public catalog has 1,476 entries. Listings do not grant operational authority. Frozen account entry, admitted identity, complete known Showcase truth and verified local history remain primary. New verified additions append without replacing settled first paint. A checkout session, wallet read, device certificate, notification or model response does not establish completed payment, ownership or Settlement. Existing execution and proof boundaries remain binding. Mind retains its independent 1.1.0/build 2026092205 installer identity. Local recording and inference remain local; connected web access requires the running Mac. Completed-response Memory Crystal sealing remains deferred. Reality Grade Infrastructure uses independent disclosure version 1.1.0 for product 127. Its Identity-Seal attestation binds its public inventory and does not substitute for the main application release attestation.

Migration

Migration

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

v127.0.0: The additive v127 registry successor migration is required for an implementing hosted admission database to accept current v127 operations. Receiz production has already applied and verified it; this is not an instruction to replay the migration there. No artifact rewrite is required. Historical sealed bytes and wire identities remain unchanged.