Current coordinated release
v128.0.0
Reality-Grade Infrastructure
Release date 2026-10-04
Outcome
Outcome
Carry the source once. Continue from it everywhere. Receiz removes the need to reconstruct authority from mutually inconsistent representations. Exact sealed sources carry identity and evidence; admitted history carries continuity; readers derive permitted state; authorized actors append under the existing law. A portable object does not require its originating application to remain the authority for its history.
Changes
What changed
AssetSeal — the asset carries its continuity
A standalone mobile-first console composes the implemented issue, lifecycle evidence, state derivation, export and independent verification path around one durable physical-asset subject. The original machine example uses real seals. Receiz ID preserves owner custody; QR identification, capture and scoped evidence lead into the actual tools. Participant authority and disclosure retain their documented application boundaries.
Technical and authority boundary
A standalone mobile-first console composes the implemented issue, lifecycle evidence, state derivation, export and independent verification path around one durable physical-asset subject. The original machine example uses real seals. Receiz ID preserves owner custody; QR identification, capture and scoped evidence lead into the actual tools. Participant authority and disclosure retain their documented application boundaries.
- Why
- The same exact source remains useful across institutions, applications, AI and disconnected devices. Retain the evidence instead of reconstructing it; verify the carried record instead of trusting whichever representation arrived last; continue authorized work without making delivery the permission to act. This is the common value expressed by the physical asset console, retained memory, AI tools and institutional workflows.
- Capability enabled
- A standalone mobile-first console composes the implemented issue, lifecycle evidence, state derivation, export and independent verification path around one durable physical-asset subject. The original machine example uses real seals. Receiz ID preserves owner custody; QR identification, capture and scoped evidence lead into the actual tools. Participant authority and disclosure retain their documented application boundaries.
- Compatibility
- The v128.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v128.0.0 migration record remains the exact adoption boundary for this outcome.
Mind — keep what you know and build on it
Shared and device-held public network documents retain the latest admitted snapshot for first paint. Verified additions extend that knowledge without returning the reader to an older checkpoint. Memory, evidence and intelligence remain bound to their existing source contracts.
Technical and authority boundary
Shared and device-held public network documents retain the latest admitted snapshot for first paint. Verified additions extend that knowledge without returning the reader to an older checkpoint. Memory, evidence and intelligence remain bound to their existing source contracts.
- Why
- The same exact source remains useful across institutions, applications, AI and disconnected devices. Retain the evidence instead of reconstructing it; verify the carried record instead of trusting whichever representation arrived last; continue authorized work without making delivery the permission to act. This is the common value expressed by the physical asset console, retained memory, AI tools and institutional workflows.
- Capability enabled
- Shared and device-held public network documents retain the latest admitted snapshot for first paint. Verified additions extend that knowledge without returning the reader to an older checkpoint. Memory, evidence and intelligence remain bound to their existing source contracts.
- Compatibility
- The v128.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v128.0.0 migration record remains the exact adoption boundary for this outcome.
AI — carry proof into the tools people already use
Manual installation, AI skills, SDK and MCP expose consented local sealing, verification, uploaded-artifact handling and source execution. Exact device-held sources survive transport; a tool description cannot grant custody or consent. Marketplace submission and marketplace approval remain distinct.
Technical and authority boundary
Manual installation, AI skills, SDK and MCP expose consented local sealing, verification, uploaded-artifact handling and source execution. Exact device-held sources survive transport; a tool description cannot grant custody or consent. Marketplace submission and marketplace approval remain distinct.
- Why
- The same exact source remains useful across institutions, applications, AI and disconnected devices. Retain the evidence instead of reconstructing it; verify the carried record instead of trusting whichever representation arrived last; continue authorized work without making delivery the permission to act. This is the common value expressed by the physical asset console, retained memory, AI tools and institutional workflows.
- Capability enabled
- Manual installation, AI skills, SDK and MCP expose consented local sealing, verification, uploaded-artifact handling and source execution. Exact device-held sources survive transport; a tool description cannot grant custody or consent. Marketplace submission and marketplace approval remain distinct.
- Compatibility
- The v128.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v128.0.0 migration record remains the exact adoption boundary for this outcome.
Institutions — preserve authority before a handoff becomes a dispute
Advantage, Solutions, government/defense, banking/financial crime, Fraud and Proof Graph make the same implemented infrastructure legible for organizational knowledge, physical assets, evidence and authorized action. Offline Studio provides a direct way to exercise supported file-carried workflows.
Technical and authority boundary
Advantage, Solutions, government/defense, banking/financial crime, Fraud and Proof Graph make the same implemented infrastructure legible for organizational knowledge, physical assets, evidence and authorized action. Offline Studio provides a direct way to exercise supported file-carried workflows.
- Why
- The same exact source remains useful across institutions, applications, AI and disconnected devices. Retain the evidence instead of reconstructing it; verify the carried record instead of trusting whichever representation arrived last; continue authorized work without making delivery the permission to act. This is the common value expressed by the physical asset console, retained memory, AI tools and institutional workflows.
- Capability enabled
- Advantage, Solutions, government/defense, banking/financial crime, Fraud and Proof Graph make the same implemented infrastructure legible for organizational knowledge, physical assets, evidence and authorized action. Offline Studio provides a direct way to exercise supported file-carried workflows.
- Compatibility
- The v128.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v128.0.0 migration record remains the exact adoption boundary for this outcome.
Continuity — keep the original through every append
Native recovery, PBI enrichment, Showcase visibility, source-scoped signing and local publication preserve the same proof identity. Accepted route truth now selects that subject even before the local handoff is available. No delivery response replaces sealed local truth or permits a competing subject.
Technical and authority boundary
Native recovery, PBI enrichment, Showcase visibility, source-scoped signing and local publication preserve the same proof identity. Accepted route truth now selects that subject even before the local handoff is available. No delivery response replaces sealed local truth or permits a competing subject.
- Why
- The same exact source remains useful across institutions, applications, AI and disconnected devices. Retain the evidence instead of reconstructing it; verify the carried record instead of trusting whichever representation arrived last; continue authorized work without making delivery the permission to act. This is the common value expressed by the physical asset console, retained memory, AI tools and institutional workflows.
- Capability enabled
- Native recovery, PBI enrichment, Showcase visibility, source-scoped signing and local publication preserve the same proof identity. Accepted route truth now selects that subject even before the local handoff is available. No delivery response replaces sealed local truth or permits a competing subject.
- Compatibility
- The v128.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v128.0.0 migration record remains the exact adoption boundary for this outcome.
Discovery — make the solution understandable and shareable
Institutional language, 14-language Fraud presentation, use-case guides, foundation explanations, crawlable text and custom social artwork connect concrete user problems to the implemented tools. The Academy records the complete v120–v128 progression and exact published package coordinates.
Technical and authority boundary
Institutional language, 14-language Fraud presentation, use-case guides, foundation explanations, crawlable text and custom social artwork connect concrete user problems to the implemented tools. The Academy records the complete v120–v128 progression and exact published package coordinates.
- Why
- The same exact source remains useful across institutions, applications, AI and disconnected devices. Retain the evidence instead of reconstructing it; verify the carried record instead of trusting whichever representation arrived last; continue authorized work without making delivery the permission to act. This is the common value expressed by the physical asset console, retained memory, AI tools and institutional workflows.
- Capability enabled
- Institutional language, 14-language Fraud presentation, use-case guides, foundation explanations, crawlable text and custom social artwork connect concrete user problems to the implemented tools. The Academy records the complete v120–v128 progression and exact published package coordinates.
- Compatibility
- The v128.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v128.0.0 migration record remains the exact adoption boundary for this outcome.
Recovered identity — continue the existing Showcase
An SDK-admitted recovered-account signer carries actions on the account's accepted Showcase without relabeling the actor or reminting the subject. Local hide/unhide, successor publication, retries and cold readers retain artifact identity, complete rooted membership, ancestry and sealed evidence roots. The accepted account relationship persists in durable local truth; a cookie or public placement cannot grant artifact admission.
Technical and authority boundary
An SDK-admitted recovered-account signer carries actions on the account's accepted Showcase without relabeling the actor or reminting the subject. Local hide/unhide, successor publication, retries and cold readers retain artifact identity, complete rooted membership, ancestry and sealed evidence roots. The accepted account relationship persists in durable local truth; a cookie or public placement cannot grant artifact admission.
- Why
- The same exact source remains useful across institutions, applications, AI and disconnected devices. Retain the evidence instead of reconstructing it; verify the carried record instead of trusting whichever representation arrived last; continue authorized work without making delivery the permission to act. This is the common value expressed by the physical asset console, retained memory, AI tools and institutional workflows.
- Capability enabled
- An SDK-admitted recovered-account signer carries actions on the account's accepted Showcase without relabeling the actor or reminting the subject. Local hide/unhide, successor publication, retries and cold readers retain artifact identity, complete rooted membership, ancestry and sealed evidence roots. The accepted account relationship persists in durable local truth; a cookie or public placement cannot grant artifact admission.
- Compatibility
- The v128.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v128.0.0 migration record remains the exact adoption boundary for this outcome.
First paint — paint held proof immediately
Known owner and public proof prepares independently of delayed secondary navigation. Complete admitted Mind and Showcase sources survive route changes, PWA navigation and unavailable discovery. Hidden historical media cannot veto an admitted public visibility transition, while complete owner archive export still requires all child custody.
Technical and authority boundary
Known owner and public proof prepares independently of delayed secondary navigation. Complete admitted Mind and Showcase sources survive route changes, PWA navigation and unavailable discovery. Hidden historical media cannot veto an admitted public visibility transition, while complete owner archive export still requires all child custody.
- Why
- The same exact source remains useful across institutions, applications, AI and disconnected devices. Retain the evidence instead of reconstructing it; verify the carried record instead of trusting whichever representation arrived last; continue authorized work without making delivery the permission to act. This is the common value expressed by the physical asset console, retained memory, AI tools and institutional workflows.
- Capability enabled
- Known owner and public proof prepares independently of delayed secondary navigation. Complete admitted Mind and Showcase sources survive route changes, PWA navigation and unavailable discovery. Hidden historical media cannot veto an admitted public visibility transition, while complete owner archive export still requires all child custody.
- Compatibility
- The v128.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v128.0.0 migration record remains the exact adoption boundary for this outcome.
Signing — enrich the admitted Original
Compare-and-set storage binds the exact predecessor artifact rather than an unrelated legacy aggregate. Retry resolves the original attempt under its actual source; signing history appends without replacing an Original or its media.
Technical and authority boundary
Compare-and-set storage binds the exact predecessor artifact rather than an unrelated legacy aggregate. Retry resolves the original attempt under its actual source; signing history appends without replacing an Original or its media.
- Why
- The same exact source remains useful across institutions, applications, AI and disconnected devices. Retain the evidence instead of reconstructing it; verify the carried record instead of trusting whichever representation arrived last; continue authorized work without making delivery the permission to act. This is the common value expressed by the physical asset console, retained memory, AI tools and institutional workflows.
- Capability enabled
- Compare-and-set storage binds the exact predecessor artifact rather than an unrelated legacy aggregate. Retry resolves the original attempt under its actual source; signing history appends without replacing an Original or its media.
- Compatibility
- The v128.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v128.0.0 migration record remains the exact adoption boundary for this outcome.
Memory Crystal — save the exact prepared state
Save consumes the exact current coordinate's prepared source immediately. It does not rebuild on click, reseal known truth, or wait for global publication. Stale prepared coordinates cannot replace the current admitted state.
Technical and authority boundary
Save consumes the exact current coordinate's prepared source immediately. It does not rebuild on click, reseal known truth, or wait for global publication. Stale prepared coordinates cannot replace the current admitted state.
- Why
- The same exact source remains useful across institutions, applications, AI and disconnected devices. Retain the evidence instead of reconstructing it; verify the carried record instead of trusting whichever representation arrived last; continue authorized work without making delivery the permission to act. This is the common value expressed by the physical asset console, retained memory, AI tools and institutional workflows.
- Capability enabled
- Save consumes the exact current coordinate's prepared source immediately. It does not rebuild on click, reseal known truth, or wait for global publication. Stale prepared coordinates cannot replace the current admitted state.
- Compatibility
- The v128.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v128.0.0 migration record remains the exact adoption boundary for this outcome.
Identity Record — recover the account with carried proof
Fractional carried account projections restore through the existing authority encoding without changing integer-only admission digests. Local proof acceptance projects the recovered account immediately; online session recovery, import and binding enrich beneath it. Original custody and recovered-account actor evidence remain distinct and explicitly verified.
Technical and authority boundary
Fractional carried account projections restore through the existing authority encoding without changing integer-only admission digests. Local proof acceptance projects the recovered account immediately; online session recovery, import and binding enrich beneath it. Original custody and recovered-account actor evidence remain distinct and explicitly verified.
- Why
- The same exact source remains useful across institutions, applications, AI and disconnected devices. Retain the evidence instead of reconstructing it; verify the carried record instead of trusting whichever representation arrived last; continue authorized work without making delivery the permission to act. This is the common value expressed by the physical asset console, retained memory, AI tools and institutional workflows.
- Capability enabled
- Fractional carried account projections restore through the existing authority encoding without changing integer-only admission digests. Local proof acceptance projects the recovered account immediately; online session recovery, import and binding enrich beneath it. Original custody and recovered-account actor evidence remain distinct and explicitly verified.
- Compatibility
- The v128.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v128.0.0 migration record remains the exact adoption boundary for this outcome.
Distribution — install the coordinated public runtime
Public discovery exposes 680 callable SDK exports. SDK and MCP expose 425 SDK client methods, 335 MCP tools, 43 AI skills and 37 manifests. The public manual kit exposes 195 scoped nonfinancial tools. These are separate interface inventories, not additional primitives or unrestricted marketplace permissions.
Technical and authority boundary
Public discovery exposes 680 callable SDK exports. SDK and MCP expose 425 SDK client methods, 335 MCP tools, 43 AI skills and 37 manifests. The public manual kit exposes 195 scoped nonfinancial tools. These are separate interface inventories, not additional primitives or unrestricted marketplace permissions.
- Why
- The same exact source remains useful across institutions, applications, AI and disconnected devices. Retain the evidence instead of reconstructing it; verify the carried record instead of trusting whichever representation arrived last; continue authorized work without making delivery the permission to act. This is the common value expressed by the physical asset console, retained memory, AI tools and institutional workflows.
- Capability enabled
- Public discovery exposes 680 callable SDK exports. SDK and MCP expose 425 SDK client methods, 335 MCP tools, 43 AI skills and 37 manifests. The public manual kit exposes 195 scoped nonfinancial tools. These are separate interface inventories, not additional primitives or unrestricted marketplace permissions.
- Compatibility
- The v128.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v128.0.0 migration record remains the exact adoption boundary for this outcome.
Public verification — retain historical evidence and inspect the successor
The public offline verifier carries the exact tagged canonical verifier and Offline Studio source books. Reality Grade Infrastructure disclosure v1.2.0 pins SDK128 and preserves the previous signed inventory; its owner-sealed disclosure proof is separate from the application release attestation.
Technical and authority boundary
The public offline verifier carries the exact tagged canonical verifier and Offline Studio source books. Reality Grade Infrastructure disclosure v1.2.0 pins SDK128 and preserves the previous signed inventory; its owner-sealed disclosure proof is separate from the application release attestation.
- Why
- The same exact source remains useful across institutions, applications, AI and disconnected devices. Retain the evidence instead of reconstructing it; verify the carried record instead of trusting whichever representation arrived last; continue authorized work without making delivery the permission to act. This is the common value expressed by the physical asset console, retained memory, AI tools and institutional workflows.
- Capability enabled
- The public offline verifier carries the exact tagged canonical verifier and Offline Studio source books. Reality Grade Infrastructure disclosure v1.2.0 pins SDK128 and preserves the previous signed inventory; its owner-sealed disclosure proof is separate from the application release attestation.
- Compatibility
- The v128.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v128.0.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
The same exact source remains useful across institutions, applications, AI and disconnected devices. Retain the evidence instead of reconstructing it; verify the carried record instead of trusting whichever representation arrived last; continue authorized work without making delivery the permission to act. This is the common value expressed by the physical asset console, retained memory, AI tools and institutional workflows.
Available outcomes
Capabilities now available
AssetSeal — the asset carries its continuity
A standalone mobile-first console composes the implemented issue, lifecycle evidence, state derivation, export and independent verification path around one durable physical-asset subject. The original machine example uses real seals. Receiz ID preserves owner custody; QR identification, capture and scoped evidence lead into the actual tools. Participant authority and disclosure retain their documented application boundaries.
Mind — keep what you know and build on it
Shared and device-held public network documents retain the latest admitted snapshot for first paint. Verified additions extend that knowledge without returning the reader to an older checkpoint. Memory, evidence and intelligence remain bound to their existing source contracts.
AI — carry proof into the tools people already use
Manual installation, AI skills, SDK and MCP expose consented local sealing, verification, uploaded-artifact handling and source execution. Exact device-held sources survive transport; a tool description cannot grant custody or consent. Marketplace submission and marketplace approval remain distinct.
Institutions — preserve authority before a handoff becomes a dispute
Advantage, Solutions, government/defense, banking/financial crime, Fraud and Proof Graph make the same implemented infrastructure legible for organizational knowledge, physical assets, evidence and authorized action. Offline Studio provides a direct way to exercise supported file-carried workflows.
Continuity — keep the original through every append
Native recovery, PBI enrichment, Showcase visibility, source-scoped signing and local publication preserve the same proof identity. Accepted route truth now selects that subject even before the local handoff is available. No delivery response replaces sealed local truth or permits a competing subject.
Discovery — make the solution understandable and shareable
Institutional language, 14-language Fraud presentation, use-case guides, foundation explanations, crawlable text and custom social artwork connect concrete user problems to the implemented tools. The Academy records the complete v120–v128 progression and exact published package coordinates.
Recovered identity — continue the existing Showcase
An SDK-admitted recovered-account signer carries actions on the account's accepted Showcase without relabeling the actor or reminting the subject. Local hide/unhide, successor publication, retries and cold readers retain artifact identity, complete rooted membership, ancestry and sealed evidence roots. The accepted account relationship persists in durable local truth; a cookie or public placement cannot grant artifact admission.
First paint — paint held proof immediately
Known owner and public proof prepares independently of delayed secondary navigation. Complete admitted Mind and Showcase sources survive route changes, PWA navigation and unavailable discovery. Hidden historical media cannot veto an admitted public visibility transition, while complete owner archive export still requires all child custody.
Signing — enrich the admitted Original
Compare-and-set storage binds the exact predecessor artifact rather than an unrelated legacy aggregate. Retry resolves the original attempt under its actual source; signing history appends without replacing an Original or its media.
Memory Crystal — save the exact prepared state
Save consumes the exact current coordinate's prepared source immediately. It does not rebuild on click, reseal known truth, or wait for global publication. Stale prepared coordinates cannot replace the current admitted state.
Identity Record — recover the account with carried proof
Fractional carried account projections restore through the existing authority encoding without changing integer-only admission digests. Local proof acceptance projects the recovered account immediately; online session recovery, import and binding enrich beneath it. Original custody and recovered-account actor evidence remain distinct and explicitly verified.
Distribution — install the coordinated public runtime
Public discovery exposes 680 callable SDK exports. SDK and MCP expose 425 SDK client methods, 335 MCP tools, 43 AI skills and 37 manifests. The public manual kit exposes 195 scoped nonfinancial tools. These are separate interface inventories, not additional primitives or unrestricted marketplace permissions.
Public verification — retain historical evidence and inspect the successor
The public offline verifier carries the exact tagged canonical verifier and Offline Studio source books. Reality Grade Infrastructure disclosure v1.2.0 pins SDK128 and preserves the previous signed inventory; its owner-sealed disclosure proof is separate from the application release attestation.
Primitive boundary
Primitives affected
- proof
- identity
- ownership
- settlement
- provenance
- media
- transfer
- verification
- public-witness
- continuity
- reserve
- sealed-artifact
- governance
Compatibility
Compatibility
Coordinated packages
SDK, MCP and AI skills install at exact 128.0.0; supported major range >=128.0.0 <129.0.0. Package publication integrity is recorded independently.
This exact v128.0.0 compatibility boundary remains binding.
Constitutional registry
V128 inherits the exact v127 registry and digest 8d0b5b839d02d9efbd4306cc99410595a183705c2670b76d2567eaaaade99065; no v128 registry or production SQL migration is created.
This exact v128.0.0 compatibility boundary remains binding.
Historical protocols
V120, v122, v123, v124, v125 and v127 operation names, schemas and law identities retain their implemented meaning beneath the v128 distribution.
This exact v128.0.0 compatibility boundary remains binding.
Sealed artifacts and verification
Existing source bytes, Signature V4, canonical document proof, native media carriers and offline verification remain authoritative; relabeling a package never requires resealing held truth.
This exact v128.0.0 compatibility boundary remains binding.
Identity and account entry
Entry stays frozen to 6e0d71c3f0e8b3092b4ec97eef39f5927667a01f. SDK-admitted recovery projects immediately; online recovery issues its existing fresh session cookie. Background imports cannot veto acceptance.
This exact v128.0.0 compatibility boundary remains binding.
Showcase recovered actions
Accepted recovered-account identity appends to the same existing subject through the established account relationship. The actual actor, root, predecessor and signature remain verified; original-device custody is not a universal prerequisite.
This exact v128.0.0 compatibility boundary remains binding.
Signing history
Exact predecessor artifact namespaces retain existing legacy aggregates and original attempt identity. Signing enrichment never remints or replaces an Original.
This exact v128.0.0 compatibility boundary remains binding.
First paint and PWA
Held admitted identity, membership, media and visible shell paint without weaker discovery. Background work only enriches; unavailable hidden media cannot replace settled public truth.
This exact v128.0.0 compatibility boundary remains binding.
Memory Crystal
Prepared exact-current-state source is saved immediately; stale coordinates reject and click-time rebuilding does not replace the prepared source.
This exact v128.0.0 compatibility boundary remains binding.
Ownership, Settlement and Reserve
Existing ownership, transfer, funded routes, Settlement and Reserve authority remain unchanged. V128 documentation and installation do not execute financial actions.
This exact v128.0.0 compatibility boundary remains binding.
AssetSeal
Export carries complete included workspace history and evidence. Restore requires admitted owner and supported empty-runtime composition; selective disclosure, independent history merging and cross-owner transfer are not implied.
This exact v128.0.0 compatibility boundary remains binding.
Mind and AI Crystals
Mind and MCP intelligence-source Crystals retain distinct reader contracts. The qualified Mind installer is independently versioned; generic verification is not universal import or sync.
This exact v128.0.0 compatibility boundary remains binding.
Public disclosure
Reality Grade Infrastructure v1.2.0 uses published SDK128 and preserves its exact v1.1.0 signed inventory. Its 167-file owner-sealed disclosure attestation is distinct from application release evidence.
This exact v128.0.0 compatibility boundary remains binding.
Migration
Migration
Required: false
No SQL, registry or artifact rewrite migrations are required. This distribution inherits the exact admitted v127 registry and preserves wire identities, carried source bytes and established custody. Package adoption advances to >=128.0.0 <129.0.0.
- Record current package coordinates, configured host, held Identity Seals, enrolled local signer custody and durable subject workspaces. Preserve exact originals and their admitted ancestry.
- Install @receiz/sdk@128.0.0, @receiz/mcp-server@128.0.0 and @receiz/ai-skills@128.0.0 together. Verify the publication integrity digests; do not republish immutable v128 tarballs to repair documentation.
- Bind distribution v128 to the inherited v127 registry, historical operation identifiers and existing current operation matrix. Do not create a v128 registry or replay already applied SQL.
- Reuse admitted local identity and valid signer enrollment. Restore accepted recovered-account custody through the existing account relationship; do not relabel its actor or remint the existing Showcase.
- Verify disconnected local sealing, saved-byte reopening, canonical verification and tamper rejection using installed resources. Retain complete source custody for full owner archive export.
- Configure historical HTTP only for a compatible implementing host where required. Preserve supported local execution and inspect exact published MCP declarations before strict consumer compilation.
- Update application and PWA release markers through the existing current-release manifest. Paint held proof immediately and let background propagation append beneath settled truth.
- Run installed SDK conformance and application-specific proof, identity, ownership, continuity and first-paint contracts. Record package publication, application deployment, smoke, disclosure signing and main release attestation separately.
Qualification
Conformance
Release qualification
Passed · 119 available gates completed through the original 113 passes and six recovered-environment reruns; original umbrella exit 1 preserved.
Isolated profile database
Not Run · No disposable profile database supplied for test:v108-profile-database.
Production smoke
Passed · 21 anonymous pages and 10 hosted conformance endpoints; no authenticated mutations.
Academy archive
Passed · 41 release archive contract tests; complete 189-route production export.
Governance controls
Passed · Existing governance check, evidence check and artifact-signature verification.
Governance controls: check, evidence-check and artifact-signature verification passed.
Passed · Governance controls: check, evidence-check and artifact-signature verification passed.
Governance check, evidence check and artifact-signature verification passed again.
Passed · Governance check, evidence check and artifact-signature verification passed again.
Control boundary
Governance
- Verification
- Passed
- Declared change class
- Normal
- Release approval
- v128.0.0-final-closeout-2026-10-04
- 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
- Binding
- Inherited byte-identically from v127.0.0; no patch registry was created.
- Digest
8d0b5b839d02d9efbd4306cc99410595a183705c2670b76d2567eaaaade99065- Predecessor
80137c2e6f294050ef36ff75e4daac15c7790b7f04d9a91fab9d1970fa3c0b09
Archive projection
Audience, domain, and change-kind facets
- Audiences
- developers · businesses · creators · institutions · people
- Domains
- identity · proof · verification · governance · integration · continuity
- Change kinds
- capability · correction · compatibility · governance · performance · security
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 c11ce719fe9882eb46f908beec64618e16c79d88e6eb9b928f0ac37ca472e792. Source-family inventory: complete.
SHA-256 b00975bc57d655153f16d3270cef5d2a99e074debd9ce5e454bb9d73d94c788eSHA-256 a8766e68d55394499fd7a92bb9b418c89730f375c84bc678757bdbd8a977db2eSHA-256 f9f713c7a4d75ab4ffccc4551cdaeaa6e9268978222d7f8cbbc13e3683155c8aSHA-256 3dfa9067939cff89623ccdb3ea073f55c57379320a2f639e8c688bb42232762eSHA-256 cf35ec9a0cb2561cb4a45fd94525c465058a4942138ede981291582ebd02267fSHA-256 90b0abe0e7acc0a8a225d464ac166f2935f93fc5fa38a892ca00c30940753debSHA-256 0e38aef10444640b54f7822fbc0795a4b55914cc3b92a233f4fc1dada427fd2dSHA-256 70e67d86a3030a3d36d9db13053627d86709eff6fd34dcf13900e2f86cf7a25bSHA-256 ea2c4dbc85298e82a656515dcc7a5712d85ce5e5581b307f971ce758f6681dcaSHA-256 961491ffea1e6411c7e2d0eb54927c47bdea106496ea4e5f668c4d853492c37eSHA-256 ec76410af034c1caa3f12d609c82d048e589ffa4b3004f9a97b1bc45660df0bdSHA-256 b6faa6436badb728dac88f63174af903572106df88c2560911b247df362ded89SHA-256 24cab60d2ba680249ed8bbf2991a25f240f13ca9e6616ee6c97d93af0c26fd25SHA-256 9e5ec51c740e6b3a0d608f6080db3755f13df0c9b40ace7f8ff041b882d5bba1SHA-256 d6958a9012a8c9fa5afcc26531b973637db3a7b1fa05e694663f4785fc66d208SHA-256 d961b8f77302fc0e9a68b29da3fcf761ed15e03e73df1c32d37ee3c706430d85SHA-256 d9ddb3dd12b6586c7412347abee6eab443d5bf68d0fe78bb09e310f62e4357b1SHA-256 e1a09df96a4ec17a35da30636815ae164dbb75e4359dc43ffe2ac5bc0c6a3c9d