Compare releases

Compatibility

Compatibility

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.

v128.0.0

SDK, MCP and AI skills install at exact 128.0.0; supported major range >=128.0.0 <129.0.0. Package publication integrity is recorded independently. V128 inherits the exact v127 registry and digest 8d0b5b839d02d9efbd4306cc99410595a183705c2670b76d2567eaaaade99065; no v128 registry or production SQL migration is created. V120, v122, v123, v124, v125 and v127 operation names, schemas and law identities retain their implemented meaning beneath the v128 distribution. Existing source bytes, Signature V4, canonical document proof, native media carriers and offline verification remain authoritative; relabeling a package never requires resealing held truth. Entry stays frozen to 6e0d71c3f0e8b3092b4ec97eef39f5927667a01f. SDK-admitted recovery projects immediately; online recovery issues its existing fresh session cookie. Background imports cannot veto acceptance. Accepted recovered-account identity appends to the same existing subject through the established account relationship. The actual actor, root, predecessor and signature remain verified; original-device custody is not a universal prerequisite. Exact predecessor artifact namespaces retain existing legacy aggregates and original attempt identity. Signing enrichment never remints or replaces an Original. Held admitted identity, membership, media and visible shell paint without weaker discovery. Background work only enriches; unavailable hidden media cannot replace settled public truth. Prepared exact-current-state source is saved immediately; stale coordinates reject and click-time rebuilding does not replace the prepared source. Existing ownership, transfer, funded routes, Settlement and Reserve authority remain unchanged. V128 documentation and installation do not execute financial actions. Export carries complete included workspace history and evidence. Restore requires admitted owner and supported empty-runtime composition; selective disclosure, independent history merging and cross-owner transfer are not implied. Mind and MCP intelligence-source Crystals retain distinct reader contracts. The qualified Mind installer is independently versioned; generic verification is not universal import or sync. Reality Grade Infrastructure v1.2.0 uses published SDK128 and preserves its exact v1.1.0 signed inventory. Its 167-file owner-sealed disclosure attestation is distinct from application release evidence.

Migration

Migration

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.

v128.0.0: No SQL, registry or artifact rewrite migrations are required. This distribution inherits the exact admitted v127 registry and preserves wire identities, carried source bytes and established custody. Package adoption advances to >=128.0.0 <129.0.0.