ReceizAcademy

Structured comparison · not a Markdown diff

Compare releases

See exactly what changed across capability, primitive, compatibility, migration, registry, and independent evidence boundaries.

From

v129.0.0

Reality-Grade Infrastructure

Authority & EvidenceClaim sources and exact digests
titleClaim SHA-256 0ad770bffc747e0c4f29ba3f5b73f87bf88afa9134d2c487c36597d2c1576616
docs/releases/v129.0.0-product-truth.mdSHA-256 b98689f5b39e13773ade608e88735feff4f13cf5410757ca38322da628870fbcdocs/releases/v129.0.0.mdSHA-256 9be3f96df9f49e857ecdf33955d56deaed9ffe52b4b02fe5683aed4a5077b780
To

v129.5.0

Reality-Grade Infrastructure

Authority & EvidenceClaim sources and exact digests
titleClaim SHA-256 0ad770bffc747e0c4f29ba3f5b73f87bf88afa9134d2c487c36597d2c1576616
docs/releases/v129.5.0-product-truth.mdSHA-256 e0b2eaf669e5f443a131badafd601d657c8004b40fabd14b31e4aa024ee36553docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Structured outcome

Capability change

Before

The actual thing remains the terminal authority through time. Receiz v129 carries exact registered applications through the existing proof-native SDK, MCP and production bindings, exposes the full financial library under actual grants and consent, and releases offline Kai-sigil valuation with verified transaction history, deterministic charts, bounded rarity policies and reproducible public replay. It coordinates published SDK, MCP and AI libraries with the complete developer capability map and carries every source change since v128. Proof objects, their exact Kai-sigil origins and verified history remain authoritative; developer and model projections cannot replace source or manufacture ownership, Settlement, intrinsic value or executed sales.

Authority & EvidenceClaim sources and exact digests
summaryClaim SHA-256 64b288e614a1cd9a366b58e14a6664ed25064db4db0cd5a5eedccf7a92584b99
docs/releases/v129.0.0-product-truth.mdSHA-256 b98689f5b39e13773ade608e88735feff4f13cf5410757ca38322da628870fbcdocs/releases/v129.0.0.mdSHA-256 9be3f96df9f49e857ecdf33955d56deaed9ffe52b4b02fe5683aed4a5077b780

After

The actual thing remains the terminal authority through time. Receiz v129.5 preserves the same proof object through identity recovery, durable local custody, authorized history appends, public Showcase, market inspection, financial records, native files and independent verification. It consolidates the complete post-v129 source arc: Crystal custody and native execution components; Account financial Originals and connected Notes; public earning, portfolios and merchant Counter; Calendar offers and paid meetings; scoped Twin/World tools; Receiz-ID email in Messages; exact creator, Profile and collection continuity; signed native Original downloads; and the coordinated security, dependency and verifier-consumer corrections.

Authority & EvidenceClaim sources and exact digests
summaryClaim SHA-256 1e2b7d5065a42cd3313429689cd8bd82d50b233f1e849670567f4cfc11d112bc
docs/releases/v129.5.0-product-truth.mdSHA-256 e0b2eaf669e5f443a131badafd601d657c8004b40fabd14b31e4aa024ee36553docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Primitive continuity

Primitive continuity

Added

provenance · media · local-truth · market · certificate · note

Retained

proof · identity · ownership · settlement · transfer · verification · public-witness · continuity · reserve · sealed-artifact · governance

Not carried in target projection

None

Authority & EvidenceClaim sources and exact digests
primitivesAffectedClaim SHA-256 09ea8c1ead8dd5f7b2809159182374735a0847452502389e9b0360e552d02288
docs/releases/v129.0.0.mdSHA-256 9be3f96df9f49e857ecdf33955d56deaed9ffe52b4b02fe5683aed4a5077b780
Authority & EvidenceClaim sources and exact digests
primitivesAffectedClaim SHA-256 53ae696db4dc42c3521fa313d9ef89af9d67a4cf5cf860fabe044115876af038
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Compatibility

Compatibility

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.

Authority & EvidenceClaim sources and exact digests
compatibility.0Claim SHA-256 282da082e4ba512e3bc7c8ef2305ebf88056590fd2fd3d46c33cb8584d4fbbbe
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.1Claim SHA-256 376ee0e6ea3b82ddb6e8165b1909a913e7052e1eec6eff919cbcf53038c18385
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.2Claim SHA-256 5fab8ccc33ac5f70550b9440f8589a5613391e31a069d581e0756224d631f702
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.3Claim SHA-256 4887ca557200f0af78ff14d95187435a2cb7a38972c60c8721f40702cafb5ae4
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.4Claim SHA-256 6214faccfff02fae15dad33b20ea78a2e786af51eb4a14f3c3f23431e1b254ef
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.5Claim SHA-256 fdfcbc62373bf32fa0a61897169086029edc3149378afb9f48618c6a9fdc3260
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.6Claim SHA-256 7a98b82971bccc61cc867d5d00ae77e2fabfe683c8d09086c917e857f499e8c3
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.7Claim SHA-256 b34dd6d1a9bf48489ac569dfb12607e134e1ffa814af96c8731222daf7cad1f4
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.8Claim SHA-256 febc1dd5a2286256ad856284f122bf4d2dfb2e7580f6bd8d88bda3cf4a284fdd
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.9Claim SHA-256 c3fd6c605336dc7e3d8a3a35c2c723f8b74d6b3ba6dca3c45f8687da04a957d7
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.10Claim SHA-256 d6959abf42a8422e91202611b84383c8abc2e7b0282666360ba5faf93e6a7724
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.11Claim SHA-256 6afdc3f4f43754d14c99c981eddf3a549830cff55dc6f80b78095c6bb899a6e0
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.12Claim SHA-256 040e6d3fdba19fbde71bdcb1d94a2d6fb0abb818334f7defde8e0064c4c39740
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.13Claim SHA-256 12fcdb76b640ebed021aaf62a2af04965de524923d19d77793a5aa2923fbe308
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.14Claim SHA-256 589dd9f6429127545cf89a97d1b3e6f52a0cdb0bb498a221fb31181ed242713b
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.15Claim SHA-256 75b15b2f59324a79f1022f45b5a1ebe6b34f767df61e6b319ab096e4fefe7fc8
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.16Claim SHA-256 4d101b50b4d719218ca75d1816a03681934b84331f01b9e5e4ccf9085956a0d7
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.17Claim SHA-256 8d418da8008986513a4001bcf17be39b109ce4f1fb6c6aa4e7828d0cb12aea63
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970
compatibility.18Claim SHA-256 56cb276fcbc152b4a5dafbf6cf893ed4f9128eaf9d704b47e1206e4c714f350e
docs/releases/v129.0.0-compatibility.mdSHA-256 44f37255e8e9acade15073031ea5d535f41cb6bc215dc0a1da7b7deb205f9970

v129.5.0

Install exact @receiz/sdk@129.5.0, @receiz/mcp-server@129.5.0 and @receiz/ai-skills@129.5.0 together. Their registry archives match the qualified archives byte for byte. See the [publication receipt](v129.5.0-package-publication-evidence.json). The declared range stays >=129.0.0 <130.0.0. This release does not activate v130 or rename historical operation/schema versions. The admitted 133-law v127 registry remains byte-identical, digest 8d0b5b839d02d9efbd4306cc99410595a183705c2670b76d2567eaaaade99065. No new constitutional issuer or ruleset is introduced. The admitted digest remains c4e0cff348b62f31db2bb2ffdeec533a92ca3a6d476757bb9b559ac58a7875e1. Inventory expansion and distribution versioning cannot enlarge an operation's authority. Existing file carriers, sealed payloads, Signature V4 roots/certificates, Groth16 checks, fixed Kai-sigil origins and ownership/provenance history retain their implemented interpretation. Resource-capacity refusal means validity was not evaluated; it is not an invalid-proof verdict. An authorized signature appends to the same Original and its predecessor-bound history. Export retains the existing signed successor and exact native carrier; downloading does not reseal, reconstruct a display record or manufacture another signature. Complete admitted local truth is used immediately. Global acknowledgement cannot erase local Original/media custody or replace a stronger held successor with a partial response. Missing delivery is a transport outcome, not evidence that an admitted object ceased to exist. The account-entry freeze remains bound to 6e0d71c3f0e8b3092b4ec97eef39f5927667a01f. Receiz ID, PBI/passkey recovery and admitted device bindings retain their established identity boundaries. The chosen Receiz ID is the public creator/profile coordinate; the signed device identifier remains its associated signing evidence. Existing historical locators retain compatibility without rewriting the sealed creator or dropping characters from current display. A renamed current profile does not rename past artifact bytes. Preserve the exact Receiz-issued application ID, spelling and case. A default profile name, device ID or stripped alias is not an application coordinate. Existing issued grants, audience, owner, nonce, replay, revocation and confirmation checks remain binding. Profile, Showcase, collection and discovery readers project admitted public source membership. A subordinate saved representation cannot authorize omission, restore hidden membership or roll an accepted successor backward. Current membership and creator display do not rewrite historical market prefixes, source basis, issuance or valuation origin. Retained prefix checks protect genuine history; they are not an independent publication authority. The current inventory has 705 callable SDK exports, 425 client methods, 356 full MCP tools, 43 skills, 37 manifests and 34 prompts. An inventory entry does not create an adapter, transfer private custody or grant permission. The separately governed ChatGPT profile remains 195 nonfinancial tools. Full-library documentation cannot enable an excluded tool; a restricted installation cannot redefine the full supported SDK/MCP library. Funding, Settlement, Reserve, quote, payment, accepted delivery, ownership claim, completed sale and seller proceeds remain distinct evidenced stages. A listing, chart, checkout session, receipt projection or hash match cannot establish an unexecuted stage. The existing qualified-device custody and once-only consumption contracts remain intact. No recipient-name-only anti-rollback substitute is introduced. Source history and currently spendable custody are distinct checks. KKS/Kai and the admitted full Kai-sigil origin retain causal authority. Chronos labels are presentation. Caller-selected evaluation coordinates, intrinsic value, asking price, market reference and executed sale remain separately typed. Standalone verifier, Offline Studio, installed SDK and Docs Workbench consume the canonical runtime at their declared source coordinates. Current distribution labels do not amend historical proof roots or older release evidence. Service security checks apply to their real operator, challenge, request and network boundaries. They introduce no mandatory server, enrollment allowlist or vendor issuer for native local PBI signing. The separate enterprise-enrollment finding retains its precise open scope in conformance. Package installation does not activate unfinished Crystal financial/hosted composition, apply schema changes, switch production custody providers or establish live acceptance. Existing source/storage selection remains explicit. Earlier release notes, failed/passed receipts, attestations, registry archives, tags and source captures remain immutable. A later success is a new receipt at its exact coordinate.

Authority & EvidenceClaim sources and exact digests
compatibility.0Claim SHA-256 24f8c79e3e3e547ddb3d1697fcb0b9760da7b4c1bafcc8b0a3bebfeab6e39d79
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.1Claim SHA-256 e21993f88c6c9efb34572fd196a4ea034c1c11422d6d04cef102ee75d1c8246a
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.2Claim SHA-256 572f77fa467d13ee9ccfd9395a3f8d5c8bf1ae80f3c3108c49921379ff912875
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.3Claim SHA-256 94a694b27cf376122a07429dcb1bf9f922168eff38bdb225ca981206682ce8f9
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.4Claim SHA-256 d24a918d764f2716d31b50bb8d1439eb4854f98556b85d6c6cf924460cb815f3
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.5Claim SHA-256 e08b7d4928ee29733d171b2298af618643774ff3643325c7cc1137904f537302
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.6Claim SHA-256 0836676baa82e63b5b1304eb3f72cb645006a6d6b0d93942a73e6b7a5ed6bb21
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.7Claim SHA-256 0d9a05f3208de196a0409eaecd11c762e20686b7297435defa96cafd9aeb03c4
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.8Claim SHA-256 07616d15034178313147fc9ab168f2749afc58ab850b9b6050b94dbd0bad886d
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.9Claim SHA-256 98f56623a643956d19d29c6bcf409b6293f25ed78440b3003a14650ac0c4a6e4
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.10Claim SHA-256 f2c3ba7e15647d235e7ba35e6a526b97103318965163a53ba935c58156a7e8d3
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.11Claim SHA-256 8c400a06fe196eac48c72f2810de02e4b68011bfb9c878e0915c4fca4a91d92e
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.12Claim SHA-256 2efe951c88c8dd3b26307a2494d07e228dd71ceca9d919c2eaeace7671bd7fba
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.13Claim SHA-256 20d1f4bc4402051f4ab580dda7f07bff6b835d45d1494224e4908a610b18c218
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.14Claim SHA-256 f78e9b37d8f508ab06171231e5b0889e69e7f6878d42a2ffd7d824db35a93256
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.15Claim SHA-256 654fb76c0f9a2295e15121f8f644cf1d573abf815c7e47e125a694f6930e7d18
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.16Claim SHA-256 36680aa96320f745492a9ae17b5fb34cecb7e5689e1fe0be33d27ab0e876b844
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.17Claim SHA-256 53be67ced71244072daa715602c1f838ce9b49a76aac749a61e4b67a12318bcc
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.18Claim SHA-256 dcd71efe9e68778e6d75bd8c1f1eca7e3a03141c217b2b693ff04759caef1df3
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.19Claim SHA-256 a2fb250d21b18edf35e3fd47ee1f7a8a49110a268280d22b2e35712ef93d140f
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
compatibility.20Claim SHA-256 739d3ce9cd189e94849113709fd3942b07c08a3f2273121a9a219c64613f07c5
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Migration

Migration

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.

Authority & EvidenceClaim sources and exact digests
migrationClaim SHA-256 46fac5222793395e0e351161ede4c3e549b3851c26036fc3273d5db5196a44ce
docs/releases/v129.0.0-migration.mdSHA-256 d09bba0120527fe9f0a41f7e4c2909d8382740b99131dc037c974e36251a11d5

v129.5.0: A forward hosted migration is required only for a deployment missing its corresponding schema or guarded function; an already applied migration must not be repeated. Hosted application adoption has a separate schema and operational boundary. The complete post-v129 source interval adds 53 forward migration files through committed Main f990dc58ab605806eaccd45e1146d2ba7c4dd958. That is a source inventory, not an instruction to apply 53 files again and not evidence of any deployment's current applied state. The [exact inventory](v129.5.0-forward-source-inventory.json) binds every path to its committed blob and SHA-256; all candidate copies match those committed bytes.

Authority & EvidenceClaim sources and exact digests
migrationClaim SHA-256 63bf78b7d7740b4785520e6b507471803c122b0726899bb8d1a6638208bb9c3c
docs/releases/v129.5.0-migration.mdSHA-256 c16287c03d4d41bf4bd5e12fabf6e73fe11699b86003d104416be7424e7d9ba1

Constitution registry

Registry chain

v129.0.0

8d0b5b839d02d9efbd4306cc99410595a183705c2670b76d2567eaaaade99065
Authority & EvidenceClaim sources and exact digests
registryClaim SHA-256 278bc896a3309c8ce3680cf7466fcff1224bcdb665c1cf3cfb523005e7d3de9d
docs/releases/v127.0.0-constitution-registry.jsonSHA-256 f9f713c7a4d75ab4ffccc4551cdaeaa6e9268978222d7f8cbbc13e3683155c8adocs/releases/v127.0.0-constitution-registry.digestSHA-256 a8766e68d55394499fd7a92bb9b418c89730f375c84bc678757bdbd8a977db2edocs/releases/v129.0.0-registry-binding.jsonSHA-256 1069608413a2e2ddfbd498ee70dc60c49ee9242277f2d330a48cb0535e80b03b

v129.5.0

8d0b5b839d02d9efbd4306cc99410595a183705c2670b76d2567eaaaade99065

Predecessor 80137c2e6f294050ef36ff75e4daac15c7790b7f04d9a91fab9d1970fa3c0b09

Authority & EvidenceClaim sources and exact digests
registryClaim SHA-256 278bc896a3309c8ce3680cf7466fcff1224bcdb665c1cf3cfb523005e7d3de9d
docs/releases/v127.0.0-constitution-registry.jsonSHA-256 f9f713c7a4d75ab4ffccc4551cdaeaa6e9268978222d7f8cbbc13e3683155c8adocs/releases/v127.0.0-constitution-registry.digestSHA-256 a8766e68d55394499fd7a92bb9b418c89730f375c84bc678757bdbd8a977db2edocs/releases/v129.5.0-registry-binding.jsonSHA-256 6fee39202a5cf7bfcca92d050de5380a1e59268371980c0f9eec0887ea0cec51

Independent evidence dimensions

Evidence status

Dimensionv129.0.0v129.5.0
Repository releasedocumenteddocumented
Git tagpresentpresent
Package publicationconfirmedconfirmed
Deploymentconfirmednot-performed
Production smokeconfirmednot-performed
Signed attestationpresentpresent
Authority & EvidenceClaim sources and exact digests
status.repositoryReleaseClaim SHA-256 b92ca68fcef087e7e50513cd9555236300017fc1f981ee5603384c1129698511
docs/releases/v129.0.0-product-truth.mdSHA-256 b98689f5b39e13773ade608e88735feff4f13cf5410757ca38322da628870fbcdocs/releases/v129.0.0.mdSHA-256 9be3f96df9f49e857ecdf33955d56deaed9ffe52b4b02fe5683aed4a5077b780
status.gitTagClaim SHA-256 94332144d941eb1212c9af7f968e215a7042bf94925c9c10b21de97a2f0cea06
docs/releases/v129.0.0-git-tag-evidence.jsonSHA-256 0c8f863981172eb4f6bc1f1b349d9e3abca60f78a8ef88465bc5bc824e4d7a07
status.packagePublicationClaim SHA-256 82dd43841f057ad05a70ca320e5eb77c2f0e384a8bd599e3af6611162e202197
docs/releases/v129.0.0-package-publication-evidence.jsonSHA-256 b1501540643accd5457bdf610810dff78ccb40a68a05d621baab9324e3c1d808
status.deploymentClaim SHA-256 82dd43841f057ad05a70ca320e5eb77c2f0e384a8bd599e3af6611162e202197
docs/releases/v129.0.0-production-deployment-evidence.jsonSHA-256 5d3af95035eaf25fcf64f2f3439ea099888533d44852267b4f6d7240509509fedocs/releases/v129.0.0-checklist.mdSHA-256 364ab056280d39c2c81b071ecf51c483dee30356e9e2e29a308f3887e36d7360
status.productionSmokeClaim SHA-256 82dd43841f057ad05a70ca320e5eb77c2f0e384a8bd599e3af6611162e202197
docs/releases/v129.0.0-production-smoke.jsonSHA-256 1cbae40f6002da18fc96de1bbf5702129ab8d205e2bc62a30afae64da194553ddocs/releases/v129.0.0-checklist.mdSHA-256 364ab056280d39c2c81b071ecf51c483dee30356e9e2e29a308f3887e36d7360
status.signedAttestationClaim SHA-256 94332144d941eb1212c9af7f968e215a7042bf94925c9c10b21de97a2f0cea06
artifacts/release-attestations/2026-10-12T02-50-04-195Z-3b5343b4bac8.jsonSHA-256 73b66225076e74ef5409fbb168c4a74b5a3fd01437cdfd77581f42a45118e654
Authority & EvidenceClaim sources and exact digests
status.repositoryReleaseClaim SHA-256 b92ca68fcef087e7e50513cd9555236300017fc1f981ee5603384c1129698511
docs/releases/v129.5.0-product-truth.mdSHA-256 e0b2eaf669e5f443a131badafd601d657c8004b40fabd14b31e4aa024ee36553docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8
status.gitTagClaim SHA-256 94332144d941eb1212c9af7f968e215a7042bf94925c9c10b21de97a2f0cea06
git:refs/tags/v129.5.0SHA-256 e8dfc84a4de2de1048889b7ef5cff063b8815717c2eba5e0109cd667bd2ed194
status.packagePublicationClaim SHA-256 82dd43841f057ad05a70ca320e5eb77c2f0e384a8bd599e3af6611162e202197
docs/releases/v129.5.0-checklist.mdSHA-256 b71078aa7594e2804ead8c72fc005b93d04982312284e658d3a41154ab10624e
status.deploymentClaim SHA-256 90e0504781525511b16bcc0a8c27d422ead0e33778040d31eef4c9448911a316
docs/releases/v129.5.0-checklist.mdSHA-256 b71078aa7594e2804ead8c72fc005b93d04982312284e658d3a41154ab10624e
status.productionSmokeClaim SHA-256 90e0504781525511b16bcc0a8c27d422ead0e33778040d31eef4c9448911a316
docs/releases/v129.5.0-checklist.mdSHA-256 b71078aa7594e2804ead8c72fc005b93d04982312284e658d3a41154ab10624e
status.signedAttestationClaim SHA-256 94332144d941eb1212c9af7f968e215a7042bf94925c9c10b21de97a2f0cea06
artifacts/release-attestations/2026-11-15T01-24-29-387Z-a78415e2bb7a.jsonSHA-256 3a29170eb1269bd1bcf13c63f498d1680298a0c73d8be9d42c359426fb6aec47