Documented release
v126.0.0
Reality-Grade Infrastructure
Release date 2026-09-07
Outcome
Outcome
One proof object, unlimited experiences. The same object carries identity, source, ownership, capabilities, and verified history between experiences. Builders can project a game, a media surface, a public profile, or an ownership experience from that source and append only the transitions its law permits. A new view does not start a new identity or erase the object's life.
Changes
What changed
One proof object, unlimited experiences
The same object carries identity, source, ownership, capabilities, and verified history between experiences. Builders can project a game, a media surface, a public profile, or an ownership experience from that source and append only the transitions its law permits. A new view does not start a new identity or erase the object's life.
Technical and authority boundary
The same object carries identity, source, ownership, capabilities, and verified history between experiences. Builders can project a game, a media surface, a public profile, or an ownership experience from that source and append only the transitions its law permits. A new view does not start a new identity or erase the object's life.
- Why
- Reality becomes the application substrate. A person can carry identity and work; an object can carry its life; an agent can act under exact consent; and a reader can independently inspect what the evidence establishes. V126 makes these parts operate through one source-governed system, so changing an interface, owner, device, or integration does not authorize changing the truth.
- Capability enabled
- The same object carries identity, source, ownership, capabilities, and verified history between experiences. Builders can project a game, a media surface, a public profile, or an ownership experience from that source and append only the transitions its law permits. A new view does not start a new identity or erase the object's life.
- Compatibility
- The v126.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v126.0.0 migration record remains the exact adoption boundary for this outcome.
People carry their identity and creations
Receiz ID, held identity proof, and complete source custody preserve continuity beyond a browser session. V126 closes large-source recovery and restored-profile gaps while preserving the original creation coordinate. Recovery returns people to their existing proof history.
Technical and authority boundary
Receiz ID, held identity proof, and complete source custody preserve continuity beyond a browser session. V126 closes large-source recovery and restored-profile gaps while preserving the original creation coordinate. Recovery returns people to their existing proof history.
- Why
- Reality becomes the application substrate. A person can carry identity and work; an object can carry its life; an agent can act under exact consent; and a reader can independently inspect what the evidence establishes. V126 makes these parts operate through one source-governed system, so changing an interface, owner, device, or integration does not authorize changing the truth.
- Capability enabled
- Receiz ID, held identity proof, and complete source custody preserve continuity beyond a browser session. V126 closes large-source recovery and restored-profile gaps while preserving the original creation coordinate. Recovery returns people to their existing proof history.
- Compatibility
- The v126.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v126.0.0 migration record remains the exact adoption boundary for this outcome.
An object's life survives its next owner
First sealing records creator and owner; verified transfers advance current ownership while retaining provenance. A later owner receives the same object's continuing history. A copy or a new presentation cannot create a second ownership or Settlement membership.
Technical and authority boundary
First sealing records creator and owner; verified transfers advance current ownership while retaining provenance. A later owner receives the same object's continuing history. A copy or a new presentation cannot create a second ownership or Settlement membership.
- Why
- Reality becomes the application substrate. A person can carry identity and work; an object can carry its life; an agent can act under exact consent; and a reader can independently inspect what the evidence establishes. V126 makes these parts operate through one source-governed system, so changing an interface, owner, device, or integration does not authorize changing the truth.
- Capability enabled
- First sealing records creator and owner; verified transfers advance current ownership while retaining provenance. A later owner receives the same object's continuing history. A copy or a new presentation cannot create a second ownership or Settlement membership.
- Compatibility
- The v126.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v126.0.0 migration record remains the exact adoption boundary for this outcome.
Complete source remains usable at the edge
Documents, media, portable state, and admitted history remain bound to their enclosing proof object. V126 connects large-source custody, direct document downloads, bounded media delivery, and complete Showcase publication so a compact projection cannot substitute for the material it represents.
Technical and authority boundary
Documents, media, portable state, and admitted history remain bound to their enclosing proof object. V126 connects large-source custody, direct document downloads, bounded media delivery, and complete Showcase publication so a compact projection cannot substitute for the material it represents.
- Why
- Reality becomes the application substrate. A person can carry identity and work; an object can carry its life; an agent can act under exact consent; and a reader can independently inspect what the evidence establishes. V126 makes these parts operate through one source-governed system, so changing an interface, owner, device, or integration does not authorize changing the truth.
- Capability enabled
- Documents, media, portable state, and admitted history remain bound to their enclosing proof object. V126 connects large-source custody, direct document downloads, bounded media delivery, and complete Showcase publication so a compact projection cannot substitute for the material it represents.
- Compatibility
- The v126.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v126.0.0 migration record remains the exact adoption boundary for this outcome.
AI reads the evidence behind the experience
Public proof discovery exposes admitted content, source coordinates, carried authorship and ownership evidence, history links, and available value inputs through the same content projection used by the Twin. Readers can follow those claims to source; generated text and search indexes gain no authority over it.
Technical and authority boundary
Public proof discovery exposes admitted content, source coordinates, carried authorship and ownership evidence, history links, and available value inputs through the same content projection used by the Twin. Readers can follow those claims to source; generated text and search indexes gain no authority over it.
- Why
- Reality becomes the application substrate. A person can carry identity and work; an object can carry its life; an agent can act under exact consent; and a reader can independently inspect what the evidence establishes. V126 makes these parts operate through one source-governed system, so changing an interface, owner, device, or integration does not authorize changing the truth.
- Capability enabled
- Public proof discovery exposes admitted content, source coordinates, carried authorship and ownership evidence, history links, and available value inputs through the same content projection used by the Twin. Readers can follow those claims to source; generated text and search indexes gain no authority over it.
- Compatibility
- The v126.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v126.0.0 migration record remains the exact adoption boundary for this outcome.
Intent stays bound to lawful action
Applications and agents compose existing verification, exact plans, scoped consent, admission, and recovery through aligned SDK, compiler, MCP, and AI interfaces. V126 carries those primitives through the coordinated distribution without allowing a tool response or successful delivery to manufacture permission or completion.
Technical and authority boundary
Applications and agents compose existing verification, exact plans, scoped consent, admission, and recovery through aligned SDK, compiler, MCP, and AI interfaces. V126 carries those primitives through the coordinated distribution without allowing a tool response or successful delivery to manufacture permission or completion.
- Why
- Reality becomes the application substrate. A person can carry identity and work; an object can carry its life; an agent can act under exact consent; and a reader can independently inspect what the evidence establishes. V126 makes these parts operate through one source-governed system, so changing an interface, owner, device, or integration does not authorize changing the truth.
- Capability enabled
- Applications and agents compose existing verification, exact plans, scoped consent, admission, and recovery through aligned SDK, compiler, MCP, and AI interfaces. V126 carries those primitives through the coordinated distribution without allowing a tool response or successful delivery to manufacture permission or completion.
- Compatibility
- The v126.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v126.0.0 migration record remains the exact adoption boundary for this outcome.
Verified reality retains its economic continuity
Settlement, Reserve, and deterministic object value retain their distinct source laws. V126 preserves large-source admission, retry recovery, and ownership appends beneath canonical verification. Economic membership follows the verified owner; distribution and rediscovery cannot duplicate it or rewrite its history.
Technical and authority boundary
Settlement, Reserve, and deterministic object value retain their distinct source laws. V126 preserves large-source admission, retry recovery, and ownership appends beneath canonical verification. Economic membership follows the verified owner; distribution and rediscovery cannot duplicate it or rewrite its history.
- Why
- Reality becomes the application substrate. A person can carry identity and work; an object can carry its life; an agent can act under exact consent; and a reader can independently inspect what the evidence establishes. V126 makes these parts operate through one source-governed system, so changing an interface, owner, device, or integration does not authorize changing the truth.
- Capability enabled
- Settlement, Reserve, and deterministic object value retain their distinct source laws. V126 preserves large-source admission, retry recovery, and ownership appends beneath canonical verification. Economic membership follows the verified owner; distribution and rediscovery cannot duplicate it or rewrite its history.
- Compatibility
- The v126.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v126.0.0 migration record remains the exact adoption boundary for this outcome.
Creators publish a source that people and machines can read
Public long-form posts, images, music, audio, and video remain discoverable through readable pages and structured proof projections. Canonical profiles, custom domains, and public readers use the same published source while known verified truth remains available on first paint.
Technical and authority boundary
Public long-form posts, images, music, audio, and video remain discoverable through readable pages and structured proof projections. Canonical profiles, custom domains, and public readers use the same published source while known verified truth remains available on first paint.
- Why
- Reality becomes the application substrate. A person can carry identity and work; an object can carry its life; an agent can act under exact consent; and a reader can independently inspect what the evidence establishes. V126 makes these parts operate through one source-governed system, so changing an interface, owner, device, or integration does not authorize changing the truth.
- Capability enabled
- Public long-form posts, images, music, audio, and video remain discoverable through readable pages and structured proof projections. Canonical profiles, custom domains, and public readers use the same published source while known verified truth remains available on first paint.
- Compatibility
- The v126.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v126.0.0 migration record remains the exact adoption boundary for this outcome.
Builders receive one coherent operating contract
The v126 application, Academy, SDK, compiler, MCP, and AI distributions expose the same source-authority boundaries. The catalog covers 663 callable SDK exports, 421 client methods, and 221 MCP tools, making the implemented system inspectable and usable across its integration surfaces.
Technical and authority boundary
The v126 application, Academy, SDK, compiler, MCP, and AI distributions expose the same source-authority boundaries. The catalog covers 663 callable SDK exports, 421 client methods, and 221 MCP tools, making the implemented system inspectable and usable across its integration surfaces.
- Why
- Reality becomes the application substrate. A person can carry identity and work; an object can carry its life; an agent can act under exact consent; and a reader can independently inspect what the evidence establishes. V126 makes these parts operate through one source-governed system, so changing an interface, owner, device, or integration does not authorize changing the truth.
- Capability enabled
- The v126 application, Academy, SDK, compiler, MCP, and AI distributions expose the same source-authority boundaries. The catalog covers 663 callable SDK exports, 421 client methods, and 221 MCP tools, making the implemented system inspectable and usable across its integration surfaces.
- Compatibility
- The v126.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v126.0.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
Reality becomes the application substrate. A person can carry identity and work; an object can carry its life; an agent can act under exact consent; and a reader can independently inspect what the evidence establishes. V126 makes these parts operate through one source-governed system, so changing an interface, owner, device, or integration does not authorize changing the truth.
Available outcomes
Capabilities now available
One proof object, unlimited experiences
The same object carries identity, source, ownership, capabilities, and verified history between experiences. Builders can project a game, a media surface, a public profile, or an ownership experience from that source and append only the transitions its law permits. A new view does not start a new identity or erase the object's life.
People carry their identity and creations
Receiz ID, held identity proof, and complete source custody preserve continuity beyond a browser session. V126 closes large-source recovery and restored-profile gaps while preserving the original creation coordinate. Recovery returns people to their existing proof history.
An object's life survives its next owner
First sealing records creator and owner; verified transfers advance current ownership while retaining provenance. A later owner receives the same object's continuing history. A copy or a new presentation cannot create a second ownership or Settlement membership.
Complete source remains usable at the edge
Documents, media, portable state, and admitted history remain bound to their enclosing proof object. V126 connects large-source custody, direct document downloads, bounded media delivery, and complete Showcase publication so a compact projection cannot substitute for the material it represents.
AI reads the evidence behind the experience
Public proof discovery exposes admitted content, source coordinates, carried authorship and ownership evidence, history links, and available value inputs through the same content projection used by the Twin. Readers can follow those claims to source; generated text and search indexes gain no authority over it.
Intent stays bound to lawful action
Applications and agents compose existing verification, exact plans, scoped consent, admission, and recovery through aligned SDK, compiler, MCP, and AI interfaces. V126 carries those primitives through the coordinated distribution without allowing a tool response or successful delivery to manufacture permission or completion.
Verified reality retains its economic continuity
Settlement, Reserve, and deterministic object value retain their distinct source laws. V126 preserves large-source admission, retry recovery, and ownership appends beneath canonical verification. Economic membership follows the verified owner; distribution and rediscovery cannot duplicate it or rewrite its history.
Creators publish a source that people and machines can read
Public long-form posts, images, music, audio, and video remain discoverable through readable pages and structured proof projections. Canonical profiles, custom domains, and public readers use the same published source while known verified truth remains available on first paint.
Builders receive one coherent operating contract
The v126 application, Academy, SDK, compiler, MCP, and AI distributions expose the same source-authority boundaries. The catalog covers 663 callable SDK exports, 421 client methods, and 221 MCP tools, making the implemented system inspectable and usable across its integration surfaces.
Primitive boundary
Primitives affected
- proof
- identity
- ownership
- provenance
- transfer
- verification
- public-witness
- continuity
- sealed-artifact
- governance
Compatibility
Compatibility
Coordinated packages
SDK, MCP and AI skills use 126.0.0; current integrations require >=126.0.0 <127.0.0.
This exact v126.0.0 compatibility boundary remains binding.
Compiler
New admissions use the exact v126 registry; historical targets retain their original registry identities.
This exact v126.0.0 compatibility boundary remains binding.
Historical proof objects
Original bytes, creation coordinates, ownership history and registry digests remain unchanged.
This exact v126.0.0 compatibility boundary remains binding.
Wire protocols
Existing versioned SDK exports, MCP tool identifiers, KKSv1.0 and Signature V4 retain their established names.
This exact v126.0.0 compatibility boundary remains binding.
Current JSON schemas
The v126 schema directory binds the current registry while preserving established wire schema identifiers; v125 schemas remain available for historical records.
This exact v126.0.0 compatibility boundary remains binding.
Function discovery
@receiz/sdk/function-inventory exposes the full callable export catalog without adding that data to the universal runtime entry point.
This exact v126.0.0 compatibility boundary remains binding.
SQL admission
The additive registry successor migration is required before the existing hosted admission functions accept v126.
This exact v126.0.0 compatibility boundary remains binding.
First paint
Complete known published Showcase truth remains visible while a newer publication is pending.
This exact v126.0.0 compatibility boundary remains binding.
Migration
Migration
Required: true
On September 8, 2026, the release operator supplied SQL results confirming all three recent v126 migration outcomes are present:
- Apply supabase/migrations/20260907114032_v126_lawful_delivery_recovery.sql to update large-source constraints and derivative admission retry handling.
- Apply supabase/migrations/20260907212000_temporal_conformance_history.sql to create Temporal conformance snapshots and daily rollups, matching the existing conformance suites.
- Apply supabase/migrations/20260908021500_v126_lawful_action_registry_successor.sql after recovery. Its guard checks require the expected predecessor or already-present successor expression. It admits the exact v126 registry alongside v125. Recovery replaces the admission function bodies, so a combined operation must reapply this successor before committing.
- Install the published coordinated 126.0.0 SDK, MCP and AI skills packages; use actual registry integrity records in the Academy lockfile.
- Deploy the application and Academy from the qualified release commit, then verify public proof, Showcase first paint and the PWA against the deployed version.
Qualification
Conformance
Release-freeze run completed with zero failures; the isolated v108 Supabase integration was unavailable because no isolated service was supplied.
Passed · Release-freeze run completed with zero failures; the isolated v108 Supabase integration was unavailable because no isolated service was supplied.
Main application build, conformance suites and performance budgets passed in that release-freeze run.
Passed · Main application build, conformance suites and performance budgets passed in that release-freeze run.
Governance controls, evidence and artifact-signature checks passed in that run.
Passed · Governance controls, evidence and artifact-signature checks passed in that run.
Academy build and size budgets passed: 187 routes, 1,033 search destinations and 6,489 internal links.
Passed · Academy build and size budgets passed: 187 routes, 1,033 search destinations and 6,489 internal links.
Isolated PostgreSQL v126 admission integration passed all three tests, including large sources, retries and ownership appends.
Passed · Isolated PostgreSQL v126 admission integration passed all three tests, including large sources, retries and ownership appends.
SDK package projection build verified exact canonical v115–v126 registry contents and digests, including detached frozen readers.
Passed · SDK package projection build verified exact canonical v115–v126 registry contents and digests, including detached frozen readers.
Control boundary
Governance
- Verification
- Passed
- Declared change class
- No separate classification record
- Release approval
- No separate approval record
- Risk owner
- No separate assignment recorded
Governance verification passed against the exact checked release evidence bound below.
No separate release approval reference or risk-owner assignment is inferred from conformance evidence.
Registry boundary
Registry
- Version
- 126.0.0
- Digest
80137c2e6f294050ef36ff75e4daac15c7790b7f04d9a91fab9d1970fa3c0b09- Predecessor
85a24c3a7fe144c8ec03c6b5fae238d1dfda64c1ed3091b24d4264dc3862ff17
Archive projection
Audience, domain, and change-kind facets
- Audiences
- developers · businesses · creators · institutions · people
- Domains
- proof · identity · ownership · provenance · verification · showcase · developer-integration
- Change kinds
- capability · correction · compatibility · migration · performance
Independent dimensions
Release boundary status
- Repository release
- Documented
- Git tag
- Present
- Package publication
- Confirmed
- Deployment
- Confirmed
- Production smoke
- Unknown
- Signed attestation
- Absent
Exact source bytes
Provenance
This Academy record is a projection beneath its sources. Record SHA-256 c3f8d321fb074f1e19cad9b11c93caf2e71af935f869c15c66e53a2255b4ba18. Source-family inventory: complete.
SHA-256 eb5cc3887a4ed3927eec0eb8723ebd37031dff794e4c0be383fc6bedf53c52e0SHA-256 b1ed45eaa24c1d629caf029cf3104f22dd7022ee7624e11bee71198762006e6dSHA-256 f133bc26731c07d07bed77ced35277560263d7df7361c6fa54bb667af96aa588SHA-256 840e0426dbe62533fefff191aeeb50e959ef1573779e1f603f0d777cdc6b0376SHA-256 a72871708540d6f649244b03a10ba21d6cf5cb30d223ccd5a3e581f535f85019SHA-256 cdda41cf16e34383ef5fe2fccc28d4aa91b22b410c669a07b4264e408b90a5b7SHA-256 a8a00389287273a8c967dd3553448abddcd2df5c94b54be2fae0c0297993b517SHA-256 6474645ba04dec3c1904aacc539f4f4ed9c0eb8c202b2385707b84688e8bf47bSHA-256 66d1ebb1918d20be4cce227335a7fe8effd4bb62131ecef9590280a38020959aSHA-256 7f242d53f223e0379c57b4e94281c58ab34991cf90d34b43db9e00a1be2c8cd5SHA-256 d455188edc363a21444dd61023576b588a34e9030cee70bd0a05997c33629389SHA-256 3cfbc1d1ca8755cdbb510380550b7c8b748ca7afca5c9d6fb15a4511d1f2cedbSHA-256 0a720163a2aa022ba347be87a3fa6e718ee1a2c9e61ae0cb67cf78e7d71664c6