v129.0.0

Existing registered applications can use their unchanged Receiz-issued client ID across SDK construction, native requests, source qualification, authority sessions, execution and replay. Registered rc IDs and existing native slugs retain exact spelling and case; an alias cannot replace the issued coordinate.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Existing registered applications can use their unchanged Receiz-issued client ID across SDK construction, native requests, source qualification, authority sessions, execution and replay. Registered rc IDs and existing native slugs retain exact spelling and case; an alias cannot replace the issued coordinate.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

The forward migration changes nine application CHECKs and five RPC predicates while preserving deployed security metadata, foreign keys, scope checks, revocation, nonce replay, custody and zero-write failures. Production application of that exact migration is independently recorded; historical artifacts and identifiers are not rewritten.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

The forward migration changes nine application CHECKs and five RPC predicates while preserving deployed security metadata, foreign keys, scope checks, revocation, nonce replay, custody and zero-write failures. Production application of that exact migration is independently recorded; historical artifacts and identifiers are not rewritten.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

OIDC client and delegated-agent selectors expose the shared supported scope catalog, including existing financial scopes. Developers select grants for the actual operations; device-held identity proof, explicit consent and issued scopes remain required, while local proof reads acquire no invented OAuth requirement.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

OIDC client and delegated-agent selectors expose the shared supported scope catalog, including existing financial scopes. Developers select grants for the actual operations; device-held identity proof, explicit consent and issued scopes remain required, while local proof reads acquire no invented OAuth requirement.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Seven added adapters expose existing wallet inspection, transfer, checkout, checkout-session inspection, embedded checkout, sealed-note download and canonical bearer-artifact claim. They compose existing SDK financial primitives beneath source, grant and consent authority; funding, payment, delivered bearer, claim, use and proceeds remain separate evidence stages.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Seven added adapters expose existing wallet inspection, transfer, checkout, checkout-session inspection, embedded checkout, sealed-note download and canonical bearer-artifact claim. They compose existing SDK financial primitives beneath source, grant and consent authority; funding, payment, delivered bearer, claim, use and proceeds remain separate evidence stages.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

The separately reviewed ChatGPT Marketplace profile retains 195 nonfinancial tools and enforces its World limits at both dispatch and wrapped-client boundaries. General developer MCP exposes the full 356-tool library; configuring a restricted installation does not redefine the full library or enable an excluded financial operation.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

The separately reviewed ChatGPT Marketplace profile retains 195 nonfinancial tools and enforces its World limits at both dispatch and wrapped-client boundaries. General developer MCP exposes the full 356-tool library; configuring a restricted installation does not redefine the full library or enable an excluded financial operation.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Eleven added adapters expose current public-proof observation, World profile/message/welcome/booking/streaming, sports history/rollups/badge, verification conformance and complete Record creation. Exact confirmation, completed stream events, bounded projections and error rejection preserve the actual SDK/host contracts without automatic retries.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Eleven added adapters expose current public-proof observation, World profile/message/welcome/booking/streaming, sports history/rollups/badge, verification conformance and complete Record creation. Exact confirmation, completed stream events, bounded projections and error rejection preserve the actual SDK/host contracts without automatic retries.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Record creation returns the actual sealed PNG and retains explicit JSON compatibility. The producer reuses the existing local anchor before Signature V4; the MCP adapter verifies the enclosing proof and privately delivers exact bytes. A remote save can precede failed delivery, so unknown outcomes require resolution before retry.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Record creation returns the actual sealed PNG and retains explicit JSON compatibility. The producer reuses the existing local anchor before Signature V4; the MCP adapter verifies the enclosing proof and privately delivers exact bytes. A remote save can precede failed delivery, so unknown outcomes require resolution before retry.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Wallet-note download returns the original PNG as a Blob, and the MCP path verifies that complete sealed file before private delivery. Canonical bearer claim opens the stronger artifact, uses the existing ownership coordinator and verifies the successor; raw note-token extraction gains no new admission or direct claim authority.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Wallet-note download returns the original PNG as a Blob, and the MCP path verifies that complete sealed file before private delivery. Canonical bearer claim opens the stronger artifact, uses the existing ownership coordinator and verifies the successor; raw note-token extraction gains no new admission or direct claim authority.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Browser and Node consumers can import the existing phi/kosmos-vφ-5 calculator, immutable policy, checksum, serialization and rounding from the pure valuation entry point. Original numerical and stamp fixtures remain unchanged; the application and SDK share checked source parity.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Browser and Node consumers can import the existing phi/kosmos-vφ-5 calculator, immutable policy, checksum, serialization and rounding from the pure valuation entry point. Original numerical and stamp fixtures remain unchanged; the application and SDK share checked source parity.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Proof-bound valuation verifies the enclosing source first and reads its existing lawful fixed Kai-sigil origin and admitted history. A supplied now/future evaluation coordinate changes the projection without resealing or resetting issuance; successor seals, upload time and missing finer precision cannot manufacture another origin.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Proof-bound valuation verifies the enclosing source first and reads its existing lawful fixed Kai-sigil origin and admitted history. A supplied now/future evaluation coordinate changes the projection without resealing or resetting issuance; successor seals, upload time and missing finer precision cannot manufacture another origin.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Each projection returns actual inputs, intermediates, formulas, rounding, source references, history bindings, applied legacy defaults and a canonical digest. Intrinsic proof value, market reference, asking price and verified executed sale price stay distinct; optional USD display uses an explicit versioned, digest-bound conversion basis.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Each projection returns actual inputs, intermediates, formulas, rounding, source references, history bindings, applied legacy defaults and a canonical digest. Intrinsic proof value, market reference, asking price and verified executed sale price stay distinct; optional USD display uses an explicit versioned, digest-bound conversion basis.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Bounded sampling recomputes value at explicit Kai coordinates with the same calculator, preserving caller order and canonical results without network, randomness, session state or implicit clock authority. Model samples stay separately typed from actual sale and transfer observations.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Bounded sampling recomputes value at explicit Kai coordinates with the same calculator, preserving caller order and canonical results without network, randomness, session state or implicit clock authority. Model samples stay separately typed from actual sale and transfer observations.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Platforms can use a bounded versioned declarative policy with exact rational arithmetic and full traces, bound to sealed issuance, its policy digest and actual operands. Declared rarity does not redefine intrinsic value or authorize Settlement; the optional last-executed-sale reference rule selects only a uniquely causally latest verified sale.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Platforms can use a bounded versioned declarative policy with exact rational arithmetic and full traces, bound to sealed issuance, its policy digest and actual operands. Declared rarity does not redefine intrinsic value or authorize Settlement; the optional last-executed-sale reference rule selects only a uniquely causally latest verified sale.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Transaction projection preserves causal ownership changes and independently verified payment plus accepted delivery for the same asset, participants and committed intent. Gifts carry null payment; payment-only, pending, failed, foreign, detached and undelivered attempts cannot become completed sales.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Transaction projection preserves causal ownership changes and independently verified payment plus accepted delivery for the same asset, participants and committed intent. Gifts carry null payment; payment-only, pending, failed, foreign, detached and undelivered attempts cannot become completed sales.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

The public replay carries exact admitted proof/history, policy, coordinates, conversion basis, public sale evidence and expected digests. Existing pinned canonical readers verify those stronger sources before recomputing values and chart samples; copied runtime JSON, edited checksums and private identity/account/conversation data cannot establish public proof.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

The public replay carries exact admitted proof/history, policy, coordinates, conversion basis, public sale evidence and expected digests. Existing pinned canonical readers verify those stronger sources before recomputing values and chart samples; copied runtime JSON, edited checksums and private identity/account/conversation data cannot establish public proof.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Actual committed participant custody can project a subordinate public sale journal body into the existing buyer-authored sealed domain replay source. Real consent, identity signing, predecessor-bound complete public issuer-state evidence and the existing seal API remain required; no temporal setter, new proof field or private recovery export is introduced.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Actual committed participant custody can project a subordinate public sale journal body into the existing buyer-authored sealed domain replay source. Real consent, identity signing, predecessor-bound complete public issuer-state evidence and the existing seal API remain required; no temporal setter, new proof field or private recovery export is introduced.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Three read-only MCP adapters inspect proof value, sample explicit coordinates and verify public replay through the same SDK functions. Workspace references are digest-bound and verified by the host; calculation performs no custody, payment, admission, approval or file writes and cannot accept model-supplied authority JSON.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Three read-only MCP adapters inspect proof value, sample explicit coordinates and verify public replay through the same SDK functions. Workspace references are digest-bound and verified by the host; calculation performs no custody, payment, admission, approval or file writes and cannot accept model-supplied authority JSON.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

SDK and MCP declarations expose actual public types without repository authority aliases, and strict installed consumers and browser/Node examples compile against the published package surface. Versioned wire identities and historical verification remain unchanged.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

SDK and MCP declarations expose actual public types without repository authority aliases, and strict installed consumers and browser/Node examples compile against the published package surface. Versioned wire identities and historical verification remain unchanged.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Current SDK, MCP, AI, developer pages, machine catalogs and social artwork agree on 704 exports, 425 methods, 356 full tools and 43 skills, including 37 manifests and 34 prompts. The execution map distinguishes direct tools, bounded compositions, private SDK custody and real device/WebAuthn workflows; discovery grants no authority.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Current SDK, MCP, AI, developer pages, machine catalogs and social artwork agree on 704 exports, 425 methods, 356 full tools and 43 skills, including 37 manifests and 34 prompts. The execution map distinguishes direct tools, bounded compositions, private SDK custody and real device/WebAuthn workflows; discovery grants no authority.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

The user published AI skills, SDK and MCP at 129.0.0 and latest, with registry hashes, integrity, sizes, file counts and internal Receiz dependencies matching the qualified candidates. The prepared manual installation kit retains its earlier build provenance and independently passes exact-runtime, canonical proof and tamper contracts.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

The user published AI skills, SDK and MCP at 129.0.0 and latest, with registry hashes, integrity, sizes, file counts and internal Receiz dependencies matching the qualified candidates. The prepared manual installation kit retains its earlier build provenance and independently passes exact-runtime, canonical proof and tamper contracts.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Carried changes since v128 preserve same-origin OIDC entry, accepted username appends, held owner identity, exact Showcase signing subjects and receipt admission. Unsigned Original reconciliation does not restore hidden membership, and weaker discovery cannot replace known verified first paint.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Carried changes since v128 preserve same-origin OIDC entry, accepted username appends, held owner identity, exact Showcase signing subjects and receipt admission. Unsigned Original reconciliation does not restore hidden membership, and weaker discovery cannot replace known verified first paint.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Historical Identity Seals reuse verified enclosing source, signed portable account state and identity-control proof without resealing. Whole-workspace restoration preserves selection and tab, admits verified descendants, retains newer held history and rejects divergence with zero writes; Native Record custody keeps its distinct boundary.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Historical Identity Seals reuse verified enclosing source, signed portable account state and identity-control proof without resealing. Whole-workspace restoration preserves selection and tab, admits verified descendants, retains newer held history and rejects divergence with zero writes; Native Record custody keeps its distinct boundary.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Shared in-flight manifest reads retain each caller's username and dirty policy, and concurrent default-business/membership/founder creation converges on the existing unique winner. App and SDK material-anchor parsing agree without relaxing locator, digest or source rejection.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Shared in-flight manifest reads retain each caller's username and dirty policy, and concurrent default-business/membership/founder creation converges on the existing unique winner. App and SDK material-anchor parsing agree without relaxing locator, digest or source rejection.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

The carried Explore navigation adds previous/next, position/progress, reduced-motion behavior and correct root containment; the reverted image warmup is not shipped. Fraud uses the application shell with scoped localization, language selection, metadata and sector links, preserving its existing proof boundaries.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

The carried Explore navigation adds previous/next, position/progress, reduced-motion behavior and correct root containment; the reverted image warmup is not shipped. Fraud uses the application shell with scoped localization, language selection, metadata and sector links, preserving its existing proof boundaries.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Reviewed hosted execution reuses original admitted custody and resolves wake credentials from the existing Vercel request context. Hosted availability remains distinct from device-held operations and Marketplace restrictions; transport does not create source authority.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Reviewed hosted execution reuses original admitted custody and resolves wake credentials from the existing Vercel request context. Hosted availability remains distinct from device-held operations and Marketplace restrictions; transport does not create source authority.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Native saves preserve verified source file types and frozen proof MIME, and exact private downloads remain accessible after handoff. Attachment diagnostics and selected-image verification use the selected original bytes without exposing private references or replaying an unrelated upload; transport never reseals a substitute object.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Native saves preserve verified source file types and frozen proof MIME, and exact private downloads remain accessible after handoff. Attachment diagnostics and selected-image verification use the selected original bytes without exposing private references or replaying an unrelated upload; transport never reseals a substitute object.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Carried changes provide refreshed manual and hosted AI setup, one-link installation, logged-in navigation and packaged verification guides. Current version-pinned package links follow the coordinated release while historical downloads retain their original coordinates.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Carried changes provide refreshed manual and hosted AI setup, one-link installation, logged-in navigation and packaged verification guides. Current version-pinned package links follow the coordinated release while historical downloads retain their original coordinates.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

One resolved request context and loaded memory are reused, independent preparation runs concurrently, and artificial fallback streaming delays are removed. Inactive Twin, credit reservation, replay, reconciliation and Settlement remain binding; no numerical production latency or connected-model acceptance is inferred.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

One resolved request context and loaded memory are reused, independent preparation runs concurrently, and artificial fallback streaming delays are removed. Inactive Twin, credit reservation, replay, reconciliation and Settlement remain binding; no numerical production latency or connected-model acceptance is inferred.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

Fourteen translated Agents routes carry deterministic source content, proof/verifier evidence, reduced-motion graphics and the settled foundation statement. Mind carries its interactive proof and checkout entrance while distinguishing the local Mac recorder/model from connected browser access; browser fixtures establish no live charge or bearer delivery.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

Fourteen translated Agents routes carry deterministic source content, proof/verifier evidence, reduced-motion graphics and the settled foundation statement. Mind carries its interactive proof and checkout entrance while distinguishing the local Mac recorder/model from connected browser access; browser fixtures establish no live charge or bearer delivery.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.

The complete 46-commit ledger retains every carried source group since the official v128 baseline, including its historical governance and deployment closeout. CI reuses the repository pnpm integrity pin; current conformance, installed-package and source-binding checks remain separate from live financial, final attestation and deployment evidence.

Why

People, creators and businesses can keep the same proof object, identity and ownership history as it moves between files, devices, applications and public witness surfaces. Developers can use the exact application coordinate Receiz issued, request supported grants, invoke the implemented SDK or MCP path and explain a collectible's value from verified source and reproducible arithmetic. Funding, payment and delivered custody remain inspectable stages rather than consequences inferred from a listing or successful checkout. Institutions and other readers can reopen the source, reproduce its calculation and inspect the carried evidence without promoting a server, registry, page or model response above it. This release removes concrete integration and delivery obstructions while preserving the fixed full Kai-sigil origin, first admission followed by lawful appends, settled visible continuity and the complete historical record. The practical result is the full frame cash out: source, law, sequence, object and evidence remain together, with every reader underneath them.

Capability enabled

The complete 46-commit ledger retains every carried source group since the official v128 baseline, including its historical governance and deployment closeout. CI reuses the repository pnpm integrity pin; current conformance, installed-package and source-binding checks remain separate from live financial, final attestation and deployment evidence.

Compatibility

The v129.0.0 compatibility record remains the exact boundary for this outcome.

Migration

The v129.0.0 migration record remains the exact adoption boundary for this outcome.