Current coordinated release
v124.1.0
Reality Becomes Infrastructure
The Production Runtime for Verified Civilization
Release date 2026-08-27
Outcome
Outcome
Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
Changes
What changed
Any sealed file becomes portable source-carried material
Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
Technical and authority boundary
Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Why
- Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Capability enabled
- Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Compatibility
- The v124.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.1.0 migration record remains the exact adoption boundary for this outcome.
Large mobile-browser video begins before whole-file settlement
The enclosing Signature-V4 artifact commits the progressive ledger. Verified first-frame ranges can play immediately while later ranges settle, without weakening legacy whole-artifact verification. Genesis posts bind directly to the signed artifact basis and manifest; they never require a successor-only native Record seal.
Technical and authority boundary
The enclosing Signature-V4 artifact commits the progressive ledger. Verified first-frame ranges can play immediately while later ranges settle, without weakening legacy whole-artifact verification. Genesis posts bind directly to the signed artifact basis and manifest; they never require a successor-only native Record seal.
- Why
- Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Capability enabled
- The enclosing Signature-V4 artifact commits the progressive ledger. Verified first-frame ranges can play immediately while later ranges settle, without weakening legacy whole-artifact verification. Genesis posts bind directly to the signed artifact basis and manifest; they never require a successor-only native Record seal.
- Compatibility
- The v124.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.1.0 migration record remains the exact adoption boundary for this outcome.
Global availability cannot outrun public truth
Large public packages are initialized, segmented, and finalized before their public coordinate is advertised. A fresh device can retrieve the complete committed family; the transport remains subordinate to the sealed artifact.
Technical and authority boundary
Large public packages are initialized, segmented, and finalized before their public coordinate is advertised. A fresh device can retrieve the complete committed family; the transport remains subordinate to the sealed artifact.
- Why
- Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Capability enabled
- Large public packages are initialized, segmented, and finalized before their public coordinate is advertised. A fresh device can retrieve the complete committed family; the transport remains subordinate to the sealed artifact.
- Compatibility
- The v124.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.1.0 migration record remains the exact adoption boundary for this outcome.
Durable global state no longer depends on a database
Content-addressed source families, exact causal heads, verified appends, and deterministic reconciliation let devices exchange and recover complete state globally. Infrastructure may relay and retain availability, but it cannot define, rewrite, or outrank the state carried by proof.
Technical and authority boundary
Content-addressed source families, exact causal heads, verified appends, and deterministic reconciliation let devices exchange and recover complete state globally. Infrastructure may relay and retain availability, but it cannot define, rewrite, or outrank the state carried by proof.
- Why
- Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Capability enabled
- Content-addressed source families, exact causal heads, verified appends, and deterministic reconciliation let devices exchange and recover complete state globally. Infrastructure may relay and retain availability, but it cannot define, rewrite, or outrank the state carried by proof.
- Compatibility
- The v124.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.1.0 migration record remains the exact adoption boundary for this outcome.
Raw RMC2/RMA3 material opens lawfully
openVerifiedReceizMaterialUrl dispatches on capsule encoding, projects raw RMA3 material directly, and never sends raw bytes into the compressed RMA2 decoder.
Technical and authority boundary
openVerifiedReceizMaterialUrl dispatches on capsule encoding, projects raw RMA3 material directly, and never sends raw bytes into the compressed RMA2 decoder.
- Why
- Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Capability enabled
- openVerifiedReceizMaterialUrl dispatches on capsule encoding, projects raw RMA3 material directly, and never sends raw bytes into the compressed RMA2 decoder.
- Compatibility
- The v124.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.1.0 migration record remains the exact adoption boundary for this outcome.
Source-carried replay preserves every verified branch
Exact sealed sources open, diff, merge, and project deterministically without a database, last-write-wins, or arrival-time head selection.
Technical and authority boundary
Exact sealed sources open, diff, merge, and project deterministically without a database, last-write-wins, or arrival-time head selection.
- Why
- Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Capability enabled
- Exact sealed sources open, diff, merge, and project deterministically without a database, last-write-wins, or arrival-time head selection.
- Compatibility
- The v124.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.1.0 migration record remains the exact adoption boundary for this outcome.
Receiz-ID conversation scales to every invited participant
Direct and group communication uses exact identity bindings, complete causal history, encrypted epoch grants, bounded work per operation, and no fixed total-member or history cap. Clear messages and epoch secrets remain outside model output.
Technical and authority boundary
Direct and group communication uses exact identity bindings, complete causal history, encrypted epoch grants, bounded work per operation, and no fixed total-member or history cap. Clear messages and epoch secrets remain outside model output.
- Why
- Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Capability enabled
- Direct and group communication uses exact identity bindings, complete causal history, encrypted epoch grants, bounded work per operation, and no fixed total-member or history cap. Clear messages and epoch secrets remain outside model output.
- Compatibility
- The v124.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.1.0 migration record remains the exact adoption boundary for this outcome.
Complete proof memory survives beyond the working window
A proof brain retains the entire admitted history, resolves bounded cognition windows, and retrieves exact primary objects without reloading or flattening the subject's memory into prompt text.
Technical and authority boundary
A proof brain retains the entire admitted history, resolves bounded cognition windows, and retrieves exact primary objects without reloading or flattening the subject's memory into prompt text.
- Why
- Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Capability enabled
- A proof brain retains the entire admitted history, resolves bounded cognition windows, and retrieves exact primary objects without reloading or flattening the subject's memory into prompt text.
- Compatibility
- The v124.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.1.0 migration record remains the exact adoption boundary for this outcome.
Private, cited cognition produces live Twin response and speech
Private imported memory stays server-side; delivered frames expose safe citations, digests, and expressly public excerpts. The Twin can generate live response and performance from the subject's proof-derived memory while its speech remains a non-authoritative proposal until deterministic command admission.
Technical and authority boundary
Private imported memory stays server-side; delivered frames expose safe citations, digests, and expressly public excerpts. The Twin can generate live response and performance from the subject's proof-derived memory while its speech remains a non-authoritative proposal until deterministic command admission.
- Why
- Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Capability enabled
- Private imported memory stays server-side; delivered frames expose safe citations, digests, and expressly public excerpts. The Twin can generate live response and performance from the subject's proof-derived memory while its speech remains a non-authoritative proposal until deterministic command admission.
- Compatibility
- The v124.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.1.0 migration record remains the exact adoption boundary for this outcome.
Identity-carried account continuity is complete without rewriting old truth
Identity Seal, Identity Record, and Receiz Key can carry profile, showcase, wallet, market positions/history, media, preferences, and proof history. Known verified state projects immediately; sync appends additions behind it. V1 completeness retains the exact pre-market domain law it signed, while newly sealed V2 completeness requires market continuity.
Technical and authority boundary
Identity Seal, Identity Record, and Receiz Key can carry profile, showcase, wallet, market positions/history, media, preferences, and proof history. Known verified state projects immediately; sync appends additions behind it. V1 completeness retains the exact pre-market domain law it signed, while newly sealed V2 completeness requires market continuity.
- Why
- Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Capability enabled
- Identity Seal, Identity Record, and Receiz Key can carry profile, showcase, wallet, market positions/history, media, preferences, and proof history. Known verified state projects immediately; sync appends additions behind it. V1 completeness retains the exact pre-market domain law it signed, while newly sealed V2 completeness requires market continuity.
- Compatibility
- The v124.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.1.0 migration record remains the exact adoption boundary for this outcome.
Application coherence is restored at the exact boundaries
The newest Clean Strike EPUB opens from verified Blob bytes; image posts never enter video playback-publication logic; video publication is deterministic rather than retry theater; authenticated profile counts reconcile to the stronger public proof register; and the owner signature ceremony affordance appears immediately after publication.
Technical and authority boundary
The newest Clean Strike EPUB opens from verified Blob bytes; image posts never enter video playback-publication logic; video publication is deterministic rather than retry theater; authenticated profile counts reconcile to the stronger public proof register; and the owner signature ceremony affordance appears immediately after publication.
- Why
- Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Capability enabled
- The newest Clean Strike EPUB opens from verified Blob bytes; image posts never enter video playback-publication logic; video publication is deterministic rather than retry theater; authenticated profile counts reconcile to the stronger public proof register; and the owner signature ceremony affordance appears immediately after publication.
- Compatibility
- The v124.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.1.0 migration record remains the exact adoption boundary for this outcome.
Transfer reseals accept the current receipt while preserving predecessor proof
The sealed original binds the current resealed receipt digest, while previousDigest independently verifies the predecessor chain.
Technical and authority boundary
The sealed original binds the current resealed receipt digest, while previousDigest independently verifies the predecessor chain.
- Why
- Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Capability enabled
- The sealed original binds the current resealed receipt digest, while previousDigest independently verifies the predecessor chain.
- Compatibility
- The v124.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.1.0 migration record remains the exact adoption boundary for this outcome.
Failed media settlement cannot survive unmount
Cancellation suppresses UI state updates only; failed enclosing-artifact settlement always revokes and evicts the cached projection.
Technical and authority boundary
Cancellation suppresses UI state updates only; failed enclosing-artifact settlement always revokes and evicts the cached projection.
- Why
- Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Capability enabled
- Cancellation suppresses UI state updates only; failed enclosing-artifact settlement always revokes and evicts the cached projection.
- Compatibility
- The v124.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.1.0 migration record remains the exact adoption boundary for this outcome.
SDK, MCP, AI Skills, and Receiz Docs share one callable capability map
RECEIZV1241CAPABILITYINVENTORY binds every capability family to exact exports, client methods, MCP tools, AI Skills, outcome, and authority boundary. The complete MCP registry contains 169 tools, including 26 V124 production-runtime tools.
Technical and authority boundary
RECEIZV1241CAPABILITYINVENTORY binds every capability family to exact exports, client methods, MCP tools, AI Skills, outcome, and authority boundary. The complete MCP registry contains 169 tools, including 26 V124 production-runtime tools.
- Why
- Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
- Capability enabled
- RECEIZV1241CAPABILITYINVENTORY binds every capability family to exact exports, client methods, MCP tools, AI Skills, outcome, and authority boundary. The complete MCP registry contains 169 tools, including 26 V124 production-runtime tools.
- Compatibility
- The v124.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.1.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
Any sealed file becomes portable source-carried material. Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
Available outcomes
Capabilities now available
Any sealed file becomes portable source-carried material
Exact bytes remain reconstructable from inline RMA2 or complete RMC1/RMC2 families. Browser-supported video, audio, images, EPUB, PDF, and text can render directly; arbitrary binary remains exact and exportable. No database, CDN, third-party media host, or external proof authority is required.
Large mobile-browser video begins before whole-file settlement
The enclosing Signature-V4 artifact commits the progressive ledger. Verified first-frame ranges can play immediately while later ranges settle, without weakening legacy whole-artifact verification. Genesis posts bind directly to the signed artifact basis and manifest; they never require a successor-only native Record seal.
Global availability cannot outrun public truth
Large public packages are initialized, segmented, and finalized before their public coordinate is advertised. A fresh device can retrieve the complete committed family; the transport remains subordinate to the sealed artifact.
Durable global state no longer depends on a database
Content-addressed source families, exact causal heads, verified appends, and deterministic reconciliation let devices exchange and recover complete state globally. Infrastructure may relay and retain availability, but it cannot define, rewrite, or outrank the state carried by proof.
Raw RMC2/RMA3 material opens lawfully
openVerifiedReceizMaterialUrl dispatches on capsule encoding, projects raw RMA3 material directly, and never sends raw bytes into the compressed RMA2 decoder.
Source-carried replay preserves every verified branch
Exact sealed sources open, diff, merge, and project deterministically without a database, last-write-wins, or arrival-time head selection.
Receiz-ID conversation scales to every invited participant
Direct and group communication uses exact identity bindings, complete causal history, encrypted epoch grants, bounded work per operation, and no fixed total-member or history cap. Clear messages and epoch secrets remain outside model output.
Complete proof memory survives beyond the working window
A proof brain retains the entire admitted history, resolves bounded cognition windows, and retrieves exact primary objects without reloading or flattening the subject's memory into prompt text.
Private, cited cognition produces live Twin response and speech
Private imported memory stays server-side; delivered frames expose safe citations, digests, and expressly public excerpts. The Twin can generate live response and performance from the subject's proof-derived memory while its speech remains a non-authoritative proposal until deterministic command admission.
Identity-carried account continuity is complete without rewriting old truth
Identity Seal, Identity Record, and Receiz Key can carry profile, showcase, wallet, market positions/history, media, preferences, and proof history. Known verified state projects immediately; sync appends additions behind it. V1 completeness retains the exact pre-market domain law it signed, while newly sealed V2 completeness requires market continuity.
Application coherence is restored at the exact boundaries
The newest Clean Strike EPUB opens from verified Blob bytes; image posts never enter video playback-publication logic; video publication is deterministic rather than retry theater; authenticated profile counts reconcile to the stronger public proof register; and the owner signature ceremony affordance appears immediately after publication.
Transfer reseals accept the current receipt while preserving predecessor proof
The sealed original binds the current resealed receipt digest, while previousDigest independently verifies the predecessor chain.
Failed media settlement cannot survive unmount
Cancellation suppresses UI state updates only; failed enclosing-artifact settlement always revokes and evicts the cached projection.
SDK, MCP, AI Skills, and Receiz Docs share one callable capability map
RECEIZV1241CAPABILITYINVENTORY binds every capability family to exact exports, client methods, MCP tools, AI Skills, outcome, and authority boundary. The complete MCP registry contains 169 tools, including 26 V124 production-runtime tools.
Primitive boundary
Primitives affected
- proof
- identity
- ownership
- settlement
- provenance
- media
- transfer
- verification
- public-witness
- local-truth
- continuity
- market
- reserve
- sealed-artifact
- governance
Compatibility
Compatibility
Application compatibility
Current source identity is 124.1.0; application and SDK compatibility remains exactly >=124.0.0 <125.0.0.
This exact v124.1.0 compatibility boundary remains binding.
SDK / MCP / AI Skills
Coordinated source identity is 124.1.0; publish together.
This exact v124.1.0 compatibility boundary remains binding.
Constitutional verifier
Source identity is 124.1.0; proof ruleset remains 124.0.0.
This exact v124.1.0 compatibility boundary remains binding.
Supported current SDK range
>=124.0.0 <125.0.0.
This exact v124.1.0 compatibility boundary remains binding.
Registry
V124 digest d02429151b0bcebdaeb89485792e377afc55130f9a25e07982c1c88221314247 remains exact.
This exact v124.1.0 compatibility boundary remains binding.
RMA2 / RMC1
Existing inline and segmented material remains readable.
This exact v124.1.0 compatibility boundary remains binding.
RMC2 / RMA3/raw
V124.1 readers dispatch raw material directly and verify the enclosing artifact.
This exact v124.1.0 compatibility boundary remains binding.
Legacy whole-SHA media
Complete settlement remains required before final admission.
This exact v124.1.0 compatibility boundary remains binding.
Progressive media
Requires the signed progressive commitment; unsupported artifacts fall back to whole verification.
This exact v124.1.0 compatibility boundary remains binding.
Genesis progressive media
Signed ranges bind to the Signature-V4 artifact basis and committed manifest/ledger without requiring successor-only native Record metadata.
This exact v124.1.0 compatibility boundary remains binding.
Portable completeness V1
Preserves the exact pre-market domain set under which the Receiz Key was sealed.
This exact v124.1.0 compatibility boundary remains binding.
Portable completeness V2
Newly sealed complete state requires the market domain in addition to every V1 domain.
This exact v124.1.0 compatibility boundary remains binding.
Historical proof objects
No rewrite, reseal, migration, or identity reissue.
This exact v124.1.0 compatibility boundary remains binding.
v122 / v123 protocol names
Stable identifiers remain unchanged.
This exact v124.1.0 compatibility boundary remains binding.
Public 124.0.3 packages
Remain historical public evidence; they are not relabeled as 124.1.0.
This exact v124.1.0 compatibility boundary remains binding.
Migration
Migration
Required: false
No artifact, registry, database, identity, conversation, ownership, or settlement migration is required. Existing sealed proof objects remain exact-byte valid. Previously sealed V1 portable-completeness claims retain their original pre-market domain semantics; new complete exports emit V2 and include market continuity.
- Upgrade @receiz/sdk, @receiz/mcp-server, and @receiz/ai-skills together to 124.1.0 after publication.
- Import RECEIZV1241CAPABILITYINVENTORY and expose only the capability families the trusted host actually supports.
- Publish complete RMC2 packages before advertising public coordinates.
- Dispatch raw material by capsuleEncoding and retain RMA2/RMC1 compatibility.
- Use signed progressive ledgers for range playback and retain whole-artifact fallback.
- Keep source bytes, conversation cleartext, epoch secrets, private memory, and identity-carried private state out of MCP/model output.
Qualification
Conformance
Identity conformance
Passed · Receiz ID, PBI, recovery, portable continuity, and exact identity-proof admission passed pnpm test:identity-conformance.
Economy conformance
Passed · Persisted value tuples, deterministic replay, value-source traceability, and zero-write rejection passed pnpm test:economy-conformance.
Settlement conformance
Passed · Settlement, Reserve, certificate, note, purchase, and governed transfer math passed pnpm test:settlement-conformance.
Interoperability conformance
Passed · Cross-runtime protocol identity, exact schemas, and bounded external mechanics passed pnpm test:interoperability-conformance.
Issuance conformance
Passed · Proof-native issue, authority, receipt, and custody transitions passed pnpm test:issuance-conformance.
Market conformance
Passed · Ownership positions, market history, deterministic first paint, and verified append continuity passed pnpm test:market-conformance.
Verification conformance
Passed · Exact bytes, enclosing-artifact authority, tamper rejection, and verifier parity passed pnpm test:verification-conformance.
World conformance
Passed · Exact heads, causal replay, atomic world transitions, proof memory, and bounded Twin proposals passed pnpm test:world-conformance.
Sports conformance
Passed · Deterministic sports state, public report evidence, history, rollups, and badge projection passed pnpm test:sports-conformance.
Signal Circuit conformance
Passed · Deterministic signal admission, execution, history, and public conformance evidence passed pnpm test:signal-circuit-conformance.
Governance controls
Passed · Governance document, evidence-cadence, and seven-artifact Ed25519 signature controls passed their three mandatory release gates.
Control boundary
Governance
- Verification
- Passed
- Declared change class
- High Risk
- Release approval
- v124.1.0-source-carried-convergence-governance
- Risk owner
- Enterprise Risk and Resilience
Governance controls and the signed governance-artifact system passed against the exact checked release evidence.
The canonical governance record declares the high-risk release boundary; a dated signed V124.1.0 release attestation remains absent and is not inferred from publication, deployment, or smoke.
Registry boundary
Registry
- Version
- 124.0.0
- Binding
- Inherited byte-identically from v124.0.0; no patch registry was created.
- Digest
d02429151b0bcebdaeb89485792e377afc55130f9a25e07982c1c88221314247- Predecessor
945a581d1fc49c2dc18fbe8c129771ef464b8a58b96188bce561e88ae8b6ceeb
Archive projection
Audience, domain, and change-kind facets
- Audiences
- developers · businesses · creators · institutions · people
- Domains
- proof · verification · media · identity · ownership · provenance · public witness · continuity · offline proof · conversation · memory · market
- Change kinds
- capability · correction · compatibility · performance · 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 73b7b84d778c7708495c40d9b8b6f762a9af702f9a86fa9f227be6865bf0814d. Source-family inventory: complete.
SHA-256 4e781346d3623ec0f40dac7687094fbb4d7e75ddb4ce77f2b202e3bbefb2b55fSHA-256 c0a91d163dfd0a160decdea18d4b86e6407ff8c65676b73b0da36ed9f70e236eSHA-256 acfda34434455190b070640de2647b5604e13385eed3a039cb03ebff62d96318SHA-256 0f6167b242377c49a08ec747f6945ca6e3553c2660f5b360906180f444d99926SHA-256 95188faf54fa219c6010279cdd8e58c68c5e7d36cc586dc2af6acf4ddec01a72SHA-256 2595f62dc84f95ac4c31b376b260c470459bb83341f92c3d6db556bf987d8ef4SHA-256 821a8b6a8b10b1c3faf9465f10b9af1f643be2fb1119dec5e5c3624c35d7312fSHA-256 455eb259a8dc9a69cff338ef9c626718c7628b01ba0027fa50879c3e62bdcf96SHA-256 7d026a6f1a16688dc3c2666df8b96935542a6025587cfff33e2494e33f2440ceSHA-256 b8deb07c25ac6596ce1ace4a170d5b05b029ad077eab6209715bb3df6819fd8aSHA-256 74c06c099a351f83e7c4d92707c91bf96da76f733ce183e0b09ad3f0c07f58c7SHA-256 75cde4344bfeae86ebacfd147c6857d1437de64deae8581999290a13078fee11SHA-256 cdb2781d2143e79cdb9817722d11bb892cb5c5ba5008cef451b5ab8c53d8ecc6SHA-256 9174207a557c146cb6feac4a0e35d503af3d945f71d56b3f77c77b00fb6f9653SHA-256 db38347e086e2aeb375bfa90b07e786789c7e7190f0819364fd0cea0dc3d668dSHA-256 32c8afa66c81e22bd07c051318291033984ff00e4160923c330b13f4f7b88a36SHA-256 1da2b1859f2b2fa74c2ef6a1f07dee2b3e490bb19f50e417a514016899286419SHA-256 ca066434f251b6e73c36294b5a7dc5dbb34c2f2da26cc61e9eb00e72e1b7cf1cSHA-256 8e09d537dcc689c2b012a531bcfe2cdb2ad8dd87cbbb94dcd6ee18505545ee28SHA-256 88c554f07d1e8364d04c32c42b97d5456893d07a8c0163346a0898c750c5aa1f