Current coordinated release
v127.0.0
Reality-Grade Infrastructure
Release date 2026-09-23
Outcome
Outcome
Carried truth becomes a local creation and intelligence foundation. People can create canonical proof on the device holding the source, retain identity and verified memory across experiences, and run intelligence against that evidence. Builders receive the same sealing and temporal proof machinery through the SDK, MCP and AI skills. V127 extends v126’s proof-object continuity into local execution: the object carries its life, the device performs the work, and every reader or agent remains accountable to the source.
Changes
What changed
Create proof where the source lives
The developer distribution packages the canonical sealer, durable device signer custody, proof resources and verification. After explicit enrollment and resource installation, sealing continues across process restarts without server signing or remote verification.
Technical and authority boundary
The developer distribution packages the canonical sealer, durable device signer custody, proof resources and verification. After explicit enrollment and resource installation, sealing continues across process restarts without server signing or remote verification.
- Why
- Creation, memory and intelligence can operate from held reality. A developer can seal a file on the machine that holds it, save the exact artifact and verify it after reopening. A person can retain sealed observations, inspect their source and ask a local model about that evidence. Export, restart, a new reader or a temporary transport outage does not authorize replacing the proof object's history.
- Capability enabled
- The developer distribution packages the canonical sealer, durable device signer custody, proof resources and verification. After explicit enrollment and resource installation, sealing continues across process restarts without server signing or remote verification.
- Compatibility
- The v127.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v127.0.0 migration record remains the exact adoption boundary for this outcome.
Run intelligence beside verified memory
Receiz Mind records local observations, exports sealed PNG Memory Crystals, inspects exact source and answers through its bundled local model. Generated answers remain interpretations grounded in evidence; they cannot rewrite the memory they read.
Technical and authority boundary
Receiz Mind records local observations, exports sealed PNG Memory Crystals, inspects exact source and answers through its bundled local model. Generated answers remain interpretations grounded in evidence; they cannot rewrite the memory they read.
- Why
- Creation, memory and intelligence can operate from held reality. A developer can seal a file on the machine that holds it, save the exact artifact and verify it after reopening. A person can retain sealed observations, inspect their source and ask a local model about that evidence. Export, restart, a new reader or a temporary transport outage does not authorize replacing the proof object's history.
- Capability enabled
- Receiz Mind records local observations, exports sealed PNG Memory Crystals, inspects exact source and answers through its bundled local model. Generated answers remain interpretations grounded in evidence; they cannot rewrite the memory they read.
- Compatibility
- The v127.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v127.0.0 migration record remains the exact adoption boundary for this outcome.
Carry continuity between experiences
Identity Seal/Record admission, multiple retained identities and explicit owner-scoped sync connect desktop, web and PWA while preserving the identity and enclosing proof objects. Connected web questions can use the running Mac's local model; that remote access path requires connectivity to the Mac.
Technical and authority boundary
Identity Seal/Record admission, multiple retained identities and explicit owner-scoped sync connect desktop, web and PWA while preserving the identity and enclosing proof objects. Connected web questions can use the running Mac's local model; that remote access path requires connectivity to the Mac.
- Why
- Creation, memory and intelligence can operate from held reality. A developer can seal a file on the machine that holds it, save the exact artifact and verify it after reopening. A person can retain sealed observations, inspect their source and ask a local model about that evidence. Export, restart, a new reader or a temporary transport outage does not authorize replacing the proof object's history.
- Capability enabled
- Identity Seal/Record admission, multiple retained identities and explicit owner-scoped sync connect desktop, web and PWA while preserving the identity and enclosing proof objects. Connected web questions can use the running Mac's local model; that remote access path requires connectivity to the Mac.
- Compatibility
- The v127.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v127.0.0 migration record remains the exact adoption boundary for this outcome.
Keep the whole object through recovery and publication
Complete Showcase proof images, material originals, carried attachments, account history and public economy history survive their export, restore and transport paths. A failed transport cannot revoke held proof.
Technical and authority boundary
Complete Showcase proof images, material originals, carried attachments, account history and public economy history survive their export, restore and transport paths. A failed transport cannot revoke held proof.
- Why
- Creation, memory and intelligence can operate from held reality. A developer can seal a file on the machine that holds it, save the exact artifact and verify it after reopening. A person can retain sealed observations, inspect their source and ask a local model about that evidence. Export, restart, a new reader or a temporary transport outage does not authorize replacing the proof object's history.
- Capability enabled
- Complete Showcase proof images, material originals, carried attachments, account history and public economy history survive their export, restore and transport paths. A failed transport cannot revoke held proof.
- Compatibility
- The v127.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v127.0.0 migration record remains the exact adoption boundary for this outcome.
Make scale serve existing truth
Retained memory heads, owner indexes, source checkpoints, bounded inspection and reduced backing-coordinate transport make complete held history usable without rebuilding it from partial pages. New verified history appends; settled first paint remains present.
Technical and authority boundary
Retained memory heads, owner indexes, source checkpoints, bounded inspection and reduced backing-coordinate transport make complete held history usable without rebuilding it from partial pages. New verified history appends; settled first paint remains present.
- Why
- Creation, memory and intelligence can operate from held reality. A developer can seal a file on the machine that holds it, save the exact artifact and verify it after reopening. A person can retain sealed observations, inspect their source and ask a local model about that evidence. Export, restart, a new reader or a temporary transport outage does not authorize replacing the proof object's history.
- Capability enabled
- Retained memory heads, owner indexes, source checkpoints, bounded inspection and reduced backing-coordinate transport make complete held history usable without rebuilding it from partial pages. New verified history appends; settled first paint remains present.
- Compatibility
- The v127.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v127.0.0 migration record remains the exact adoption boundary for this outcome.
Preserve lawful economic continuity
Settlement projects from published proof and retained local events; signed subscription terms retain owner binding and their Kai interval. A notification, model response or device signing certificate creates no ownership, entitlement or Settlement authority. This release record covers the full development interval since v126, including the independently published Mind releases and the coordinated v127 published developer distribution.
Technical and authority boundary
Settlement projects from published proof and retained local events; signed subscription terms retain owner binding and their Kai interval. A notification, model response or device signing certificate creates no ownership, entitlement or Settlement authority. This release record covers the full development interval since v126, including the independently published Mind releases and the coordinated v127 published developer distribution.
- Why
- Creation, memory and intelligence can operate from held reality. A developer can seal a file on the machine that holds it, save the exact artifact and verify it after reopening. A person can retain sealed observations, inspect their source and ask a local model about that evidence. Export, restart, a new reader or a temporary transport outage does not authorize replacing the proof object's history.
- Capability enabled
- Settlement projects from published proof and retained local events; signed subscription terms retain owner binding and their Kai interval. A notification, model response or device signing certificate creates no ownership, entitlement or Settlement authority. This release record covers the full development interval since v126, including the independently published Mind releases and the coordinated v127 published developer distribution.
- Compatibility
- The v127.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v127.0.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
Creation, memory and intelligence can operate from held reality. A developer can seal a file on the machine that holds it, save the exact artifact and verify it after reopening. A person can retain sealed observations, inspect their source and ask a local model about that evidence. Export, restart, a new reader or a temporary transport outage does not authorize replacing the proof object's history.
Available outcomes
Capabilities now available
Create proof where the source lives
The developer distribution packages the canonical sealer, durable device signer custody, proof resources and verification. After explicit enrollment and resource installation, sealing continues across process restarts without server signing or remote verification.
Run intelligence beside verified memory
Receiz Mind records local observations, exports sealed PNG Memory Crystals, inspects exact source and answers through its bundled local model. Generated answers remain interpretations grounded in evidence; they cannot rewrite the memory they read.
Carry continuity between experiences
Identity Seal/Record admission, multiple retained identities and explicit owner-scoped sync connect desktop, web and PWA while preserving the identity and enclosing proof objects. Connected web questions can use the running Mac's local model; that remote access path requires connectivity to the Mac.
Keep the whole object through recovery and publication
Complete Showcase proof images, material originals, carried attachments, account history and public economy history survive their export, restore and transport paths. A failed transport cannot revoke held proof.
Make scale serve existing truth
Retained memory heads, owner indexes, source checkpoints, bounded inspection and reduced backing-coordinate transport make complete held history usable without rebuilding it from partial pages. New verified history appends; settled first paint remains present.
Preserve lawful economic continuity
Settlement projects from published proof and retained local events; signed subscription terms retain owner binding and their Kai interval. A notification, model response or device signing certificate creates no ownership, entitlement or Settlement authority. This release record covers the full development interval since v126, including the independently published Mind releases and the coordinated v127 published developer distribution.
Primitive boundary
Primitives affected
- proof
- identity
- ownership
- settlement
- media
- transfer
- verification
- public-witness
- local-truth
- continuity
- market
- certificate
- sealed-artifact
- governance
Compatibility
Compatibility
Coordinated packages
SDK, MCP and AI skills use exact 127.0.0; current integrations require >=127.0.0 <128.0.0. Upgrade the three packages together and retain registry integrity.
This exact v127.0.0 compatibility boundary remains binding.
Current admission
Compiler and current operation admission bind ruleset 127.0.0, the exact v127 registry digest and operation matrix. Historical targets retain their original registry identities.
This exact v127.0.0 compatibility boundary remains binding.
SQL admission
The additive v127 registry successor migration is required before existing hosted admission functions accept the v127 digest. Receiz production has applied and verified it; other implementing deployments must check their own state.
This exact v127.0.0 compatibility boundary remains binding.
Historical proof objects
Original sealed bytes, creation coordinates, ownership history, registry identities and verification remain unchanged. A version upgrade cannot rewrite carried proof.
This exact v127.0.0 compatibility boundary remains binding.
Wire protocols
Existing versioned exports, MCP identifiers, KKSv1.0, Signature V4 and historical schema names retain their identities. Package127 does not rename every protocol to 127.
This exact v127.0.0 compatibility boundary remains binding.
Offline file sealing
Explicit one-time online device enrollment and locally installed canonical proof resources are required. Subsequent sealing and verification run locally across restarts; a seal call never enrolls implicitly.
This exact v127.0.0 compatibility boundary remains binding.
Local signer custody
Node private custody and browser origin-scoped IndexedDB remain separate. Installing packages or changing browser origins does not transfer a device signer or its enrollment.
This exact v127.0.0 compatibility boundary remains binding.
Full KaiSigil proof
Local generation uses canonical BLAKE3, Poseidon and Groth16 resources without enrollment or network calls. Bare pulse or timestamp values cannot replace full coordinate proof.
This exact v127.0.0 compatibility boundary remains binding.
Proof domains
Document sealing proof and subject temporal-envelope proof remain distinct. Inner hashes or a device signing certificate cannot replace enclosing identity, ownership, temporal or Settlement authority.
This exact v127.0.0 compatibility boundary remains binding.
Local V120 subjects
The shipped local host reuses admitted Identity Record and enclosing V120 source; exact identity, source bytes, durable history and temporal evidence survive restart. V122 admission does not remint historical V120 state.
This exact v127.0.0 compatibility boundary remains binding.
Portable subject history
Export carries exact sources, snapshot and temporal evidence. Import requires an enclosing sealed artifact and verification of every binding; bare JSON and copied bearer snapshots do not establish shared custody.
This exact v127.0.0 compatibility boundary remains binding.
Historical HTTP transport
Historical Connect methods require an explicit implementing custom host and legacyConnectTransport=http; credentials alone do not enable absent routes. Offline sealing and local subject execution do not require that host.
This exact v127.0.0 compatibility boundary remains binding.
MCP strict declarations
MCP127 includes three repository-alias declaration imports. Strict consumers use the exact installed-SDK mapping documented in the migration guide with skipLibCheck=false; unmodified declarations are not certified portable.
This exact v127.0.0 compatibility boundary remains binding.
Public inventories
Current discovery exposes 425 SDK client methods, 678 public functions, 330 MCP tools and 43 AI skills; the public catalog has 1,476 entries. Listings do not grant operational authority.
This exact v127.0.0 compatibility boundary remains binding.
Identity and first paint
Frozen account entry, admitted identity, complete known Showcase truth and verified local history remain primary. New verified additions append without replacing settled first paint.
This exact v127.0.0 compatibility boundary remains binding.
Settlement and payment
A checkout session, wallet read, device certificate, notification or model response does not establish completed payment, ownership or Settlement. Existing execution and proof boundaries remain binding.
This exact v127.0.0 compatibility boundary remains binding.
Receiz Mind
Mind retains its independent 1.1.0/build 2026092205 installer identity. Local recording and inference remain local; connected web access requires the running Mac. Completed-response Memory Crystal sealing remains deferred.
This exact v127.0.0 compatibility boundary remains binding.
Public disclosure
Reality Grade Infrastructure uses independent disclosure version 1.1.0 for product 127. Its Identity-Seal attestation binds its public inventory and does not substitute for the main application release attestation.
This exact v127.0.0 compatibility boundary remains binding.
Migration
Migration
Required: true
The additive v127 registry successor migration is required for an implementing hosted admission database to accept current v127 operations. Receiz production has already applied and verified it; this is not an instruction to replay the migration there. No artifact rewrite is required. Historical sealed bytes and wire identities remain unchanged.
- Record the current package versions, configured host, held identities, local signer directory and subject workspace before upgrading. Preserve the exact artifacts and durable local custody.
- Install SDK, MCP and AI skills at exact 127.0.0 together. Verify package integrity against the publication evidence and bind current ruleset, registry digest and operation matrix.
- For an implementing hosted admission database, inspect the migration ledger and both admission functions. Apply 20260923234022_v127_lawful_action_registry_successor.sql only where the v127 digest is not yet admitted; verify the additive digest change and preserved permissions. Receiz production is already complete.
- For offline file sealing, install the canonical local resources and explicitly enroll a device signer once while online. Reuse existing valid custody rather than replacing it. Disconnect, restart, seal, save, reopen and verify exact output bytes; test that tampering rejects.
- For local KaiSigil generation, install its separate canonical circuit resources and verify complete coordinate proof and causal succession. Do not substitute pulses or caller timestamps, and do not confuse document proof with a temporal envelope.
- For local V120 subjects, configure the shipped host, admitted Identity Record and enclosing source, retain durable state, and verify restart plus sealed export/import. Preserve original V120 identity and history; do not remint it through V122.
- Enable historical HTTP only when a compatible custom implementing host and explicit legacy transport are required. Use the supported local host and sealer directly for local execution. Map the exact MCP declaration alias below if strict compilation checks the affected types.
- Regenerate package-bound references and source digests; run installed examples and scoped identity, offline, temporal and coordinated release checks before adoption. Record application delivery, smoke, public disclosure signing and main release attestation independently.
Qualification
Conformance
Receiz Temporal authority conformance
Passed · Receiz application/protocol: pnpm test:temporal-authority-conformance; passed in the 116-command qualification of commit 211994264c2e.
Receiz Artifact verification conformance
Passed · Receiz application/protocol: pnpm test:v108-artifact-conformance; passed in the 116-command qualification of commit 211994264c2e.
Receiz Temporal conformance access conformance
Passed · Receiz application/protocol: pnpm test:temporal-conformance-access; passed in the 116-command qualification of commit 211994264c2e.
Receiz Economy conformance
Passed · Receiz application/protocol: pnpm test:economy-conformance; passed in the 116-command qualification of commit 211994264c2e.
Receiz Settlement conformance
Passed · Receiz application/protocol: pnpm test:settlement-conformance; passed in the 116-command qualification of commit 211994264c2e.
Receiz Identity conformance
Passed · Receiz application/protocol: pnpm test:identity-conformance; passed in the 116-command qualification of commit 211994264c2e.
Receiz Interoperability conformance
Passed · Receiz application/protocol: pnpm test:interoperability-conformance; passed in the 116-command qualification of commit 211994264c2e.
Receiz Issuance conformance
Passed · Receiz application/protocol: pnpm test:issuance-conformance; passed in the 116-command qualification of commit 211994264c2e.
Receiz Market conformance
Passed · Receiz application/protocol: pnpm test:market-conformance; passed in the 116-command qualification of commit 211994264c2e.
Receiz Verification conformance
Passed · Receiz application/protocol: pnpm test:verification-conformance; passed in the 116-command qualification of commit 211994264c2e.
Receiz World conformance
Passed · Receiz application/protocol: pnpm test:world-conformance; passed in the 116-command qualification of commit 211994264c2e.
Receiz Sports conformance
Passed · Receiz application/protocol: pnpm test:sports-conformance; passed in the 116-command qualification of commit 211994264c2e.
Receiz Signal Circuit conformance
Passed · Receiz application/protocol: pnpm test:signal-circuit-conformance; passed in the 116-command qualification of commit 211994264c2e.
Mind scoped source suite: 402 passed, 22 skipped. Existing 1.1.0/build 2026092205 installer identity and its separate historical distribution qualification are preserved; no new installer is claimed.
Passed · Mind scoped source suite: 402 passed, 22 skipped. Existing 1.1.0/build 2026092205 installer identity and its separate historical distribution qualification are preserved; no new installer is claimed.
Coordinated package release passes, including full SDK tests, type checking, builds, packed source exports, MCP package contracts and generated inventory parity.
Passed · Coordinated package release passes, including full SDK tests, type checking, builds, packed source exports, MCP package contracts and generated inventory parity.
Governance controls, evidence and artifact signature pass locally.
Passed · Governance controls, evidence and artifact signature pass locally.
Control boundary
Governance
- Verification
- Passed
- Declared change class
- High Risk
- Release approval
- v127.0.0-single-owner-release-authorization
- Risk owner
- bjklock
Dated signed attestations apply only to their exact commit, tree, and build; package publication, deployment, and production smoke remain independent evidence dimensions.
Explicit single-owner approval under the existing Identity Seal; no independent review occurred.
Registry boundary
Registry
- Version
- 127.0.0
- Digest
8d0b5b839d02d9efbd4306cc99410595a183705c2670b76d2567eaaaade99065- Predecessor
80137c2e6f294050ef36ff75e4daac15c7790b7f04d9a91fab9d1970fa3c0b09
Archive projection
Audience, domain, and change-kind facets
- Audiences
- Not established
- Domains
- Not established
- Change kinds
- Not established
Independent dimensions
Release boundary status
- Repository release
- Documented
- Git tag
- Present
- Package publication
- Confirmed
- Deployment
- Confirmed
- Production smoke
- Confirmed
- Signed attestation
- Present
Exact source bytes
Provenance
This Academy record is a projection beneath its sources. Record SHA-256 9d34290053a88f30ba5c39449e6dae84a8aa905ed77725391830ccd3fe2cb2f6. Source-family inventory: complete.
SHA-256 71421afa64a76b3587b1158ddfd237fb650711190298fdc8835f1ca7385f8d1eSHA-256 8957cfc16eb8a0a3c2aa103f840687f6b196fb80eddb63acb9a3bbd60d8ff00eSHA-256 e4a4e177b65d9af79427e6128eaf52f4ef5637e61e2b7eee61e1d6ec31aebfa4SHA-256 7f0bf9bff72437a8d5e0c47b3f02aca150d7c65dd1d60ce732808c4f11d8c3e5SHA-256 aeec0917d7470076436f3cd6955f245168958d922634e049a327bd0a927e115aSHA-256 a8766e68d55394499fd7a92bb9b418c89730f375c84bc678757bdbd8a977db2eSHA-256 f9f713c7a4d75ab4ffccc4551cdaeaa6e9268978222d7f8cbbc13e3683155c8aSHA-256 fefb1f79e7ffc8ddcc3f1e95a738d8b1409f1c7ef8584ced55e3837626e8e47bSHA-256 c6fd5976f388396169c152d3f109a5a5917de75beb984c5205b5867dc055080bSHA-256 3e0831b9d3198a2a7222ddbab90ae2a386be8dca81f580d22f812dd11af7602bSHA-256 26db0c0b5cf5190790a52cac9ea4e5147db1cf31a41983efb09a01cec32bf450SHA-256 86607147da141b9b4d93534c1b8a602298202ec28d56c47974db3ec5082454d0SHA-256 0e9fe3dfc1eac1441b31156873d27c4c2334792c19a9636c0800f19898c11bf4SHA-256 7608f829fea003fd2a1e934870690bd1c8cc16238ccf2562da0686e1d7e001bbSHA-256 694dc068d06f67fb92bef835221bb2a8f1d44bba09024f18d34ddd793db2df88SHA-256 a7f2d56be028c033f4bbedef63bf5396967bab262ed4a79377b01315ed0f3d7d