Documented release
v123.0.0
Intent Becomes Lawful Action
Release date 2026-08-22
Outcome
Outcome
V123 turns verified intent into recoverable lawful action across value, identity, subject, and world systems. Developers can keep people inside their own application, verify object authority at the edge, request only explicit minimum scope, obtain every security-critical byte from the SDK, execute Settlement or Reserve without collapsing their distinct value law, and recover ambiguity without duplicate action.
Changes
What changed
client.value.executeSettlement(intent, authority) executes canonical Phi Settlement
client.value.executeSettlement(intent, authority) executes canonical Phi Settlement.
Technical and authority boundary
client.value.executeSettlement(intent, authority) executes canonical Phi Settlement.
- Why
- V123 closes the distance between proof and action. Any application can now turn verified objects into lawful participants, grant narrow authority without surrendering identity or custody, coordinate private worlds, and move Phi through Settlement or Reserve—with no mandatory redirect and no application-made trust layer. This gives developers and institutions one universal foundation for markets, autonomous systems, games, infrastructure, and entire economies: truth remains with the object, consent remains explicit, execution is deterministic and recoverable, and every outcome remains independently verifiable. Receiz does not merely prove reality; it makes verified reality economically operable without placing a platform above it.
- Capability enabled
- client.value.executeSettlement(intent, authority) executes canonical Phi Settlement.
- Compatibility
- The v123.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v123.0.0 migration record remains the exact adoption boundary for this outcome.
client.value.executeReserve(intent, authority) executes canonical Phi Reserve
client.value.executeReserve(intent, authority) executes canonical Phi Reserve.
Technical and authority boundary
client.value.executeReserve(intent, authority) executes canonical Phi Reserve.
- Why
- V123 closes the distance between proof and action. Any application can now turn verified objects into lawful participants, grant narrow authority without surrendering identity or custody, coordinate private worlds, and move Phi through Settlement or Reserve—with no mandatory redirect and no application-made trust layer. This gives developers and institutions one universal foundation for markets, autonomous systems, games, infrastructure, and entire economies: truth remains with the object, consent remains explicit, execution is deterministic and recoverable, and every outcome remains independently verifiable. Receiz does not merely prove reality; it makes verified reality economically operable without placing a platform above it.
- Capability enabled
- client.value.executeReserve(intent, authority) executes canonical Phi Reserve.
- Compatibility
- The v123.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v123.0.0 migration record remains the exact adoption boundary for this outcome.
client.value.executionByIdempotencyKey(key) recovers an ambiguous execution outcome
client.value.executionByIdempotencyKey(key) recovers an ambiguous execution outcome.
Technical and authority boundary
client.value.executionByIdempotencyKey(key) recovers an ambiguous execution outcome.
- Why
- V123 closes the distance between proof and action. Any application can now turn verified objects into lawful participants, grant narrow authority without surrendering identity or custody, coordinate private worlds, and move Phi through Settlement or Reserve—with no mandatory redirect and no application-made trust layer. This gives developers and institutions one universal foundation for markets, autonomous systems, games, infrastructure, and entire economies: truth remains with the object, consent remains explicit, execution is deterministic and recoverable, and every outcome remains independently verifiable. Receiz does not merely prove reality; it makes verified reality economically operable without placing a platform above it.
- Capability enabled
- client.value.executionByIdempotencyKey(key) recovers an ambiguous execution outcome.
- Compatibility
- The v123.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v123.0.0 migration record remains the exact adoption boundary for this outcome.
client.world.planCommandV122(input) and client.world.planTransactionV122(input) produce canonical public world command bytes, authority…
client.world.planCommandV122(input) and client.world.planTransactionV122(input) produce canonical public world command bytes, authority and plan digests, transaction identity, and transaction digest. The v122 suffix remains the stable protocol identifier.
Technical and authority boundary
client.world.planCommandV122(input) and client.world.planTransactionV122(input) produce canonical public world command bytes, authority and plan digests, transaction identity, and transaction digest. The v122 suffix remains the stable protocol identifier.
- Why
- V123 closes the distance between proof and action. Any application can now turn verified objects into lawful participants, grant narrow authority without surrendering identity or custody, coordinate private worlds, and move Phi through Settlement or Reserve—with no mandatory redirect and no application-made trust layer. This gives developers and institutions one universal foundation for markets, autonomous systems, games, infrastructure, and entire economies: truth remains with the object, consent remains explicit, execution is deterministic and recoverable, and every outcome remains independently verifiable. Receiz does not merely prove reality; it makes verified reality economically operable without placing a platform above it.
- Capability enabled
- client.world.planCommandV122(input) and client.world.planTransactionV122(input) produce canonical public world command bytes, authority and plan digests, transaction identity, and transaction digest. The v122 suffix remains the stable protocol identifier.
- Compatibility
- The v123.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v123.0.0 migration record remains the exact adoption boundary for this outcome.
Settlement and Reserve have authoritative OAuth/OIDC scopes plus granted- and…
Settlement and Reserve have authoritative OAuth/OIDC scopes plus granted- and missing-scope introspection.
Technical and authority boundary
Settlement and Reserve have authoritative OAuth/OIDC scopes plus granted- and missing-scope introspection.
- Why
- V123 closes the distance between proof and action. Any application can now turn verified objects into lawful participants, grant narrow authority without surrendering identity or custody, coordinate private worlds, and move Phi through Settlement or Reserve—with no mandatory redirect and no application-made trust layer. This gives developers and institutions one universal foundation for markets, autonomous systems, games, infrastructure, and entire economies: truth remains with the object, consent remains explicit, execution is deterministic and recoverable, and every outcome remains independently verifiable. Receiz does not merely prove reality; it makes verified reality economically operable without placing a platform above it.
- Capability enabled
- Settlement and Reserve have authoritative OAuth/OIDC scopes plus granted- and missing-scope introspection.
- Compatibility
- The v123.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v123.0.0 migration record remains the exact adoption boundary for this outcome.
client.subjects.resolveNamespaces({ subjectId, atHead, names }) resolves exact current subject namespaces…
client.subjects.resolveNamespaces({ subjectId, atHead, names }) resolves exact current subject namespaces at one authenticated head.
Technical and authority boundary
client.subjects.resolveNamespaces({ subjectId, atHead, names }) resolves exact current subject namespaces at one authenticated head.
- Why
- V123 closes the distance between proof and action. Any application can now turn verified objects into lawful participants, grant narrow authority without surrendering identity or custody, coordinate private worlds, and move Phi through Settlement or Reserve—with no mandatory redirect and no application-made trust layer. This gives developers and institutions one universal foundation for markets, autonomous systems, games, infrastructure, and entire economies: truth remains with the object, consent remains explicit, execution is deterministic and recoverable, and every outcome remains independently verifiable. Receiz does not merely prove reality; it makes verified reality economically operable without placing a platform above it.
- Capability enabled
- client.subjects.resolveNamespaces({ subjectId, atHead, names }) resolves exact current subject namespaces at one authenticated head.
- Compatibility
- The v123.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v123.0.0 migration record remains the exact adoption boundary for this outcome.
client.identity.exchangeProofAuthority({ artifact, challenge, applicationId, scopes }) exchanges independently verified artifact…
client.identity.exchangeProofAuthority({ artifact, challenge, applicationId, scopes }) exchanges independently verified artifact proof and explicit in-application consent for short-lived, non-refreshable, minimum-scope authority without redirecting the person to receiz.com.
Technical and authority boundary
client.identity.exchangeProofAuthority({ artifact, challenge, applicationId, scopes }) exchanges independently verified artifact proof and explicit in-application consent for short-lived, non-refreshable, minimum-scope authority without redirecting the person to receiz.com.
- Why
- V123 closes the distance between proof and action. Any application can now turn verified objects into lawful participants, grant narrow authority without surrendering identity or custody, coordinate private worlds, and move Phi through Settlement or Reserve—with no mandatory redirect and no application-made trust layer. This gives developers and institutions one universal foundation for markets, autonomous systems, games, infrastructure, and entire economies: truth remains with the object, consent remains explicit, execution is deterministic and recoverable, and every outcome remains independently verifiable. Receiz does not merely prove reality; it makes verified reality economically operable without placing a platform above it.
- Capability enabled
- client.identity.exchangeProofAuthority({ artifact, challenge, applicationId, scopes }) exchanges independently verified artifact proof and explicit in-application consent for short-lived, non-refreshable, minimum-scope authority without redirecting the person to receiz.com.
- Compatibility
- The v123.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v123.0.0 migration record remains the exact adoption boundary for this outcome.
SDK, MCP, AI Skills, registry, operation matrix, OpenAPI, receiz.com developer…
SDK, MCP, AI Skills, registry, operation matrix, OpenAPI, receiz.com developer surfaces, and Receiz Docs advance together to v123. These are universal public rails. They are not application-specific conveniences and they do not require developers to recreate authority, canonical bytes, execution recovery, rail scopes, or exact-head resolution in application code.
Technical and authority boundary
SDK, MCP, AI Skills, registry, operation matrix, OpenAPI, receiz.com developer surfaces, and Receiz Docs advance together to v123. These are universal public rails. They are not application-specific conveniences and they do not require developers to recreate authority, canonical bytes, execution recovery, rail scopes, or exact-head resolution in application code.
- Why
- V123 closes the distance between proof and action. Any application can now turn verified objects into lawful participants, grant narrow authority without surrendering identity or custody, coordinate private worlds, and move Phi through Settlement or Reserve—with no mandatory redirect and no application-made trust layer. This gives developers and institutions one universal foundation for markets, autonomous systems, games, infrastructure, and entire economies: truth remains with the object, consent remains explicit, execution is deterministic and recoverable, and every outcome remains independently verifiable. Receiz does not merely prove reality; it makes verified reality economically operable without placing a platform above it.
- Capability enabled
- SDK, MCP, AI Skills, registry, operation matrix, OpenAPI, receiz.com developer surfaces, and Receiz Docs advance together to v123. These are universal public rails. They are not application-specific conveniences and they do not require developers to recreate authority, canonical bytes, execution recovery, rail scopes, or exact-head resolution in application code.
- Compatibility
- The v123.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v123.0.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
V123 closes the distance between proof and action. Any application can now turn verified objects into lawful participants, grant narrow authority without surrendering identity or custody, coordinate private worlds, and move Phi through Settlement or Reserve—with no mandatory redirect and no application-made trust layer. This gives developers and institutions one universal foundation for markets, autonomous systems, games, infrastructure, and entire economies: truth remains with the object, consent remains explicit, execution is deterministic and recoverable, and every outcome remains independently verifiable. Receiz does not merely prove reality; it makes verified reality economically operable without placing a platform above it.
Available outcomes
Capabilities now available
client.value.executeSettlement(intent, authority) executes canonical Phi Settlement
client.value.executeSettlement(intent, authority) executes canonical Phi Settlement.
client.value.executeReserve(intent, authority) executes canonical Phi Reserve
client.value.executeReserve(intent, authority) executes canonical Phi Reserve.
client.value.executionByIdempotencyKey(key) recovers an ambiguous execution outcome
client.value.executionByIdempotencyKey(key) recovers an ambiguous execution outcome.
client.world.planCommandV122(input) and client.world.planTransactionV122(input) produce canonical public world command bytes, authority…
client.world.planCommandV122(input) and client.world.planTransactionV122(input) produce canonical public world command bytes, authority and plan digests, transaction identity, and transaction digest. The v122 suffix remains the stable protocol identifier.
Settlement and Reserve have authoritative OAuth/OIDC scopes plus granted- and…
Settlement and Reserve have authoritative OAuth/OIDC scopes plus granted- and missing-scope introspection.
client.subjects.resolveNamespaces({ subjectId, atHead, names }) resolves exact current subject namespaces…
client.subjects.resolveNamespaces({ subjectId, atHead, names }) resolves exact current subject namespaces at one authenticated head.
client.identity.exchangeProofAuthority({ artifact, challenge, applicationId, scopes }) exchanges independently verified artifact…
client.identity.exchangeProofAuthority({ artifact, challenge, applicationId, scopes }) exchanges independently verified artifact proof and explicit in-application consent for short-lived, non-refreshable, minimum-scope authority without redirecting the person to receiz.com.
SDK, MCP, AI Skills, registry, operation matrix, OpenAPI, receiz.com developer…
SDK, MCP, AI Skills, registry, operation matrix, OpenAPI, receiz.com developer surfaces, and Receiz Docs advance together to v123. These are universal public rails. They are not application-specific conveniences and they do not require developers to recreate authority, canonical bytes, execution recovery, rail scopes, or exact-head resolution in application code.
Primitive boundary
Primitives affected
- proof
- identity
- settlement
- media
- verification
- local-truth
- reserve
- sealed-artifact
Compatibility
Compatibility
@receiz/sdk
123.0.0
This exact v123.0.0 compatibility boundary remains binding.
@receiz/mcp-server
123.0.0
This exact v123.0.0 compatibility boundary remains binding.
@receiz/ai-skills
123.0.0
This exact v123.0.0 compatibility boundary remains binding.
Constitutional verifier
123.0.0
This exact v123.0.0 compatibility boundary remains binding.
Registry
123.0.0
This exact v123.0.0 compatibility boundary remains binding.
Operation matrix
v123
This exact v123.0.0 compatibility boundary remains binding.
OpenAPI
2026-08-22.v123
This exact v123.0.0 compatibility boundary remains binding.
Production migration
v123 SQL candidate
This exact v123.0.0 compatibility boundary remains binding.
Migration
Migration
Required: true
The v123 SQL migration is required for production remote authority and Phi execution routes. Its production application is separately authorized and evidenced below.
- Continue verifying the enclosing proof object at the edge.
- Replace application-made public world digests with planCommandV122 and planTransactionV122.
- Request Settlement or Reserve scopes through scopesForRails; inspect granted and missing scopes.
- Exchange an identity artifact and explicit consent for narrow proof authority when an embedded flow must avoid a redirect.
- Resolve subject namespaces at the exact head used for planning.
- Execute the prepared Phi intent on its named rail.
- Persist the exact intent and idempotency key.
- On ambiguity, call executionByIdempotencyKey before retry.
Qualification
Conformance
SDK, MCP, AI Skills, and Receiz Docs typecheck/test/build pass.
Passed · SDK, MCP, AI Skills, and Receiz Docs typecheck/test/build pass.
Governance checks pass.
Passed · Governance checks pass.
Focused v123 tests pass.
Passed · Focused v123 tests pass.
Control boundary
Governance
- Verification
- Passed
- Declared change class
- No separate classification record
- Release approval
- No separate approval record
- Risk owner
- No separate assignment recorded
Package publication, production deployment, and production smoke are independently confirmed; signed release attestation remains absent and is not inferred from the live release.
Registry boundary
Registry
- Version
- 123.0.0
- Digest
945a581d1fc49c2dc18fbe8c129771ef464b8a58b96188bce561e88ae8b6ceeb- Predecessor
ed65956a16dd5f0d76d04db2f4a651fc43eb0a71cef64afd53576aa782dc9896
Archive projection
Audience, domain, and change-kind facets
- Audiences
- developers · businesses · creators · institutions · people
- Domains
- proof-object-authority · edge-verification · scoped-consent · identity · subjects · public-world-planning · settlement · reserve · phi-execution · execution-recovery · oauth · oidc · sdk · mcp · ai-skills
- Change kinds
- capability · compatibility · governance · security
Independent dimensions
Release boundary status
- Repository release
- Documented
- Git tag
- Present
- Package publication
- Confirmed
- Deployment
- Confirmed
- Production smoke
- Confirmed
- Signed attestation
- Absent
Exact source bytes
Provenance
This Academy record is a projection beneath its sources. Record SHA-256 222a30ed01471c68655d2f471b76767a35d0ed9da916932fd98f475e8b7f452d. Source-family inventory: complete.
SHA-256 2af35a2c78695e0198442e09c1a8613da6834c72c5a1e3280ac668733c5c2f25SHA-256 0555b3b3ea89f67531230a5b5b54b172d924ba335e460ebe18c8c19f14be0f1cSHA-256 8c453816b62c015da6d4448dd0e060f6f6b2b999f93563d9b24e164b2dee8e84SHA-256 7e7c3054e1fd05d273b141e03f443b3724f1851c02aa324ec2d0b6e742a6d767SHA-256 6f84468172a6e2a39976f422771e012e0a33f801d2574d12d33cabe40a520783SHA-256 051e58ace1fa9fad8421521b87b149117314c997778dc849fdddc8ea9d5f5aecSHA-256 ee35995097e8f262ddb033d00e62c5f86e1abbdc9764678de2ba000cd26391f6SHA-256 e363c3f13bb06cdf6de5e7223b717e6a838f352a67783284e6e0a91da0a778daSHA-256 a176b58caff78961f1f9df61272ab442e7b4e25e3efdb547ac9795826ee03116SHA-256 bf5490dcf5f4a8eede5962f04e940504d49bcb73b901b87ac41f7d7fbf48a464SHA-256 533c32da6eda31dbaf8d6358c98b1dd5a8adf1cfea323db516de090569d86a76SHA-256 ed4728cfba4c971b0cd469abe2211458923644e6ca33693aae9f0ef7d5441182