ReceizAcademy

Current coordinated release

v129.5.0

Reality-Grade Infrastructure

Release date 2026-11-13

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

Outcome

Outcome

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

Changes

What changed

Exact durable Source custody

The native byte rail retains immutable Source bytes, staged commitments, bounded discovery, capacity accounting and process locks. Cancellation, retry, changed transport bytes and concurrent installation are checked at the actual storage boundary. A descriptor or provider response cannot replace the Source it names.

Technical and authority boundary

The native byte rail retains immutable Source bytes, staged commitments, bounded discovery, capacity accounting and process locks. Cancellation, retry, changed transport bytes and concurrent installation are checked at the actual storage boundary. A descriptor or provider response cannot replace the Source it names.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
The native byte rail retains immutable Source bytes, staged commitments, bounded discovery, capacity accounting and process locks. Cancellation, retry, changed transport bytes and concurrent installation are checked at the actual storage boundary. A descriptor or provider response cannot replace the Source it names.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.0Claim SHA-256 09fe78bf605ae64478d678022dbd6aa5a5d09d474b4be9a73dad9a44648432b3
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Native Account and Subject composition

Initial Subject admission, namespaces, state, access keys, Account history and selected Source controls compose the existing enclosing proof and custody. These implemented components retain their exact scoped qualification; full production transaction hosting and provider cutover remain separately recorded.

Technical and authority boundary

Initial Subject admission, namespaces, state, access keys, Account history and selected Source controls compose the existing enclosing proof and custody. These implemented components retain their exact scoped qualification; full production transaction hosting and provider cutover remain separately recorded.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Initial Subject admission, namespaces, state, access keys, Account history and selected Source controls compose the existing enclosing proof and custody. These implemented components retain their exact scoped qualification; full production transaction hosting and provider cutover remain separately recorded.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.1Claim SHA-256 c885ffa57d44379e2f0c19bb4134e9ae63d162750b45206b7927841e7efc8898
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Identity Record continuity

Export carries accepted account state and artwork; restore selects the Account carried by the Record and binds its existing grants. Verified local restoration projects that accepted identity immediately while permitted synchronization appends beneath it.

Technical and authority boundary

Export carries accepted account state and artwork; restore selects the Account carried by the Record and binds its existing grants. Verified local restoration projects that accepted identity immediately while permitted synchronization appends beneath it.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Export carries accepted account state and artwork; restore selects the Account carried by the Record and binds its existing grants. Verified local restoration projects that accepted identity immediately while permitted synchronization appends beneath it.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.2Claim SHA-256 af19d316a961b789069704fecca0b1c19c6cae208f5fbcaf6196aeec08a92e1a
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Isolated identity custody

Vault isolation, optional Account passkeys, canonical-RP PBI composition and recovered-account device bindings preserve the admitted Account. Device signing identity remains associated evidence under the chosen public Receiz ID.

Technical and authority boundary

Vault isolation, optional Account passkeys, canonical-RP PBI composition and recovered-account device bindings preserve the admitted Account. Device signing identity remains associated evidence under the chosen public Receiz ID.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Vault isolation, optional Account passkeys, canonical-RP PBI composition and recovered-account device bindings preserve the admitted Account. Device signing identity remains associated evidence under the chosen public Receiz ID.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.3Claim SHA-256 67940b0d7aebcb99e05c11f28bf303b366261102e134ed8d7935afbeb570dbce
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Complete receiving names and routes

Current Receiz IDs retain every character through receiving, lookup, profile sharing and public labels. Compatible historical locators continue to resolve beneath their source-bound account; current display does not shorten the name or rewrite sealed historical identity.

Technical and authority boundary

Current Receiz IDs retain every character through receiving, lookup, profile sharing and public labels. Compatible historical locators continue to resolve beneath their source-bound account; current display does not shorten the name or rewrite sealed historical identity.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Current Receiz IDs retain every character through receiving, lookup, profile sharing and public labels. Compatible historical locators continue to resolve beneath their source-bound account; current display does not shorten the name or rewrite sealed historical identity.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.4Claim SHA-256 effd18231653a2886e6c81828b2310c429fe81aebdcf347d11c5a4f1b2612091
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Held Profile entry

Managed entry reuses the complete held public Profile and adds admitted owner controls beneath the same Source. Profile navigation does not replace known identity, membership or media with a partial loading representation while later account reads complete.

Technical and authority boundary

Managed entry reuses the complete held public Profile and adds admitted owner controls beneath the same Source. Profile navigation does not replace known identity, membership or media with a partial loading representation while later account reads complete.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Managed entry reuses the complete held public Profile and adds admitted owner controls beneath the same Source. Profile navigation does not replace known identity, membership or media with a partial loading representation while later account reads complete.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.5Claim SHA-256 1d9beb7fd7f51c270e2a22bdf8add8476b2a3c4a5086a9e01340484fd8e2ce88
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Accepted Showcase succession

Signing, visibility, metadata, public inventory and collection delivery preserve predecessor-bound accepted successors. An older capture, equal count, partial body or subordinate dirty/prepared marker cannot establish a newer Source or outrank its admitted membership.

Technical and authority boundary

Signing, visibility, metadata, public inventory and collection delivery preserve predecessor-bound accepted successors. An older capture, equal count, partial body or subordinate dirty/prepared marker cannot establish a newer Source or outrank its admitted membership.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Signing, visibility, metadata, public inventory and collection delivery preserve predecessor-bound accepted successors. An older capture, equal count, partial body or subordinate dirty/prepared marker cannot establish a newer Source or outrank its admitted membership.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.6Claim SHA-256 6d18a524e2dc00bf58776e2f085ad9f6d9d0f28f0f97602e7f1815c2939d14dc
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

One source across public readers

Profile, collection, discovery, Explore, Ledger and direct Original readers consume admitted public Source membership. Bounded packs, exact source coordinates and existing delivery recovery carry the same successor without whole-history rediscovery or another publication authority.

Technical and authority boundary

Profile, collection, discovery, Explore, Ledger and direct Original readers consume admitted public Source membership. Bounded packs, exact source coordinates and existing delivery recovery carry the same successor without whole-history rediscovery or another publication authority.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Profile, collection, discovery, Explore, Ledger and direct Original readers consume admitted public Source membership. Bounded packs, exact source coordinates and existing delivery recovery carry the same successor without whole-history rediscovery or another publication authority.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.7Claim SHA-256 1045cdf081bae91f99b01675e59584d7a71fcc2d75ca9487f0d35b549416a7cd
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Chosen creator continuity

New creator payloads carry the chosen Receiz ID while retaining the associated signing-device identity. The visible creator and owner are projected from the same accepted relationships; current name enrichment does not forge a historical signature or change an Original's stable identity.

Technical and authority boundary

New creator payloads carry the chosen Receiz ID while retaining the associated signing-device identity. The visible creator and owner are projected from the same accepted relationships; current name enrichment does not forge a historical signature or change an Original's stable identity.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
New creator payloads carry the chosen Receiz ID while retaining the associated signing-device identity. The visible creator and owner are projected from the same accepted relationships; current name enrichment does not forge a historical signature or change an Original's stable identity.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.8Claim SHA-256 4489c61da76ab03875abf3e28b2554bdfe2bda2329b640c88f1fe6dc2efc416d
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Exact signed native Originals

Authored file carriers retain native media bytes and the existing appended authorship/history. PDF, image, audio and other supported file paths use the existing custody/exporter; download does not substitute display JSON, reseal the file or request another signature. Warm Save reuses the retained authored file without a sealer or network request; cold reopening reads existing local custody/IndexedDB. Verification ZIP creation separately reads verifier resources. Actual candidate browser download remains pending in conformance.

Technical and authority boundary

Authored file carriers retain native media bytes and the existing appended authorship/history. PDF, image, audio and other supported file paths use the existing custody/exporter; download does not substitute display JSON, reseal the file or request another signature. Warm Save reuses the retained authored file without a sealer or network request; cold reopening reads existing local custody/IndexedDB. Verification ZIP creation separately reads verifier resources. Actual candidate browser download remains pending in conformance.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Authored file carriers retain native media bytes and the existing appended authorship/history. PDF, image, audio and other supported file paths use the existing custody/exporter; download does not substitute display JSON, reseal the file or request another signature. Warm Save reuses the retained authored file without a sealer or network request; cold reopening reads existing local custody/IndexedDB. Verification ZIP creation separately reads verifier resources. Actual candidate browser download remains pending in conformance.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.9Claim SHA-256 f05eb9bc4872b34fb19e97662753a57a8853a3d893fe649ad361a750c8ed3b42
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Independent Original and derivative offers

Composer options carry separate allow/disable controls for the Original file, derivative and Moment record. Optional quantity and price apply independently to the Original and derivative; the Moment record is allow-only. Quantity is 1–1,000,000; a paid USD price is $0.01–$10,000 and blank price is free. Protected primary media enters the existing private Original custody only when that option is selected. Existing source-bound checkout/payment and atomic consumption enforce the chosen terms; downloading does not itself transfer ownership or admit a trade.

Technical and authority boundary

Composer options carry separate allow/disable controls for the Original file, derivative and Moment record. Optional quantity and price apply independently to the Original and derivative; the Moment record is allow-only. Quantity is 1–1,000,000; a paid USD price is $0.01–$10,000 and blank price is free. Protected primary media enters the existing private Original custody only when that option is selected. Existing source-bound checkout/payment and atomic consumption enforce the chosen terms; downloading does not itself transfer ownership or admit a trade.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Composer options carry separate allow/disable controls for the Original file, derivative and Moment record. Optional quantity and price apply independently to the Original and derivative; the Moment record is allow-only. Quantity is 1–1,000,000; a paid USD price is $0.01–$10,000 and blank price is free. Protected primary media enters the existing private Original custody only when that option is selected. Existing source-bound checkout/payment and atomic consumption enforce the chosen terms; downloading does not itself transfer ownership or admit a trade.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.10Claim SHA-256 5740db9c46588f97d03dd51df44a801fbad98438a4e038c6045b9eb54700449a
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Actual transaction Original export

Receipt and Ledger exports bind the actual transaction, participant and original-source reader. Bank's receipt-share correction passes that existing context to downloadLedgerOriginal instead of serializing the receipt display. The actual saved file and its offline verification remain explicit acceptance evidence.

Technical and authority boundary

Receipt and Ledger exports bind the actual transaction, participant and original-source reader. Bank's receipt-share correction passes that existing context to downloadLedgerOriginal instead of serializing the receipt display. The actual saved file and its offline verification remain explicit acceptance evidence.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Receipt and Ledger exports bind the actual transaction, participant and original-source reader. Bank's receipt-share correction passes that existing context to downloadLedgerOriginal instead of serializing the receipt display. The actual saved file and its offline verification remain explicit acceptance evidence.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.11Claim SHA-256 984794af66286e614ce823480a09db4c682f485c07d0be8fdd04eec16c3da32d
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Complete verification-kit custody

A kit carries the exact Original, its existing proof/history and the standalone verification closure required to inspect it. Incomplete source cannot be represented as a complete kit; file download and kit download retain distinct contracts.

Technical and authority boundary

A kit carries the exact Original, its existing proof/history and the standalone verification closure required to inspect it. Incomplete source cannot be represented as a complete kit; file download and kit download retain distinct contracts.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
A kit carries the exact Original, its existing proof/history and the standalone verification closure required to inspect it. Incomplete source cannot be represented as a complete kit; file download and kit download retain distinct contracts.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.12Claim SHA-256 c413422c591897518be01ce8b95081bd0f5137f7704dde7e328e520f6421aacb
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Bounded canonical verification

PNG/provenance extraction and native carrier readers enforce their existing execution bounds and preserve malformed-proof precedence. Capacity refusal reports that validity was not evaluated. It cannot become a forged acceptance or an invalid-proof verdict.

Technical and authority boundary

PNG/provenance extraction and native carrier readers enforce their existing execution bounds and preserve malformed-proof precedence. Capacity refusal reports that validity was not evaluated. It cannot become a forged acceptance or an invalid-proof verdict.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
PNG/provenance extraction and native carrier readers enforce their existing execution bounds and preserve malformed-proof precedence. Capacity refusal reports that validity was not evaluated. It cannot become a forged acceptance or an invalid-proof verdict.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.13Claim SHA-256 a16b14cbf0322dd1cc7b4f77cdb7ab5107f26096c2c694db03120ca2c6698029
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Canonical verifier consumers

SDK, standalone verifier, Offline Studio and Docs Workbench derive from their declared canonical implementation. The Workbench closure includes the actual browser runtime dependencies; generated delivery resources cannot drift into a separate proof interpretation.

Technical and authority boundary

SDK, standalone verifier, Offline Studio and Docs Workbench derive from their declared canonical implementation. The Workbench closure includes the actual browser runtime dependencies; generated delivery resources cannot drift into a separate proof interpretation.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
SDK, standalone verifier, Offline Studio and Docs Workbench derive from their declared canonical implementation. The Workbench closure includes the actual browser runtime dependencies; generated delivery resources cannot drift into a separate proof interpretation.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.14Claim SHA-256 34e11c59a13320f12e06690ea7353f511a33dfbd03f39a79bb8687778fbaa8ad
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Uncut transaction download transport

The exact GET transaction Moment export uses the existing network-only service-worker rail. Its full exporter lifetime and bytes survive beyond the unrelated 3.5-second API snapshot cutoff; origin errors remain actual errors and private attachments are not cached as public snapshots.

Technical and authority boundary

The exact GET transaction Moment export uses the existing network-only service-worker rail. Its full exporter lifetime and bytes survive beyond the unrelated 3.5-second API snapshot cutoff; origin errors remain actual errors and private attachments are not cached as public snapshots.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
The exact GET transaction Moment export uses the existing network-only service-worker rail. Its full exporter lifetime and bytes survive beyond the unrelated 3.5-second API snapshot cutoff; origin errors remain actual errors and private attachments are not cached as public snapshots.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.15Claim SHA-256 ef6d27bf0e3b0859c04904601bbcda633342f114c6c7d7690882d1db0be6d261
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Connected Notes and Wallet funding continuity

Bank Note funding/redemption, exact quotes, device attestation, connected Account Notes and Wallet-ledger projection reuse existing custody and financial writers. Composite allocation conserves its funding Source; downloaded bearer, accepted receiving, Settlement and current spend authority remain separately inspectable stages.

Technical and authority boundary

Bank Note funding/redemption, exact quotes, device attestation, connected Account Notes and Wallet-ledger projection reuse existing custody and financial writers. Composite allocation conserves its funding Source; downloaded bearer, accepted receiving, Settlement and current spend authority remain separately inspectable stages.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Bank Note funding/redemption, exact quotes, device attestation, connected Account Notes and Wallet-ledger projection reuse existing custody and financial writers. Composite allocation conserves its funding Source; downloaded bearer, accepted receiving, Settlement and current spend authority remain separately inspectable stages.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.16Claim SHA-256 85af15a747cd72dd10b4e655fe09d5709b3588510744d069860214d74a3ddf4a
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Financial Originals and finite rights

Existing Account grants, ordinary owner consent, canonical Source and SDK signing bind Wallet/Market operands and finite execution rights. Scoped source admission, local computation, causal adoption, receipts, receiving and handoff preserve original Kai and existing numerical law. Complete Bank activation and global fill/cancel qualification remain explicit boundaries.

Technical and authority boundary

Existing Account grants, ordinary owner consent, canonical Source and SDK signing bind Wallet/Market operands and finite execution rights. Scoped source admission, local computation, causal adoption, receipts, receiving and handoff preserve original Kai and existing numerical law. Complete Bank activation and global fill/cancel qualification remain explicit boundaries.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Existing Account grants, ordinary owner consent, canonical Source and SDK signing bind Wallet/Market operands and finite execution rights. Scoped source admission, local computation, causal adoption, receipts, receiving and handoff preserve original Kai and existing numerical law. Complete Bank activation and global fill/cancel qualification remain explicit boundaries.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.17Claim SHA-256 430c6c070d08c4a3bfec3f894de8a634df555394c1d308dd43b008eea71c2b01
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Account Statement from the retained Original

Saving an Account Statement reuses the already verified held account-proof bytes with a clear file title. It performs no publication or resealing. The separate opt-in public image/link and Ledger verification kit retain their own source and disclosure boundaries.

Technical and authority boundary

Saving an Account Statement reuses the already verified held account-proof bytes with a clear file title. It performs no publication or resealing. The separate opt-in public image/link and Ledger verification kit retain their own source and disclosure boundaries.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Saving an Account Statement reuses the already verified held account-proof bytes with a clear file title. It performs no publication or resealing. The separate opt-in public image/link and Ledger verification kit retain their own source and disclosure boundaries.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.18Claim SHA-256 32389b31a14c0f15b10fa4df9663f3338764987fc80e8178a9065cf30c812066
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Recoverable payment outcomes

Pending Send cancellation/resolution uses the original saved request and existing atomic outcome rather than submitting another payment. Profile display/readiness work cannot become financial authority or permit duplicate execution. A terminal refusal and an unknown outcome retain their distinct recovery contracts.

Technical and authority boundary

Pending Send cancellation/resolution uses the original saved request and existing atomic outcome rather than submitting another payment. Profile display/readiness work cannot become financial authority or permit duplicate execution. A terminal refusal and an unknown outcome retain their distinct recovery contracts.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Pending Send cancellation/resolution uses the original saved request and existing atomic outcome rather than submitting another payment. Profile display/readiness work cannot become financial authority or permit duplicate execution. A terminal refusal and an unknown outcome retain their distinct recovery contracts.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.19Claim SHA-256 0a6690ca81d23ada1b549df8dd337d240479f7a954817f5f7cb5103cf5da90fe
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Funding disclosure and retained ancestry

Transfer, Note, Reserve and certificate records retain source links, funding allocations and original coordinates. Public/private display reuses carried supporting history; a projection cannot manufacture missing evidence or silently redefine a funding source. The exact complete-ancestry acceptance status belongs in conformance.

Technical and authority boundary

Transfer, Note, Reserve and certificate records retain source links, funding allocations and original coordinates. Public/private display reuses carried supporting history; a projection cannot manufacture missing evidence or silently redefine a funding source. The exact complete-ancestry acceptance status belongs in conformance.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Transfer, Note, Reserve and certificate records retain source links, funding allocations and original coordinates. Public/private display reuses carried supporting history; a projection cannot manufacture missing evidence or silently redefine a funding source. The exact complete-ancestry acceptance status belongs in conformance.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.20Claim SHA-256 c54e0f0b0e342bcecfb8aa7b1cf6ec2f3f4688c26d4eed6e5753541e4f2d0fa7
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Public Original earning and cash preservation

Qualified public PBI-signed Originals compose the existing Settlement admission path. Wallet projection reuses the accepted signing result while preserving prior cash and funding history. An earning display does not establish a sale, seller proceeds or a separately unexecuted payment.

Technical and authority boundary

Qualified public PBI-signed Originals compose the existing Settlement admission path. Wallet projection reuses the accepted signing result while preserving prior cash and funding history. An earning display does not establish a sale, seller proceeds or a separately unexecuted payment.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Qualified public PBI-signed Originals compose the existing Settlement admission path. Wallet projection reuses the accepted signing result while preserving prior cash and funding history. An earning display does not establish a sale, seller proceeds or a separately unexecuted payment.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.21Claim SHA-256 f04f3f194d2b7b3feb365217926bfb891bcc8d2aa27bc42f0142448c7ca4f043
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Exact holdings and market coordinates

Portfolio and trade records retain quantity, cost, realized facts and issuance coordinates. Stable Receiz ID selects the public Original's market key, so a name presentation cannot create another asset or reset history. Retained historical prefixes remain binding beneath current display.

Technical and authority boundary

Portfolio and trade records retain quantity, cost, realized facts and issuance coordinates. Stable Receiz ID selects the public Original's market key, so a name presentation cannot create another asset or reset history. Retained historical prefixes remain binding beneath current display.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Portfolio and trade records retain quantity, cost, realized facts and issuance coordinates. Stable Receiz ID selects the public Original's market key, so a name presentation cannot create another asset or reset history. Retained historical prefixes remain binding beneath current display.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.22Claim SHA-256 72427efee2e481ed34c4b6cfc9909773f00eb7e36bed246078de3a8ab698845e
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Merchant Counter

Owner-bound catalogs, variants/modifiers, taxes, discounts, fixed checkout requests, stock reservations and atomic inventory lifecycles compose existing payment machinery. A catalog entry or reservation cannot stand in for completed payment and delivered custody.

Technical and authority boundary

Owner-bound catalogs, variants/modifiers, taxes, discounts, fixed checkout requests, stock reservations and atomic inventory lifecycles compose existing payment machinery. A catalog entry or reservation cannot stand in for completed payment and delivered custody.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Owner-bound catalogs, variants/modifiers, taxes, discounts, fixed checkout requests, stock reservations and atomic inventory lifecycles compose existing payment machinery. A catalog entry or reservation cannot stand in for completed payment and delivered custody.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.23Claim SHA-256 2971b41a3af82d6ae55cc8621908352f41a576e48781619e5b5d81c0ba274e4c
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Calendar offers and paid appointments

Owner timezone and accepted offer terms govern availability, per-guest price, payment handoff and recovery. Native Calendar/Message continuity, room evidence, recordings and reminders retain the accepted booking and Account relationship.

Technical and authority boundary

Owner timezone and accepted offer terms govern availability, per-guest price, payment handoff and recovery. Native Calendar/Message continuity, room evidence, recordings and reminders retain the accepted booking and Account relationship.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Owner timezone and accepted offer terms govern availability, per-guest price, payment handoff and recovery. Native Calendar/Message continuity, room evidence, recordings and reminders retain the accepted booking and Account relationship.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.24Claim SHA-256 fea275e45594a8db8ad20331ffd222e563bf5a2ec117e16c2bf1bddbf0708559
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Owner-controlled booking notice

Saved preferences permit same-day booking and minimum advance notice from 0 to 43,200 minutes, retaining the existing ten-minute default. Same-day exclusion is evaluated in the owner's saved timezone; visitor display settings cannot redefine availability.

Technical and authority boundary

Saved preferences permit same-day booking and minimum advance notice from 0 to 43,200 minutes, retaining the existing ten-minute default. Same-day exclusion is evaluated in the owner's saved timezone; visitor display settings cannot redefine availability.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Saved preferences permit same-day booking and minimum advance notice from 0 to 43,200 minutes, retaining the existing ten-minute default. Same-day exclusion is evaluated in the owner's saved timezone; visitor display settings cannot redefine availability.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.25Claim SHA-256 8b476a8f6a07d96a67ed56cd7216c51fbaac765f27d550fe87ee454789e70a07
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Meeting and invitation continuity

Invitations, guest confirmations, existing conversations, Calendar events and real meeting entrances remain attached to their accepted recipient and booking. Visitor-local labels display the booked instant without changing the owner's schedule or the payment terms.

Technical and authority boundary

Invitations, guest confirmations, existing conversations, Calendar events and real meeting entrances remain attached to their accepted recipient and booking. Visitor-local labels display the booked instant without changing the owner's schedule or the payment terms.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Invitations, guest confirmations, existing conversations, Calendar events and real meeting entrances remain attached to their accepted recipient and booking. Visitor-local labels display the booked instant without changing the owner's schedule or the payment terms.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.26Claim SHA-256 985aba478e798660acbd7e734440cce3c044018fd040f4c073284e8e78918e56
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Scoped Twin and organizer execution

Owned Twins reuse their brain and complete conversation context across streaming and supported contact, Calendar, organizer and financial tools. Owner/visitor boundaries remain explicit; shared cookies or request probes cannot expose another person's private memory or contacts.

Technical and authority boundary

Owned Twins reuse their brain and complete conversation context across streaming and supported contact, Calendar, organizer and financial tools. Owner/visitor boundaries remain explicit; shared cookies or request probes cannot expose another person's private memory or contacts.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Owned Twins reuse their brain and complete conversation context across streaming and supported contact, Calendar, organizer and financial tools. Owner/visitor boundaries remain explicit; shared cookies or request probes cannot expose another person's private memory or contacts.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.27Claim SHA-256 303882c423a8d72b19e94ab978f79d79c949a3f92ceeeb6b61601e42cd82f363
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Actual provider and usage accounting

Provider continuations, sponsored replies, reserved capacity and metered usage bind accepted funding and actual execution. Existing independent preparation runs concurrently where supported; redundant serial preparation and artificial streaming waits are removed without creating a new budget authority.

Technical and authority boundary

Provider continuations, sponsored replies, reserved capacity and metered usage bind accepted funding and actual execution. Existing independent preparation runs concurrently where supported; redundant serial preparation and artificial streaming waits are removed without creating a new budget authority.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Provider continuations, sponsored replies, reserved capacity and metered usage bind accepted funding and actual execution. Existing independent preparation runs concurrently where supported; redundant serial preparation and artificial streaming waits are removed without creating a new budget authority.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.28Claim SHA-256 166a352615839ea18e48ce50ad753306a307d21e468c8c478db06dbfa37d34cb
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Receiz-ID email in native Messages

Current and permanently retained aliases bind the exact Account UID. Signed external envelopes, verified private MIME and provider/RFC delivery identifiers remain external observations inside existing Message custody, preserving the same correspondent and thread.

Technical and authority boundary

Current and permanently retained aliases bind the exact Account UID. Signed external envelopes, verified private MIME and provider/RFC delivery identifiers remain external observations inside existing Message custody, preserving the same correspondent and thread.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Current and permanently retained aliases bind the exact Account UID. Signed external envelopes, verified private MIME and provider/RFC delivery identifiers remain external observations inside existing Message custody, preserving the same correspondent and thread.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.29Claim SHA-256 ca6b9b7cd49dd29c54cced661bcc763347d5c23c20ddd3b72f74be8a5a8e47b4
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Bounded recipient adoption and reply privacy

One-use recipient access, alias guards and reply correlation preserve the intended Account and conversation. Recipient-only login links stay out of replies and shared exports. SMTP possession does not become native authorship, identity admission or financial authorization.

Technical and authority boundary

One-use recipient access, alias guards and reply correlation preserve the intended Account and conversation. Recipient-only login links stay out of replies and shared exports. SMTP possession does not become native authorship, identity admission or financial authorization.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
One-use recipient access, alias guards and reply correlation preserve the intended Account and conversation. Recipient-only login links stay out of replies and shared exports. SMTP possession does not become native authorship, identity admission or financial authorization.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.30Claim SHA-256 f5d6ebde7e0706c31bc3e2c1b4ec6bb6fba001f1686ef05b4e9096efdaf2567e
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Existing conversation presentation

Bank correspondence reuses its registered-client context, verified recipient, existing conversation and established email design. A separate receiving credential preserves the sending boundary; routing activation and later presentation deployment have their own evidence.

Technical and authority boundary

Bank correspondence reuses its registered-client context, verified recipient, existing conversation and established email design. A separate receiving credential preserves the sending boundary; routing activation and later presentation deployment have their own evidence.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Bank correspondence reuses its registered-client context, verified recipient, existing conversation and established email design. A separate receiving credential preserves the sending boundary; routing activation and later presentation deployment have their own evidence.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.31Claim SHA-256 b407d24e82b642c2954ddb1594e63c7688f4a92aab4d61176d0200f4a0b138e8
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Shared exact projections

Existing receipt, download-link and DER/signature helpers replace competing copies while preserving input/output and historical signature behavior. Synchronous viewport ownership lets one active writer survive another writer's cleanup without a paint delay or a new loading interval.

Technical and authority boundary

Existing receipt, download-link and DER/signature helpers replace competing copies while preserving input/output and historical signature behavior. Synchronous viewport ownership lets one active writer survive another writer's cleanup without a paint delay or a new loading interval.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Existing receipt, download-link and DER/signature helpers replace competing copies while preserving input/output and historical signature behavior. Synchronous viewport ownership lets one active writer survive another writer's cleanup without a paint delay or a new loading interval.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.32Claim SHA-256 634aff23875652fe3ebc1f30f9ba8577360735d5135fbf7a6863707e4238f0de
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Targeted service security

Operator-only billing closeout, atomic challenge consumption, request-local World overrides and public-proof HTTPS/DNS/IP/TLS/redirect/resource controls protect their existing boundaries. They introduce no server, vendor allowlist or external issuer requirement for ordinary native local PBI signing.

Technical and authority boundary

Operator-only billing closeout, atomic challenge consumption, request-local World overrides and public-proof HTTPS/DNS/IP/TLS/redirect/resource controls protect their existing boundaries. They introduce no server, vendor allowlist or external issuer requirement for ordinary native local PBI signing.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Operator-only billing closeout, atomic challenge consumption, request-local World overrides and public-proof HTTPS/DNS/IP/TLS/redirect/resource controls protect their existing boundaries. They introduce no server, vendor allowlist or external issuer requirement for ordinary native local PBI signing.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.33Claim SHA-256 7cdd32e2a08d59ba28f1756a70ab70569f31d33018eb420b1dad5434609146bf
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Patched dependency closure

Targeted framework, image, MCP and transitive corrections preserve the established Streamdown 2.5 renderer, actual Creator DOM and frozen lint policy. The existing patched framework renderer supplies proof images; ordinary PNG controls retain exact output and unsafe SVG inputs retain refusal/escaping.

Technical and authority boundary

Targeted framework, image, MCP and transitive corrections preserve the established Streamdown 2.5 renderer, actual Creator DOM and frozen lint policy. The existing patched framework renderer supplies proof images; ordinary PNG controls retain exact output and unsafe SVG inputs retain refusal/escaping.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
Targeted framework, image, MCP and transitive corrections preserve the established Streamdown 2.5 renderer, actual Creator DOM and frozen lint policy. The existing patched framework renderer supplies proof images; ordinary PNG controls retain exact output and unsafe SVG inputs retain refusal/escaping.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.34Claim SHA-256 038197d05c34a0a64e37e318b9353c44c335eb1078a72eb9bac4e1979b16133d
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Coordinated public capability coverage

The current catalog contains 1,529 entries: 705 callable SDK exports, 425 client methods, 356 full MCP tools and 43 AI skills, with 37 manifests and 34 prompts. The added projectReceizAccountDisplayName projects existing account-name truth. No public export is removed; inventory membership creates no grant, adapter or private custody.

Technical and authority boundary

The current catalog contains 1,529 entries: 705 callable SDK exports, 425 client methods, 356 full MCP tools and 43 AI skills, with 37 manifests and 34 prompts. The added projectReceizAccountDisplayName projects existing account-name truth. No public export is removed; inventory membership creates no grant, adapter or private custody.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
The current catalog contains 1,529 entries: 705 callable SDK exports, 425 client methods, 356 full MCP tools and 43 AI skills, with 37 manifests and 34 prompts. The added projectReceizAccountDisplayName projects existing account-name truth. No public export is removed; inventory membership creates no grant, adapter or private custody.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.35Claim SHA-256 119b232cb67e655c9f76c476d7421baf8f8bf802427ca1f6457be3686be20dc4
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Byte-exact package and installation delivery

All three public 129.5 archives match qualification. The current public AI installation kit carries its checked runtime/proof resources, while every historical content-addressed download remains unchanged. Installed consumer, application, standalone and disclosure qualification remain independently recorded.

Technical and authority boundary

All three public 129.5 archives match qualification. The current public AI installation kit carries its checked runtime/proof resources, while every historical content-addressed download remains unchanged. Installed consumer, application, standalone and disclosure qualification remain independently recorded.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
All three public 129.5 archives match qualification. The current public AI installation kit carries its checked runtime/proof resources, while every historical content-addressed download remains unchanged. Installed consumer, application, standalone and disclosure qualification remain independently recorded.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.36Claim SHA-256 264b2641f22bffccfef6c30bac11e00ce24c6e7df6b91528fa6baf7e2ee8ded7
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Complete release provenance

The release book includes all 399 post-tag commits, the separate current candidate, inherited registry/matrix, compatibility, migration inventory, practical integration, governance and exact conformance. Historical v129 closeout and failed attempts remain at their original coordinates.

Technical and authority boundary

The release book includes all 399 post-tag commits, the separate current candidate, inherited registry/matrix, compatibility, migration inventory, practical integration, governance and exact conformance. Historical v129 closeout and failed attempts remain at their original coordinates.

Why
People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.
Capability enabled
The release book includes all 399 post-tag commits, the separate current candidate, inherited registry/matrix, compatibility, migration inventory, practical integration, governance and exact conformance. Historical v129 closeout and failed attempts remain at their original coordinates.
Compatibility
The v129.5.0 compatibility record remains the exact boundary for this outcome.
Migration
The v129.5.0 migration record remains the exact adoption boundary for this outcome.
Authority & EvidenceClaim sources and exact digests
whatChanged.37Claim SHA-256 522217737d19404e7471a4c881c1fa1eedca71a08caa4d46095d795af0f46498
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Purpose

Why it matters

  • People, creators, businesses, developers and institutions can carry and inspect the same actual proof across experiences. Accepted identity, complete Profile, signed native Original, original Kai and retained ownership/history remain together as the object moves between device, file, application and public witness surface. Creators keep their chosen public identity and authored media through lawful signing, offers and download; a listing, asking price and completed transfer remain separately evidenced facts. Businesses compose Counter, funded Notes, accepted Calendar offers, approved appointment payments, real meetings, scoped Twins and existing Messages under actual consent and execution. Developers use one coordinated distribution and the implemented SDK/MCP/AI paths while preserving issued application IDs, grants, audience, nonce, replay and device/trusted-host custody. Counterparties and auditors can reopen exact source, reproduce verification and distinguish what was issued, accepted, appended, transported, paid, delivered and claimed. The practical cash out is source, law, sequence, object and evidence remaining inspectable together, with every reader underneath them. A database, institution, provider, page or model cannot replace that authority.

    Authority & EvidenceClaim sources and exact digests
    why.0Claim SHA-256 050b331b7996b2ece70857e5c6d9b25e1802dd2fb6e5df731a1708b9fdf63b3a
    docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Available outcomes

Capabilities now available

Exact durable Source custody

The native byte rail retains immutable Source bytes, staged commitments, bounded discovery, capacity accounting and process locks. Cancellation, retry, changed transport bytes and concurrent installation are checked at the actual storage boundary. A descriptor or provider response cannot replace the Source it names.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.0Claim SHA-256 4bd950a2fb889ac71df196d9b3435f9a88c714a24c18706d5d7c8b7689b3f53d
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Native Account and Subject composition

Initial Subject admission, namespaces, state, access keys, Account history and selected Source controls compose the existing enclosing proof and custody. These implemented components retain their exact scoped qualification; full production transaction hosting and provider cutover remain separately recorded.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.1Claim SHA-256 55f55341f87373f4f15bb83f0605b004d3f332bb7a647189f337b8247fac21f4
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Identity Record continuity

Export carries accepted account state and artwork; restore selects the Account carried by the Record and binds its existing grants. Verified local restoration projects that accepted identity immediately while permitted synchronization appends beneath it.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.2Claim SHA-256 ddd8b35e8c10d22553076f364a860ceb9353bb7eeb0400d0445574afd6844f87
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Isolated identity custody

Vault isolation, optional Account passkeys, canonical-RP PBI composition and recovered-account device bindings preserve the admitted Account. Device signing identity remains associated evidence under the chosen public Receiz ID.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.3Claim SHA-256 914d34552b2aedc2bac7d871c32c166166d44f9f3748dd77b2f50a4e4f920bb5
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Complete receiving names and routes

Current Receiz IDs retain every character through receiving, lookup, profile sharing and public labels. Compatible historical locators continue to resolve beneath their source-bound account; current display does not shorten the name or rewrite sealed historical identity.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.4Claim SHA-256 513d9be2302544358721010f5faf3baac9f289788f73df40ccba5e0d15121232
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Held Profile entry

Managed entry reuses the complete held public Profile and adds admitted owner controls beneath the same Source. Profile navigation does not replace known identity, membership or media with a partial loading representation while later account reads complete.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.5Claim SHA-256 26cd9f0ae3e112787433d2a0bfe49c42c999f5a481265f7bdee155fd64aba00a
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Accepted Showcase succession

Signing, visibility, metadata, public inventory and collection delivery preserve predecessor-bound accepted successors. An older capture, equal count, partial body or subordinate dirty/prepared marker cannot establish a newer Source or outrank its admitted membership.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.6Claim SHA-256 c976ba3d56228268c9d96574d066dcc3ae7e2fe132e923c4dcb4a74c3cbd6828
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

One source across public readers

Profile, collection, discovery, Explore, Ledger and direct Original readers consume admitted public Source membership. Bounded packs, exact source coordinates and existing delivery recovery carry the same successor without whole-history rediscovery or another publication authority.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.7Claim SHA-256 7ad8d898d4a5483cba1ccdc9d85ecacb226cff9d72fb949c9b4087bac27fcdaa
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Chosen creator continuity

New creator payloads carry the chosen Receiz ID while retaining the associated signing-device identity. The visible creator and owner are projected from the same accepted relationships; current name enrichment does not forge a historical signature or change an Original's stable identity.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.8Claim SHA-256 f3c76203025292f0bfe698077caa72753b183885240f149a5cc3b049d3da13ff
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Exact signed native Originals

Authored file carriers retain native media bytes and the existing appended authorship/history. PDF, image, audio and other supported file paths use the existing custody/exporter; download does not substitute display JSON, reseal the file or request another signature. Warm Save reuses the retained authored file without a sealer or network request; cold reopening reads existing local custody/IndexedDB. Verification ZIP creation separately reads verifier resources. Actual candidate browser download remains pending in conformance.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.9Claim SHA-256 5dbb7416bc83a5479b702b96e1efba40a7a79ca9f85abbb99f10c5c3bdd22fc5
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Independent Original and derivative offers

Composer options carry separate allow/disable controls for the Original file, derivative and Moment record. Optional quantity and price apply independently to the Original and derivative; the Moment record is allow-only. Quantity is 1–1,000,000; a paid USD price is $0.01–$10,000 and blank price is free. Protected primary media enters the existing private Original custody only when that option is selected. Existing source-bound checkout/payment and atomic consumption enforce the chosen terms; downloading does not itself transfer ownership or admit a trade.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.10Claim SHA-256 a0071b9e56cbb7c688ee29f9a6a2825344aaa64ca82edc7d780a73df3e80b08b
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Actual transaction Original export

Receipt and Ledger exports bind the actual transaction, participant and original-source reader. Bank's receipt-share correction passes that existing context to downloadLedgerOriginal instead of serializing the receipt display. The actual saved file and its offline verification remain explicit acceptance evidence.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.11Claim SHA-256 07fdef5a91f7bf2d3a55818b70206f3da05805473cf83d4c03ab1235e82e6e9d
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Complete verification-kit custody

A kit carries the exact Original, its existing proof/history and the standalone verification closure required to inspect it. Incomplete source cannot be represented as a complete kit; file download and kit download retain distinct contracts.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.12Claim SHA-256 b0419c6ace197e84297c9b50adaf11b6a66fed3c0bf23a33f4db62862bcc0a39
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Bounded canonical verification

PNG/provenance extraction and native carrier readers enforce their existing execution bounds and preserve malformed-proof precedence. Capacity refusal reports that validity was not evaluated. It cannot become a forged acceptance or an invalid-proof verdict.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.13Claim SHA-256 36f173a4424a7337d4c6bc6afb85eb0aaf256c7399e0e746c5f2ce0f93216f8a
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Canonical verifier consumers

SDK, standalone verifier, Offline Studio and Docs Workbench derive from their declared canonical implementation. The Workbench closure includes the actual browser runtime dependencies; generated delivery resources cannot drift into a separate proof interpretation.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.14Claim SHA-256 9867a084739e3175110fa6004cd02042bbdc7389cdc3d1e8a1f3c10989b30849
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Uncut transaction download transport

The exact GET transaction Moment export uses the existing network-only service-worker rail. Its full exporter lifetime and bytes survive beyond the unrelated 3.5-second API snapshot cutoff; origin errors remain actual errors and private attachments are not cached as public snapshots.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.15Claim SHA-256 0c0551760c2274a2d2db9f6456b20fa400f2c46462e7806d9fe0c67d94afc721
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Connected Notes and Wallet funding continuity

Bank Note funding/redemption, exact quotes, device attestation, connected Account Notes and Wallet-ledger projection reuse existing custody and financial writers. Composite allocation conserves its funding Source; downloaded bearer, accepted receiving, Settlement and current spend authority remain separately inspectable stages.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.16Claim SHA-256 8bd5a201ac149362fdca4649853d0404484c77b32e3a04bceaeadb6a6ff0d2f4
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Financial Originals and finite rights

Existing Account grants, ordinary owner consent, canonical Source and SDK signing bind Wallet/Market operands and finite execution rights. Scoped source admission, local computation, causal adoption, receipts, receiving and handoff preserve original Kai and existing numerical law. Complete Bank activation and global fill/cancel qualification remain explicit boundaries.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.17Claim SHA-256 7e8e059744ccd3181f77fadbf11f29b6ba97971683e62ea033152c7232411d99
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Account Statement from the retained Original

Saving an Account Statement reuses the already verified held account-proof bytes with a clear file title. It performs no publication or resealing. The separate opt-in public image/link and Ledger verification kit retain their own source and disclosure boundaries.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.18Claim SHA-256 d77c0722e3de5268527aa6fe6b34ee4026ef749e77acec96a8ed09ee006e0085
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Recoverable payment outcomes

Pending Send cancellation/resolution uses the original saved request and existing atomic outcome rather than submitting another payment. Profile display/readiness work cannot become financial authority or permit duplicate execution. A terminal refusal and an unknown outcome retain their distinct recovery contracts.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.19Claim SHA-256 3bc429df2d0fbf64f98330a870508fd73bcbefd91d1df5145db9808e342250ed
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Funding disclosure and retained ancestry

Transfer, Note, Reserve and certificate records retain source links, funding allocations and original coordinates. Public/private display reuses carried supporting history; a projection cannot manufacture missing evidence or silently redefine a funding source. The exact complete-ancestry acceptance status belongs in conformance.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.20Claim SHA-256 a11160448c97eafc4c239078225954c8272a4bc672b447b49eb26c703f63673e
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Public Original earning and cash preservation

Qualified public PBI-signed Originals compose the existing Settlement admission path. Wallet projection reuses the accepted signing result while preserving prior cash and funding history. An earning display does not establish a sale, seller proceeds or a separately unexecuted payment.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.21Claim SHA-256 afe33dacead403422fb4cfbe79777bb051eb5f6c3c8161abfdd9501535fc94ed
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Exact holdings and market coordinates

Portfolio and trade records retain quantity, cost, realized facts and issuance coordinates. Stable Receiz ID selects the public Original's market key, so a name presentation cannot create another asset or reset history. Retained historical prefixes remain binding beneath current display.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.22Claim SHA-256 61992246e49c7446db78434eba8d15ec7bf9320f97b43679424f1c302b939b38
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Merchant Counter

Owner-bound catalogs, variants/modifiers, taxes, discounts, fixed checkout requests, stock reservations and atomic inventory lifecycles compose existing payment machinery. A catalog entry or reservation cannot stand in for completed payment and delivered custody.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.23Claim SHA-256 3305318dec19045fb6283dddddddc78d5d627b40536fe984576eead1bc290034
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Calendar offers and paid appointments

Owner timezone and accepted offer terms govern availability, per-guest price, payment handoff and recovery. Native Calendar/Message continuity, room evidence, recordings and reminders retain the accepted booking and Account relationship.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.24Claim SHA-256 7c667762097e7c7c5359116f08ec6ee432d457e0956cd6650a9e74c04846f9d7
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Owner-controlled booking notice

Saved preferences permit same-day booking and minimum advance notice from 0 to 43,200 minutes, retaining the existing ten-minute default. Same-day exclusion is evaluated in the owner's saved timezone; visitor display settings cannot redefine availability.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.25Claim SHA-256 8cff8764c96ab1fe8a7f3ea3b2641f9873944174b95419c329b7962077ae2414
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Meeting and invitation continuity

Invitations, guest confirmations, existing conversations, Calendar events and real meeting entrances remain attached to their accepted recipient and booking. Visitor-local labels display the booked instant without changing the owner's schedule or the payment terms.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.26Claim SHA-256 583084a68d161264cf460076d7a3b89249271aa0e7cc856ea8435566dbf01382
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Scoped Twin and organizer execution

Owned Twins reuse their brain and complete conversation context across streaming and supported contact, Calendar, organizer and financial tools. Owner/visitor boundaries remain explicit; shared cookies or request probes cannot expose another person's private memory or contacts.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.27Claim SHA-256 c38400575a3c32ac7079b5e32458cbc7ec9cbc489653108d83d0f090bfec4fa5
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Actual provider and usage accounting

Provider continuations, sponsored replies, reserved capacity and metered usage bind accepted funding and actual execution. Existing independent preparation runs concurrently where supported; redundant serial preparation and artificial streaming waits are removed without creating a new budget authority.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.28Claim SHA-256 098e4cc21b8eec51731b56224635b69ce33009242ec22a6feeeb043dbe03c2ef
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Receiz-ID email in native Messages

Current and permanently retained aliases bind the exact Account UID. Signed external envelopes, verified private MIME and provider/RFC delivery identifiers remain external observations inside existing Message custody, preserving the same correspondent and thread.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.29Claim SHA-256 83bd917be019b06a85f2841a793fc27d4566a4bab2af65335f5f60080961a64e
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Bounded recipient adoption and reply privacy

One-use recipient access, alias guards and reply correlation preserve the intended Account and conversation. Recipient-only login links stay out of replies and shared exports. SMTP possession does not become native authorship, identity admission or financial authorization.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.30Claim SHA-256 87fc7cf55674087402d9206a4844267d8e8902ca2446e776935ce55da78e959f
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Existing conversation presentation

Bank correspondence reuses its registered-client context, verified recipient, existing conversation and established email design. A separate receiving credential preserves the sending boundary; routing activation and later presentation deployment have their own evidence.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.31Claim SHA-256 1e28cb17a6f1704b335183943a727949f06460dcc9f7e2d48193a2935dd1779d
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Shared exact projections

Existing receipt, download-link and DER/signature helpers replace competing copies while preserving input/output and historical signature behavior. Synchronous viewport ownership lets one active writer survive another writer's cleanup without a paint delay or a new loading interval.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.32Claim SHA-256 3649e026aeb55ef9eaf0703bc2d18ff81ec8d7c478d52b795064c2b9782b5f25
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Targeted service security

Operator-only billing closeout, atomic challenge consumption, request-local World overrides and public-proof HTTPS/DNS/IP/TLS/redirect/resource controls protect their existing boundaries. They introduce no server, vendor allowlist or external issuer requirement for ordinary native local PBI signing.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.33Claim SHA-256 54cdfe21a4ad4cb2f8fd92597e9e38580bdb4a3741b0a63835fd93561e5ecdf9
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Patched dependency closure

Targeted framework, image, MCP and transitive corrections preserve the established Streamdown 2.5 renderer, actual Creator DOM and frozen lint policy. The existing patched framework renderer supplies proof images; ordinary PNG controls retain exact output and unsafe SVG inputs retain refusal/escaping.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.34Claim SHA-256 845a9ef1b54703d91527478c0d7eb6bce734f170e548cc185330b3dda48ed755
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Coordinated public capability coverage

The current catalog contains 1,529 entries: 705 callable SDK exports, 425 client methods, 356 full MCP tools and 43 AI skills, with 37 manifests and 34 prompts. The added projectReceizAccountDisplayName projects existing account-name truth. No public export is removed; inventory membership creates no grant, adapter or private custody.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.35Claim SHA-256 a5842a94437d391cb2160357f7440a8e22f22af05986ab68d06261d1d63cdded
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Byte-exact package and installation delivery

All three public 129.5 archives match qualification. The current public AI installation kit carries its checked runtime/proof resources, while every historical content-addressed download remains unchanged. Installed consumer, application, standalone and disclosure qualification remain independently recorded.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.36Claim SHA-256 d10202797a8970e1b4aec2949b016fe255ba889e58f9df7858446994e3791ff7
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Complete release provenance

The release book includes all 399 post-tag commits, the separate current candidate, inherited registry/matrix, compatibility, migration inventory, practical integration, governance and exact conformance. Historical v129 closeout and failed attempts remain at their original coordinates.

Authority & EvidenceClaim sources and exact digests
capabilitiesEnabled.37Claim SHA-256 a567c05eb8bfb083bb633c284034c20b5cac5b9af3291e52ff7e2480cee222b3
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Primitive boundary

Primitives affected

  • proof
  • identity
  • ownership
  • settlement
  • provenance
  • media
  • transfer
  • verification
  • public-witness
  • local-truth
  • continuity
  • market
  • certificate
  • note
  • reserve
  • sealed-artifact
  • governance
Authority & EvidenceClaim sources and exact digests
primitivesAffectedClaim SHA-256 53ae696db4dc42c3521fa313d9ef89af9d67a4cf5cf860fabe044115876af038
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Compatibility

Compatibility

Published packages

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).

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.0Claim SHA-256 24f8c79e3e3e547ddb3d1697fcb0b9760da7b4c1bafcc8b0a3bebfeab6e39d79
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Major compatibility

The declared range stays >=129.0.0 <130.0.0. This release does not activate v130 or rename historical operation/schema versions.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.1Claim SHA-256 e21993f88c6c9efb34572fd196a4ea034c1c11422d6d04cef102ee75d1c8246a
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Constitutional registry

The admitted 133-law v127 registry remains byte-identical, digest 8d0b5b839d02d9efbd4306cc99410595a183705c2670b76d2567eaaaade99065. No new constitutional issuer or ruleset is introduced.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.2Claim SHA-256 572f77fa467d13ee9ccfd9395a3f8d5c8bf1ae80f3c3108c49921379ff912875
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Operation matrix

The admitted digest remains c4e0cff348b62f31db2bb2ffdeec533a92ca3a6d476757bb9b559ac58a7875e1. Inventory expansion and distribution versioning cannot enlarge an operation's authority.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.3Claim SHA-256 94a694b27cf376122a07429dcb1bf9f922168eff38bdb225ca981206682ce8f9
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Historical verification

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.4Claim SHA-256 d24a918d764f2716d31b50bb8d1439eb4854f98556b85d6c6cf924460cb815f3
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Signed Originals

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.5Claim SHA-256 e08b7d4928ee29733d171b2298af618643774ff3643325c7cc1137904f537302
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Source and local custody

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.6Claim SHA-256 0836676baa82e63b5b1304eb3f72cb645006a6d6b0d93942a73e6b7a5ed6bb21
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Identity and account entry

The account-entry freeze remains bound to 6e0d71c3f0e8b3092b4ec97eef39f5927667a01f. Receiz ID, PBI/passkey recovery and admitted device bindings retain their established identity boundaries.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.7Claim SHA-256 0d9a05f3208de196a0409eaecd11c762e20686b7297435defa96cafd9aeb03c4
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Public Receiz ID

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.8Claim SHA-256 07616d15034178313147fc9ab168f2749afc58ab850b9b6050b94dbd0bad886d
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Registered applications

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.9Claim SHA-256 98f56623a643956d19d29c6bcf409b6293f25ed78440b3003a14650ac0c4a6e4
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Public collections

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.10Claim SHA-256 f2c3ba7e15647d235e7ba35e6a526b97103318965163a53ba935c58156a7e8d3
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Market history

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.11Claim SHA-256 8c400a06fe196eac48c72f2810de02e4b68011bfb9c878e0915c4fca4a91d92e
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Full SDK/MCP/AI surface

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.12Claim SHA-256 2efe951c88c8dd3b26307a2494d07e228dd71ceca9d919c2eaeace7671bd7fba
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Restricted installation

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.13Claim SHA-256 20d1f4bc4402051f4ab580dda7f07bff6b835d45d1494224e4908a610b18c218
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Financial evidence

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.14Claim SHA-256 f78e9b37d8f508ab06171231e5b0889e69e7f6878d42a2ffd7d824db35a93256
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Offline Notes

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.15Claim SHA-256 654fb76c0f9a2295e15121f8f644cf1d573abf815c7e47e125a694f6930e7d18
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Valuation and time

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.16Claim SHA-256 36680aa96320f745492a9ae17b5fb34cecb7e5689e1fe0be33d27ab0e876b844
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Canonical consumers

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.17Claim SHA-256 53be67ced71244072daa715602c1f838ce9b49a76aac749a61e4b67a12318bcc
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Optional services

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.18Claim SHA-256 dcd71efe9e68778e6d75bd8c1f1eca7e3a03141c217b2b693ff04759caef1df3
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Deployment and provider selection

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.19Claim SHA-256 a2fb250d21b18edf35e3fd47ee1f7a8a49110a268280d22b2e35712ef93d140f
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Historical records

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.

This exact v129.5.0 compatibility boundary remains binding.

Authority & EvidenceClaim sources and exact digests
compatibility.20Claim SHA-256 739d3ce9cd189e94849113709fd3942b07c08a3f2273121a9a219c64613f07c5
docs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379

Migration

Migration

Required: true

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.

  1. Install @receiz/ai-skills@129.5.0, @receiz/sdk@129.5.0 and @receiz/mcp-server@129.5.0 through the consumer's normal package manager. Retain registry URLs/integrity in its actual lockfile; do not substitute repository aliases or local archive paths as release adoption.
  2. Preserve exact registered application IDs and actual grants, audience, owner, consent, nonce, replay and revocation boundaries. Public Receiz ID projection does not replace an issued application coordinate or device signing proof.
  3. Keep admitted complete Identity Records, Original/media bytes, Source heads and histories. Reuse the inherited registry and existing verifiers; do not clear storage or reseal files to make an update appear current.
  4. For a hosted deployment, inspect its real applied migration ledger and definitions, then apply only missing forward migrations in the repository's established order under their own guards. A file's presence in Git cannot prove application; an earlier applied receipt cannot certify a different database. Preserve existing constraints, owner/security metadata, locks and zero-write refusals.
  5. Follow the current operation-specific configuration and custody requirements for Calendar/Counter, username email, Notes, account financial Sources and public delivery. Recipient-only links, private MIME, signing secrets and deployment credentials remain outside public source and shared exports.
  6. Preserve existing production provider selection. Implemented native byte/Account/Subject components and scoped financial-source tests do not activate unfinished whole-application Crystal/Settlement/hosted composition. Qualify an actual cutover separately.
  7. Regenerate current release identity, inventories, canonical standalone resources, Workbench runtime closure and public documentation through their existing source-owning commands. Keep historical captures and content-addressed downloads unchanged.
  8. Qualify the actual installed consumer and its used proof/export/execution path. Check complete first HTML, owner navigation, downloaded Original and offline verification, separate kit completeness, current migration state and deployment readback where those are claimed.
  9. Capture final release and public disclosure evidence at their exact source/tree coordinates. Generate a new attestation only after its required gates pass; never reuse an old signature over changed bytes.
Authority & EvidenceClaim sources and exact digests
migrationClaim SHA-256 63bf78b7d7740b4785520e6b507471803c122b0726899bb8d1a6638208bb9c3c
docs/releases/v129.5.0-migration.mdSHA-256 c16287c03d4d41bf4bd5e12fabf6e73fe11699b86003d104416be7424e7d9ba1

Qualification

Conformance

Full post-correction SDK test suite passed 1,142/1,142 plus six package-boundary cases; full MCP test suite passed 437/437.

Passed · Full post-correction SDK test suite passed 1,142/1,142 plus six package-boundary cases; full MCP test suite passed 437/437.

Authority & EvidenceClaim sources and exact digests
conformance.0Claim SHA-256 bbb44a6c4ed12397297b4668f3e57fe50fae04cbef0567649dfbfd0677a89bd5
docs/releases/v129.5.0-checklist.mdSHA-256 b71078aa7594e2804ead8c72fc005b93d04982312284e658d3a41154ab10624e

Prior packed-archive invocation of pnpm test:coordinated-package-release passed, including packed documentation and installed CLI/stdio tests against the exact retained archives. This item binds that retained archive qualification.

Passed · Prior packed-archive invocation of pnpm test:coordinated-package-release passed, including packed documentation and installed CLI/stdio tests against the exact retained archives. This item binds that retained archive qualification.

Authority & EvidenceClaim sources and exact digests
conformance.1Claim SHA-256 f0f5a41fc0c88da74d8c49a27107321b8605843fe86e132dcdeca748a8c2f7e1
docs/releases/v129.5.0-checklist.mdSHA-256 b71078aa7594e2804ead8c72fc005b93d04982312284e658d3a41154ab10624e

Current public AI installation kit tests passed through actual packaged runtime/proof/tamper controls; 53 historical files retained unchanged.

Passed · Current public AI installation kit tests passed through actual packaged runtime/proof/tamper controls; 53 historical files retained unchanged.

Authority & EvidenceClaim sources and exact digests
conformance.2Claim SHA-256 30ff29c3c3578500bca5bbf012cd1038c496c565d5f438607787e39a661ab5b2
docs/releases/v129.5.0-checklist.mdSHA-256 b71078aa7594e2804ead8c72fc005b93d04982312284e658d3a41154ab10624e

Exact transaction GET worker correction qualified by scoped RED→GREEN and combined 71/71 worker tests; observed old live failure retained separately.

Passed · Exact transaction GET worker correction qualified by scoped RED→GREEN and combined 71/71 worker tests; observed old live failure retained separately.

Authority & EvidenceClaim sources and exact digests
conformance.3Claim SHA-256 192c04e24a0ca1fe61a8e58830ca7b5748eb91aca4c1601989f0aa35a4c5ab32
docs/releases/v129.5.0-checklist.mdSHA-256 b71078aa7594e2804ead8c72fc005b93d04982312284e658d3a41154ab10624e

Governance check, evidence check and existing artifact-signature verification passed on the current Source.

Passed · Governance check, evidence check and existing artifact-signature verification passed on the current Source.

Authority & EvidenceClaim sources and exact digests
conformance.4Claim SHA-256 6a08b2c820881018ffc238f595778f401aac1ad20cccf4467c2208c68661e801
docs/releases/v129.5.0-checklist.mdSHA-256 b71078aa7594e2804ead8c72fc005b93d04982312284e658d3a41154ab10624e

Infrastructure disclosure 1.3.0 preserved the full 168-file signed 1.2.0 tree, adopted exact 129.5 SDK/source inventory and passed 15/15 tests plus SDK conformance. Its existing designated-owner proof verifies all 357 inventory files at 81532462fd0fd6594dc172cb7b5c103ab21ce416; an altered projection is refused. See the exact independent proof boundary in [Governance](v129.5.0-governance.md#post-tag-disclosure-governance-closeout--14-november-2026).

Passed · Infrastructure disclosure 1.3.0 preserved the full 168-file signed 1.2.0 tree, adopted exact 129.5 SDK/source inventory and passed 15/15 tests plus SDK conformance. Its existing designated-owner proof verifies all 357 inventory files at 81532462fd0fd6594dc172cb7b5c103ab21ce416; an altered projection is refused. See the exact independent proof boundary in [Governance](v129.5.0-governance.md#post-tag-disclosure-governance-closeout--14-november-2026).

Authority & EvidenceClaim sources and exact digests
conformance.5Claim SHA-256 94b9f90ea6835d99e4b0259787460e19190f6046beae88d77a5a05c629534dd6
docs/releases/v129.5.0-checklist.mdSHA-256 b71078aa7594e2804ead8c72fc005b93d04982312284e658d3a41154ab10624e

Control boundary

Governance

Verification
Passed
Declared change class
High Risk
Release approval
v129.5.0-application-gate-closeout-2026-11-14-sha256-437519cee92c75be4155f613d901ea0065640ccdcf52541f64289010e5866f3f
Risk owner
bjklock

Dated signed attestations apply only to their exact commit, tree, and build; package publication, deployment, and production smoke remain independent evidence dimensions.

Explicit single-owner approval under the existing Identity Seal; no independent review occurred.

Authority & EvidenceClaim sources and exact digests
governanceClaim SHA-256 a79d305d348a135050ca85469349e9e754e7745f92baad4ed88cc202c185e28e
docs/releases/v129.5.0-checklist.mdSHA-256 b71078aa7594e2804ead8c72fc005b93d04982312284e658d3a41154ab10624eartifacts/release-attestations/2026-11-15T01-24-29-387Z-a78415e2bb7a.jsonSHA-256 3a29170eb1269bd1bcf13c63f498d1680298a0c73d8be9d42c359426fb6aec47

Registry boundary

Registry

Version
127.0.0
Binding
Inherited byte-identically from v127.0.0; no patch registry was created.
Digest
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

Archive projection

Audience, domain, and change-kind facets

Audiences
people · creators · businesses · developers · institutions
Domains
proof · identity · ownership · provenance · verification · local-truth · continuity · market · settlement · reserve · note · calendar · commerce · messages · intelligence · infrastructure · governance
Change kinds
capability · correction · compatibility · migration · governance · performance · security
Authority & EvidenceClaim sources and exact digests
facets.audiencesClaim SHA-256 c46740193deec68668a5ddad28b6a0aba746a7386f07d02578ebd8f289f337f4
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8
facets.domainsClaim SHA-256 542deb8a8cd1677b594e918b6b2ec7723eb80735f49d467919d3013ebe967fb5
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8
facets.changeKindsClaim SHA-256 47e96289107150cb601c935f8c010cf219877c8a8ca98adf01b0ee48dc237dfa
docs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8

Independent dimensions

Release boundary status

Repository release
Documented
Git tag
Present
Package publication
Confirmed
Deployment
Not Performed
Production smoke
Not Performed
Signed attestation
Present
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

Exact source bytes

Provenance

This Academy record is a projection beneath its sources. Record SHA-256 153526bba8aca3f3eef166c20161d26378f2fac227803ff5a341e81942b352fa. Source-family inventory: complete.

attestation · evidenceartifacts/release-attestations/2026-11-15T01-24-29-387Z-a78415e2bb7a.jsonSHA-256 3a29170eb1269bd1bcf13c63f498d1680298a0c73d8be9d42c359426fb6aec47
registry-digest · evidencedocs/releases/v127.0.0-constitution-registry.digestSHA-256 a8766e68d55394499fd7a92bb9b418c89730f375c84bc678757bdbd8a977db2e
registry · normativedocs/releases/v127.0.0-constitution-registry.jsonSHA-256 f9f713c7a4d75ab4ffccc4551cdaeaa6e9268978222d7f8cbbc13e3683155c8a
supporting · evidencedocs/releases/v129.5.0-bank-hosted-ci-evidence.jsonSHA-256 aad975ef9095936dfc960af66a3a2e34f54b82660acaecf51a161d921b8b7435
supporting · evidencedocs/releases/v129.5.0-bank-local-evidence.jsonSHA-256 aed3c1a66cbee5373d3bbb2f7f76d722355e313c06b4b69db1ddc34bba6de1d9
checklist · evidencedocs/releases/v129.5.0-checklist.mdSHA-256 b71078aa7594e2804ead8c72fc005b93d04982312284e658d3a41154ab10624e
commit-ledger · evidencedocs/releases/v129.5.0-commit-history.mdSHA-256 1986664790937e26c045e0f1c52a3151494d69975416950214aa31a26134d26f
compatibility · normativedocs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379
conformance · normativedocs/releases/v129.5.0-conformance.mdSHA-256 9cf201839fa766b911864ea326258a4c711fa13d608a4443bb38925468b9c168
supporting · evidencedocs/releases/v129.5.0-forward-source-inventory.jsonSHA-256 a1bc7c5730ccb0f8b02cd99db2893cd16e7db18d0af1c92a2bee158ac842a7d4
governance · normativedocs/releases/v129.5.0-governance.mdSHA-256 677068fd54ba2e1990970cbe88f9e795727f28da56c6db404ea996e56b80c9fa
supporting · evidencedocs/releases/v129.5.0-integration.mdSHA-256 7a10282d4e649012345a1e100e9ad16d72ebcd79b9abc404b8e980027ab3758d
migration · normativedocs/releases/v129.5.0-migration.mdSHA-256 c16287c03d4d41bf4bd5e12fabf6e73fe11699b86003d104416be7424e7d9ba1
supporting · evidencedocs/releases/v129.5.0-package-candidates.jsonSHA-256 189624d0094adc581490ff723b91865f8a97bece3cae40ce6853264850f5c0f0
supporting · evidencedocs/releases/v129.5.0-package-publication-evidence.jsonSHA-256 108c2c60ef0e4af12ad140708e073e3a8429ef2a449fc505e1e8afba288781bb
process · normativedocs/releases/v129.5.0-process.mdSHA-256 a54170d150e6aaf9479ae2bbc22c3c864b40f1972bf214b8bcbd5ecf77d48d33
product-truth · normativedocs/releases/v129.5.0-product-truth.mdSHA-256 e0b2eaf669e5f443a131badafd601d657c8004b40fabd14b31e4aa024ee36553
supporting · evidencedocs/releases/v129.5.0-registry-binding.jsonSHA-256 6fee39202a5cf7bfcca92d050de5380a1e59268371980c0f9eec0887ea0cec51
regression · normativedocs/releases/v129.5.0-regression-lessons.mdSHA-256 be96fc14faf6dc406c1c62b4f2f3d0efef4bd2c2b8c38c8e0a03940c3ae3c0de
supporting · evidencedocs/releases/v129.5.0-release-freeze-evidence.jsonSHA-256 437519cee92c75be4155f613d901ea0065640ccdcf52541f64289010e5866f3f
supporting · evidencedocs/releases/v129.5.0-source-history.jsonSHA-256 aa9f4bc6a39df6cb6ab8b7dfbff8054b8cc5007efbe21af2427915e46563d9fc
main · normativedocs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8
supporting · evidencegit:refs/tags/v129.5.0SHA-256 e8dfc84a4de2de1048889b7ef5cff063b8815717c2eba5e0109cd667bd2ed194
Authority & EvidenceClaim sources and exact digests
sourceFamilyClaim SHA-256 b09541c04be08caf8ecf6c95b626458e0d4e2697d256560d9a0bf3ce798120e3
artifacts/release-attestations/2026-11-15T01-24-29-387Z-a78415e2bb7a.jsonSHA-256 3a29170eb1269bd1bcf13c63f498d1680298a0c73d8be9d42c359426fb6aec47docs/releases/v127.0.0-constitution-registry.digestSHA-256 a8766e68d55394499fd7a92bb9b418c89730f375c84bc678757bdbd8a977db2edocs/releases/v127.0.0-constitution-registry.jsonSHA-256 f9f713c7a4d75ab4ffccc4551cdaeaa6e9268978222d7f8cbbc13e3683155c8adocs/releases/v129.5.0-bank-hosted-ci-evidence.jsonSHA-256 aad975ef9095936dfc960af66a3a2e34f54b82660acaecf51a161d921b8b7435docs/releases/v129.5.0-bank-local-evidence.jsonSHA-256 aed3c1a66cbee5373d3bbb2f7f76d722355e313c06b4b69db1ddc34bba6de1d9docs/releases/v129.5.0-checklist.mdSHA-256 b71078aa7594e2804ead8c72fc005b93d04982312284e658d3a41154ab10624edocs/releases/v129.5.0-commit-history.mdSHA-256 1986664790937e26c045e0f1c52a3151494d69975416950214aa31a26134d26fdocs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379docs/releases/v129.5.0-conformance.mdSHA-256 9cf201839fa766b911864ea326258a4c711fa13d608a4443bb38925468b9c168docs/releases/v129.5.0-forward-source-inventory.jsonSHA-256 a1bc7c5730ccb0f8b02cd99db2893cd16e7db18d0af1c92a2bee158ac842a7d4docs/releases/v129.5.0-governance.mdSHA-256 677068fd54ba2e1990970cbe88f9e795727f28da56c6db404ea996e56b80c9fadocs/releases/v129.5.0-integration.mdSHA-256 7a10282d4e649012345a1e100e9ad16d72ebcd79b9abc404b8e980027ab3758ddocs/releases/v129.5.0-migration.mdSHA-256 c16287c03d4d41bf4bd5e12fabf6e73fe11699b86003d104416be7424e7d9ba1docs/releases/v129.5.0-package-candidates.jsonSHA-256 189624d0094adc581490ff723b91865f8a97bece3cae40ce6853264850f5c0f0docs/releases/v129.5.0-package-publication-evidence.jsonSHA-256 108c2c60ef0e4af12ad140708e073e3a8429ef2a449fc505e1e8afba288781bbdocs/releases/v129.5.0-process.mdSHA-256 a54170d150e6aaf9479ae2bbc22c3c864b40f1972bf214b8bcbd5ecf77d48d33docs/releases/v129.5.0-product-truth.mdSHA-256 e0b2eaf669e5f443a131badafd601d657c8004b40fabd14b31e4aa024ee36553docs/releases/v129.5.0-registry-binding.jsonSHA-256 6fee39202a5cf7bfcca92d050de5380a1e59268371980c0f9eec0887ea0cec51docs/releases/v129.5.0-regression-lessons.mdSHA-256 be96fc14faf6dc406c1c62b4f2f3d0efef4bd2c2b8c38c8e0a03940c3ae3c0dedocs/releases/v129.5.0-release-freeze-evidence.jsonSHA-256 437519cee92c75be4155f613d901ea0065640ccdcf52541f64289010e5866f3fdocs/releases/v129.5.0-source-history.jsonSHA-256 aa9f4bc6a39df6cb6ab8b7dfbff8054b8cc5007efbe21af2427915e46563d9fcdocs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8git:refs/tags/v129.5.0SHA-256 e8dfc84a4de2de1048889b7ef5cff063b8815717c2eba5e0109cd667bd2ed194
provenanceClaim SHA-256 5cb107ea8c24943e421c1fa9993045233a488884ee72aedaec8717aa19290395
artifacts/release-attestations/2026-11-15T01-24-29-387Z-a78415e2bb7a.jsonSHA-256 3a29170eb1269bd1bcf13c63f498d1680298a0c73d8be9d42c359426fb6aec47docs/releases/v127.0.0-constitution-registry.digestSHA-256 a8766e68d55394499fd7a92bb9b418c89730f375c84bc678757bdbd8a977db2edocs/releases/v127.0.0-constitution-registry.jsonSHA-256 f9f713c7a4d75ab4ffccc4551cdaeaa6e9268978222d7f8cbbc13e3683155c8adocs/releases/v129.5.0-bank-hosted-ci-evidence.jsonSHA-256 aad975ef9095936dfc960af66a3a2e34f54b82660acaecf51a161d921b8b7435docs/releases/v129.5.0-bank-local-evidence.jsonSHA-256 aed3c1a66cbee5373d3bbb2f7f76d722355e313c06b4b69db1ddc34bba6de1d9docs/releases/v129.5.0-checklist.mdSHA-256 b71078aa7594e2804ead8c72fc005b93d04982312284e658d3a41154ab10624edocs/releases/v129.5.0-commit-history.mdSHA-256 1986664790937e26c045e0f1c52a3151494d69975416950214aa31a26134d26fdocs/releases/v129.5.0-compatibility.mdSHA-256 2b4d78dcbd2040d2ff97bce8bdb729ae032f311ce46204d5bc75a38ee3583379docs/releases/v129.5.0-conformance.mdSHA-256 9cf201839fa766b911864ea326258a4c711fa13d608a4443bb38925468b9c168docs/releases/v129.5.0-forward-source-inventory.jsonSHA-256 a1bc7c5730ccb0f8b02cd99db2893cd16e7db18d0af1c92a2bee158ac842a7d4docs/releases/v129.5.0-governance.mdSHA-256 677068fd54ba2e1990970cbe88f9e795727f28da56c6db404ea996e56b80c9fadocs/releases/v129.5.0-integration.mdSHA-256 7a10282d4e649012345a1e100e9ad16d72ebcd79b9abc404b8e980027ab3758ddocs/releases/v129.5.0-migration.mdSHA-256 c16287c03d4d41bf4bd5e12fabf6e73fe11699b86003d104416be7424e7d9ba1docs/releases/v129.5.0-package-candidates.jsonSHA-256 189624d0094adc581490ff723b91865f8a97bece3cae40ce6853264850f5c0f0docs/releases/v129.5.0-package-publication-evidence.jsonSHA-256 108c2c60ef0e4af12ad140708e073e3a8429ef2a449fc505e1e8afba288781bbdocs/releases/v129.5.0-process.mdSHA-256 a54170d150e6aaf9479ae2bbc22c3c864b40f1972bf214b8bcbd5ecf77d48d33docs/releases/v129.5.0-product-truth.mdSHA-256 e0b2eaf669e5f443a131badafd601d657c8004b40fabd14b31e4aa024ee36553docs/releases/v129.5.0-registry-binding.jsonSHA-256 6fee39202a5cf7bfcca92d050de5380a1e59268371980c0f9eec0887ea0cec51docs/releases/v129.5.0-regression-lessons.mdSHA-256 be96fc14faf6dc406c1c62b4f2f3d0efef4bd2c2b8c38c8e0a03940c3ae3c0dedocs/releases/v129.5.0-release-freeze-evidence.jsonSHA-256 437519cee92c75be4155f613d901ea0065640ccdcf52541f64289010e5866f3fdocs/releases/v129.5.0-source-history.jsonSHA-256 aa9f4bc6a39df6cb6ab8b7dfbff8054b8cc5007efbe21af2427915e46563d9fcdocs/releases/v129.5.0.mdSHA-256 7f9b600a53e59c8e834f94933ac78a3fd59c685c9b38ca5b3fcf7229970a07c8git:refs/tags/v129.5.0SHA-256 e8dfc84a4de2de1048889b7ef5cff063b8815717c2eba5e0109cd667bd2ed194