Documented release
v124.0.0
Reality Becomes Infrastructure
The Production Runtime for Verified Civilization
Release date 2026-08-22
Outcome
Outcome
V124 makes production deployment structurally harder to misconfigure. Applications can derive canonical live Kai coordinates from pulses since genesis, create whole-pulse proof-authority challenges, bind short-lived execution sessions to application audience and exact proof authority, stage durable plans, execute once, recover by idempotency key, admit only verified replay/checkpoint additions, filter private additions before hydration, commit multi-domain world and inventory effects atomically, resolve recipients without exposing directory enumeration, and report whether required dependencies are operational rather than merely present.
Changes
What changed
Canonical live Kai exposes exact whole-pulse and micro-pulse coordinates derived…
Canonical live Kai exposes exact whole-pulse and micro-pulse coordinates derived from pulses since genesis through the existing phi-exact ties-to-even bridge.
Technical and authority boundary
Canonical live Kai exposes exact whole-pulse and micro-pulse coordinates derived from pulses since genesis through the existing phi-exact ties-to-even bridge.
- Why
- V124 removes ambiguity between representation and reality. A deployer no longer needs custom ports that accidentally duplicate execution, split a transaction, admit unverified replay, retain stale authority, expose private coordinates, enumerate recipients, or report a configured-but-inoperative dependency as production-ready. Verified reality can coordinate durable execution without granting unilateral jurisdiction to an application, institution, server, database, SDK, or network operator.
- Capability enabled
- Canonical live Kai exposes exact whole-pulse and micro-pulse coordinates derived from pulses since genesis through the existing phi-exact ties-to-even bridge.
- Compatibility
- The v124.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.0 migration record remains the exact adoption boundary for this outcome.
Proof-authority challenges bind application, artifact digest, exact scopes, consent digest…
Proof-authority challenges bind application, artifact digest, exact scopes, consent digest, bounded whole-pulse lifetime, and nonce without reinterpreting V123 fields.
Technical and authority boundary
Proof-authority challenges bind application, artifact digest, exact scopes, consent digest, bounded whole-pulse lifetime, and nonce without reinterpreting V123 fields.
- Why
- V124 removes ambiguity between representation and reality. A deployer no longer needs custom ports that accidentally duplicate execution, split a transaction, admit unverified replay, retain stale authority, expose private coordinates, enumerate recipients, or report a configured-but-inoperative dependency as production-ready. Verified reality can coordinate durable execution without granting unilateral jurisdiction to an application, institution, server, database, SDK, or network operator.
- Capability enabled
- Proof-authority challenges bind application, artifact digest, exact scopes, consent digest, bounded whole-pulse lifetime, and nonce without reinterpreting V123 fields.
- Compatibility
- The v124.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.0 migration record remains the exact adoption boundary for this outcome.
One runtime factory binds existing proof authority, subject ownership/head, namespaces…
One runtime factory binds existing proof authority, subject ownership/head, namespaces, revocation, durable journal/checkpoint, plans, transaction context, private access, and recipient resolution.
Technical and authority boundary
One runtime factory binds existing proof authority, subject ownership/head, namespaces, revocation, durable journal/checkpoint, plans, transaction context, private access, and recipient resolution.
- Why
- V124 removes ambiguity between representation and reality. A deployer no longer needs custom ports that accidentally duplicate execution, split a transaction, admit unverified replay, retain stale authority, expose private coordinates, enumerate recipients, or report a configured-but-inoperative dependency as production-ready. Verified reality can coordinate durable execution without granting unilateral jurisdiction to an application, institution, server, database, SDK, or network operator.
- Capability enabled
- One runtime factory binds existing proof authority, subject ownership/head, namespaces, revocation, durable journal/checkpoint, plans, transaction context, private access, and recipient resolution.
- Compatibility
- The v124.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.0 migration record remains the exact adoption boundary for this outcome.
Runtime sessions and every returned result bind the exact application…
Runtime sessions and every returned result bind the exact application audience, originating request, proof authority, and authenticated head.
Technical and authority boundary
Runtime sessions and every returned result bind the exact application audience, originating request, proof authority, and authenticated head.
- Why
- V124 removes ambiguity between representation and reality. A deployer no longer needs custom ports that accidentally duplicate execution, split a transaction, admit unverified replay, retain stale authority, expose private coordinates, enumerate recipients, or report a configured-but-inoperative dependency as production-ready. Verified reality can coordinate durable execution without granting unilateral jurisdiction to an application, institution, server, database, SDK, or network operator.
- Capability enabled
- Runtime sessions and every returned result bind the exact application audience, originating request, proof authority, and authenticated head.
- Compatibility
- The v124.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.0 migration record remains the exact adoption boundary for this outcome.
Durable server-side plans support stage, exactly-once execute, cancel, terminal outcome…
Durable server-side plans support stage, exactly-once execute, cancel, terminal outcome resolution, and recovery by semantic idempotency key.
Technical and authority boundary
Durable server-side plans support stage, exactly-once execute, cancel, terminal outcome resolution, and recovery by semantic idempotency key.
- Why
- V124 removes ambiguity between representation and reality. A deployer no longer needs custom ports that accidentally duplicate execution, split a transaction, admit unverified replay, retain stale authority, expose private coordinates, enumerate recipients, or report a configured-but-inoperative dependency as production-ready. Verified reality can coordinate durable execution without granting unilateral jurisdiction to an application, institution, server, database, SDK, or network operator.
- Capability enabled
- Durable server-side plans support stage, exactly-once execute, cancel, terminal outcome resolution, and recovery by semantic idempotency key.
- Compatibility
- The v124.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.0 migration record remains the exact adoption boundary for this outcome.
Replay and checkpoint verification returns only fully validated additions and…
Replay and checkpoint verification returns only fully validated additions and namespace metadata; unknown discriminators and statuses fail before callbacks.
Technical and authority boundary
Replay and checkpoint verification returns only fully validated additions and namespace metadata; unknown discriminators and statuses fail before callbacks.
- Why
- V124 removes ambiguity between representation and reality. A deployer no longer needs custom ports that accidentally duplicate execution, split a transaction, admit unverified replay, retain stale authority, expose private coordinates, enumerate recipients, or report a configured-but-inoperative dependency as production-ready. Verified reality can coordinate durable execution without granting unilateral jurisdiction to an application, institution, server, database, SDK, or network operator.
- Capability enabled
- Replay and checkpoint verification returns only fully validated additions and namespace metadata; unknown discriminators and statuses fail before callbacks.
- Compatibility
- The v124.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.0 migration record remains the exact adoption boundary for this outcome.
Access-filtered hydration prevents unauthorized private additions, coordinates, membership, or plaintext…
Access-filtered hydration prevents unauthorized private additions, coordinates, membership, or plaintext from reaching the caller.
Technical and authority boundary
Access-filtered hydration prevents unauthorized private additions, coordinates, membership, or plaintext from reaching the caller.
- Why
- V124 removes ambiguity between representation and reality. A deployer no longer needs custom ports that accidentally duplicate execution, split a transaction, admit unverified replay, retain stale authority, expose private coordinates, enumerate recipients, or report a configured-but-inoperative dependency as production-ready. Verified reality can coordinate durable execution without granting unilateral jurisdiction to an application, institution, server, database, SDK, or network operator.
- Capability enabled
- Access-filtered hydration prevents unauthorized private additions, coordinates, membership, or plaintext from reaching the caller.
- Compatibility
- The v124.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.0 migration record remains the exact adoption boundary for this outcome.
Atomic world, inventory/material, Settlement, and Reserve transaction effects advance every…
Atomic world, inventory/material, Settlement, and Reserve transaction effects advance every declared participant head or write zero accepted state.
Technical and authority boundary
Atomic world, inventory/material, Settlement, and Reserve transaction effects advance every declared participant head or write zero accepted state.
- Why
- V124 removes ambiguity between representation and reality. A deployer no longer needs custom ports that accidentally duplicate execution, split a transaction, admit unverified replay, retain stale authority, expose private coordinates, enumerate recipients, or report a configured-but-inoperative dependency as production-ready. Verified reality can coordinate durable execution without granting unilateral jurisdiction to an application, institution, server, database, SDK, or network operator.
- Capability enabled
- Atomic world, inventory/material, Settlement, and Reserve transaction effects advance every declared participant head or write zero accepted state.
- Compatibility
- The v124.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.0 migration record remains the exact adoption boundary for this outcome.
Privacy-safe recipient resolution is consent-bound, rate-limited, non-enumerable, and subordinate to…
Privacy-safe recipient resolution is consent-bound, rate-limited, non-enumerable, and subordinate to the enclosing transfer proof object.
Technical and authority boundary
Privacy-safe recipient resolution is consent-bound, rate-limited, non-enumerable, and subordinate to the enclosing transfer proof object.
- Why
- V124 removes ambiguity between representation and reality. A deployer no longer needs custom ports that accidentally duplicate execution, split a transaction, admit unverified replay, retain stale authority, expose private coordinates, enumerate recipients, or report a configured-but-inoperative dependency as production-ready. Verified reality can coordinate durable execution without granting unilateral jurisdiction to an application, institution, server, database, SDK, or network operator.
- Capability enabled
- Privacy-safe recipient resolution is consent-bound, rate-limited, non-enumerable, and subordinate to the enclosing transfer proof object.
- Compatibility
- The v124.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.0 migration record remains the exact adoption boundary for this outcome.
Capability descriptors distinguish configured presence from evidenced operational readiness for…
Capability descriptors distinguish configured presence from evidenced operational readiness for every required production dependency. The implementation remains universal. V124 creates no consumer-specific application identity, issuer, admission path, or authority tier. Existing application/principal admission remains unchanged.
Technical and authority boundary
Capability descriptors distinguish configured presence from evidenced operational readiness for every required production dependency. The implementation remains universal. V124 creates no consumer-specific application identity, issuer, admission path, or authority tier. Existing application/principal admission remains unchanged.
- Why
- V124 removes ambiguity between representation and reality. A deployer no longer needs custom ports that accidentally duplicate execution, split a transaction, admit unverified replay, retain stale authority, expose private coordinates, enumerate recipients, or report a configured-but-inoperative dependency as production-ready. Verified reality can coordinate durable execution without granting unilateral jurisdiction to an application, institution, server, database, SDK, or network operator.
- Capability enabled
- Capability descriptors distinguish configured presence from evidenced operational readiness for every required production dependency. The implementation remains universal. V124 creates no consumer-specific application identity, issuer, admission path, or authority tier. Existing application/principal admission remains unchanged.
- Compatibility
- The v124.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
V124 removes ambiguity between representation and reality. A deployer no longer needs custom ports that accidentally duplicate execution, split a transaction, admit unverified replay, retain stale authority, expose private coordinates, enumerate recipients, or report a configured-but-inoperative dependency as production-ready. Verified reality can coordinate durable execution without granting unilateral jurisdiction to an application, institution, server, database, SDK, or network operator.
Available outcomes
Capabilities now available
Canonical live Kai exposes exact whole-pulse and micro-pulse coordinates derived…
Canonical live Kai exposes exact whole-pulse and micro-pulse coordinates derived from pulses since genesis through the existing phi-exact ties-to-even bridge.
Proof-authority challenges bind application, artifact digest, exact scopes, consent digest…
Proof-authority challenges bind application, artifact digest, exact scopes, consent digest, bounded whole-pulse lifetime, and nonce without reinterpreting V123 fields.
One runtime factory binds existing proof authority, subject ownership/head, namespaces…
One runtime factory binds existing proof authority, subject ownership/head, namespaces, revocation, durable journal/checkpoint, plans, transaction context, private access, and recipient resolution.
Runtime sessions and every returned result bind the exact application…
Runtime sessions and every returned result bind the exact application audience, originating request, proof authority, and authenticated head.
Durable server-side plans support stage, exactly-once execute, cancel, terminal outcome…
Durable server-side plans support stage, exactly-once execute, cancel, terminal outcome resolution, and recovery by semantic idempotency key.
Replay and checkpoint verification returns only fully validated additions and…
Replay and checkpoint verification returns only fully validated additions and namespace metadata; unknown discriminators and statuses fail before callbacks.
Access-filtered hydration prevents unauthorized private additions, coordinates, membership, or plaintext…
Access-filtered hydration prevents unauthorized private additions, coordinates, membership, or plaintext from reaching the caller.
Atomic world, inventory/material, Settlement, and Reserve transaction effects advance every…
Atomic world, inventory/material, Settlement, and Reserve transaction effects advance every declared participant head or write zero accepted state.
Privacy-safe recipient resolution is consent-bound, rate-limited, non-enumerable, and subordinate to…
Privacy-safe recipient resolution is consent-bound, rate-limited, non-enumerable, and subordinate to the enclosing transfer proof object.
Capability descriptors distinguish configured presence from evidenced operational readiness for…
Capability descriptors distinguish configured presence from evidenced operational readiness for every required production dependency. The implementation remains universal. V124 creates no consumer-specific application identity, issuer, admission path, or authority tier. Existing application/principal admission remains unchanged.
Primitive boundary
Primitives affected
- proof
- identity
- ownership
- settlement
- transfer
- verification
- local-truth
- continuity
- reserve
- sealed-artifact
- governance
Compatibility
Compatibility
Coordinated package identity
@receiz/sdk, @receiz/mcp-server, and @receiz/ai-skills are current at 124.0.0; current application compatibility is >=124.0.0 <125.0.0.
This exact v124.0.0 compatibility boundary remains binding.
V123 proof objects
Historical V123 sealed proof object bytes, schemas, registry bytes, digests, signatures, and whole-pulse issuedAtKai semantics remain byte-compatible and unchanged.
This exact v124.0.0 compatibility boundary remains binding.
Micro-pulse precision
Explicit issuedAtKaiUPulse / expiresAtKaiUPulse or structured micro-pulse coordinates require a newly versioned schema; existing fields are never reinterpreted.
This exact v124.0.0 compatibility boundary remains binding.
Stable operation identifiers
Existing v122 and v123 SDK/MCP identifiers remain stable protocol names in the V124 distribution.
This exact v124.0.0 compatibility boundary remains binding.
Application admission
Existing application/principal admission remains unchanged; V124 creates no second identity or consumer-specific admission path.
This exact v124.0.0 compatibility boundary remains binding.
Proof authority
Sealed proof-object verification and exact authenticated heads remain authority; runtime responses must bind to the originating request and stronger evidence.
This exact v124.0.0 compatibility boundary remains binding.
Hosted persistence
Journal, checkpoint, plan, execution, session, and database records are sync/coordination/recovery beneath proof authority.
This exact v124.0.0 compatibility boundary remains binding.
Replay
Only fully verified additions and namespace metadata can enter application callbacks; unknown discriminators and statuses fail closed.
This exact v124.0.0 compatibility boundary remains binding.
Private state
Private additions hydrate only after access verification; private coordinates and recipient membership are not projected to unauthorized callers.
This exact v124.0.0 compatibility boundary remains binding.
Atomic domains
World, inventory/material, Settlement, and Reserve transaction effects commit together or produce zero accepted writes.
This exact v124.0.0 compatibility boundary remains binding.
Recipient resolution
Username resolution returns a privacy-safe transfer coordinate only under consent and rate limits; it never exposes directory enumeration.
This exact v124.0.0 compatibility boundary remains binding.
Capability evidence
A dependency is operational only when its declared evidence passes; configured or present is not equivalent to operational.
This exact v124.0.0 compatibility boundary remains binding.
Durable memory
Durable proof memory remains first admission only, then append forever.
This exact v124.0.0 compatibility boundary remains binding.
Migration
Migration
Required: true
The Production Runtime for Verified Civilization. The three reviewed durable-runtime migrations are required for every production environment; all three are applied and independently confirmed on the configured production project. No proof-object migration or rewrite is required. Historical sealed proof object bytes remain authority and retain exact V123 semantics.
- Upgrade @receiz/sdk, @receiz/mcp-server, and @receiz/ai-skills together to the independently confirmed 124.0.0 publications.
- Set application compatibility to >=124.0.0 <125.0.0.
- Preserve V123 whole-pulse fields and introduce explicit micro-pulse fields only through their new schema.
- Configure durable journal, checkpoint, plan, revocation, transaction, private-access, and recipient-resolution dependencies.
- Require operational evidence for every required dependency and fail qualification closed when any evidence is absent.
- For each additional environment, apply the same reviewed migrations through approved deployment tooling and capture independent project, checksum, rollback, and post-application evidence.
- Verify request-bound proof/head authentication before enabling public runtime and execution calls.
Qualification
Conformance
pnpm test:v124-release-lock passes.
Passed · pnpm test:v124-release-lock passes.
Coordinated release identity tests pass for @receiz/sdk, @receiz/mcp-server, and @receiz/ai-skills at 124.0.0.
Passed · Coordinated release identity tests pass for @receiz/sdk, @receiz/mcp-server, and @receiz/ai-skills at 124.0.0.
Focused V124 SDK adversarial and typecheck gates pass.
Passed · Focused V124 SDK adversarial and typecheck gates pass.
OpenAPI generation and contract tests pass.
Passed · OpenAPI generation and contract tests pass.
Receiz Docs V124 archive and evidence tests pass.
Passed · Receiz Docs V124 archive and evidence tests pass.
Release-freeze focused contracts pass.
Passed · Release-freeze focused contracts pass.
Control boundary
Governance
- Verification
- Unknown
- Declared change class
- No separate classification record
- Release approval
- No separate approval record
- Risk owner
- No separate assignment recorded
No checked governance verification evidence is bound to this release. Release approval and risk ownership are not inferred.
Registry boundary
Registry
- Version
- 124.0.0
- Digest
d02429151b0bcebdaeb89485792e377afc55130f9a25e07982c1c88221314247- Predecessor
945a581d1fc49c2dc18fbe8c129771ef464b8a58b96188bce561e88ae8b6ceeb
Archive projection
Audience, domain, and change-kind facets
- Audiences
- developers · businesses · creators · institutions · people
- Domains
- sealed-proof-object · exact-head · live-kai · durable-journal · exactly-once-execution · replay · checkpoint · private-access · atomic-transaction · recipient-privacy · capability-evidence · 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
- Not Performed
- Signed attestation
- Absent
Exact source bytes
Provenance
This Academy record is a projection beneath its sources. Record SHA-256 5f688bf36f922d9f77207b6f025090b31b50aa0e67d6f7126d7a467436862258. Source-family inventory: complete.
SHA-256 38faa2d75e62f2b31e8ea9986c32740006e9eec2718eb3b44d7dfffb29064d54SHA-256 3705f9c12857fae20c3baa6f38b332aea718e9a8f5463ee2021f279d66b2376bSHA-256 8603517839ef261cceb15255ac5373a1ad64ca0c1404b9c5db6ea865c0bcc654SHA-256 7fe5166591d4eb23585918ea58f397b23a0d8b2e3b80f22174e1e808af8904b7SHA-256 4e781346d3623ec0f40dac7687094fbb4d7e75ddb4ce77f2b202e3bbefb2b55fSHA-256 c0a91d163dfd0a160decdea18d4b86e6407ff8c65676b73b0da36ed9f70e236eSHA-256 1836570117d8dbd1476b963bd0e0db988ac1b1e163e1b989a0943635ba2bfabeSHA-256 9a164fe7d25935e00b9c9b12c64365fa73667f76b68347aa0a18b459de7bbd23SHA-256 96732fa511239b072c128c7215db223601c56ad2a4985c7837d630a35a3d0e55SHA-256 5ab7d54a0dca6307c723c14d603b5e10a4d03e46a8dce3e7688cd1a6367378d7SHA-256 c1fdb51c1c216e9f72efd785af755220b5840f549c5856a71beafe0e6f937d1cSHA-256 ff3b89c0f929dfbdc03a3e0cf4e6c9e2e25417d6051e5e1f4ef1b0627e1efaa4SHA-256 119258efa97da919bbf003afcdf46b9fec5e2ee56368c76b5df297d6e58631fbSHA-256 bb98f54ebaf6b7f91515171be897dfb10a4812a9d4260e5af2ca1ca19f0d7204SHA-256 11c930f2c115d8ac877c2d4d595397b06e351d7632e0392a12a606d942404551SHA-256 5a8f7fab67f5ed84c603455b264cfc6618d30b55d74ec7c19dd8fab29b6f97fcSHA-256 c5a000f6b444943e67a67bc6c88110f5f932fd5dede11548729fb7faa43351d5SHA-256 2019cf5b62b5a93c32c908326cc9473a549ea564beef74cb43d9321037650934SHA-256 90047b6a37b1e85d2360f452f7ccdaebabc8d3aac229a6857f10c590dedf62a5SHA-256 6e27a29112102979860c73cf9f4c46d6b8abe9f12aa33f6e1bbcab2de4d386c2SHA-256 0b7ed2135e1274e71ca951eede7614a72efd432118bc4a4fbffa45f76ca7ee91