Compare releases

Compatibility

Compatibility

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.

v129.0.0

SDK, MCP and AI skills are published at exact 129.0.0. Public registry tarballs match the qualified candidates byte for byte; changing release prose does not repack or mutate published files. RECEIZ_APPLICATION_ID is the exact registered OIDC clientId: its unchanged native slug or rc_ followed by exactly 24 ASCII letters, digits, underscores or hyphens. Preserve case and bytes; no normalization, prefix removal, subject Receiz ID, username, secret or substitute alias is valid. Existing lowercase native slugs up to 128 characters retain their canonical syntax. Domain, operation and audience validators retain their own contracts. Existing registered clients and sealed coordinates require no rewrite. The forward compatibility migration changes only nine application CHECKs and five audited RPC predicates; scopes, active-client checks, revocation, replay, custody, locks and zero-write rejection remain binding. V129 inherits the exact v127 registry at docs/releases/v127.0.0-constitution-registry.json and digest 8d0b5b839d02d9efbd4306cc99410595a183705c2670b76d2567eaaaade99065. No new v129 constitutional registry or authority is created. Existing v120/v122/v123/v124/v125/v127 operation names, schemas and law identities retain their implemented meaning beneath the v129 distribution. Package versions do not rename protocols. Original sealed bytes, complete payload, Signature V4, full Kai-sigil and canonical offline verification remain authority. Valuation adds no proof-bundle field, signer/parser/verifier change or temporal setter; the separate Record correction composes the existing local anchor and preserves explicit anchors. Read the verified original full Kai-sigil or admitted original history before projection. A successor seal or caller evaluation cannot replace origin; ordinary legacy whole-pulse precision stays explicit and absent finer micro-pulses are never manufactured. Account entry remains frozen to 6e0d71c3f0e8b3092b4ec97eef39f5927667a01f. Existing Identity Seal, Receiz Key, PBI and recovered-account continuity compose through their established admission and binding primitives. Held verified identity, proof, membership, media, ownership and Showcase paint from stronger truth immediately. Background network/server/session work may append verified additions without replacing the settled surface. The full developer library has 356 tools, including supported financial operations. The ChatGPT Marketplace profile separately exposes 195 nonfinancial tools with its execution restrictions; neither profile enlarges issued grants or device-held custody. Private Identity Seal/account-Twin custody, identity-signed source/store publication, offline Note/Reserve and actual WebAuthn retain their trusted SDK host/device boundaries. Discovery of 704 exports does not make every object an arbitrary model argument or direct tool invocation. Default Record and wallet-note download preserve their actual sealed PNG bytes. Explicit Record JSON mode remains supported; public save/showcase headers describe remote effects only, and unknown delivery after a remote save forbids automatic retry. Canonical bearer admission verifies the enclosing artifact, executes the existing ownership coordinator and verifies the successor. Legacy SDK raw-token note-claim methods retain compatibility but gain no direct MCP adapter without an enclosing-note-bound projector. Existing intrinsic numerical law, sealed custom market reference, asking price and verified executed sale remain distinct. Versioned exact rarity arithmetic, policy digest and operands remain beneath sealed issuance and never authorize spending. Gifts have null payment. Completed sale requires independently verified payment and accepted delivery, the same asset/participants/intent and source-bound issuer state; missing historical joins remain unavailable rather than invented. Public value replay uses pinned canonical readers over exact carried public proof/history. Private identity/account/conversation bytes and old private recovery cannot be redacted into a new public authority artifact. Existing workspace restore and carried source history retain their supported composition. Selective disclosure, third-party transfer, connected-model acceptance and independently versioned Mind installers are not implied by generic verification or a package upgrade. The v128 baseline, all 46 carried commits, earlier release acceptance and failed aggregate records retain their exact coordinates. Academy, search, social artwork, tags and public verifier projections remain readers beneath proof, not substitute admission authorities.

Migration

Migration

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.

v129.0.0: A forward SQL migration is required for hosted deployments retaining the predecessor application-ID predicates. The exact migration 20261011204630_receiz_v129_registered_application_ids is already applied and independently verified in the recorded production project: nine updated application CHECKs, zero predecessor CHECKs and five exact RPC predicate replacements, with owner, ACL, configuration and SECURITY DEFINER metadata unchanged. This is application-coordinate compatibility, not an artifact or registry rewrite.