Documented release
v124.0.3
Reality Becomes Infrastructure
The Production Runtime for Verified Civilization
Release date 2026-08-25
Outcome
Outcome
V124.0.3 is the reconciliation that makes V124 operationally whole: immutable source authority, verified continuity, identity, ownership, authorship, offline proof, public witness, developer distribution, and AI-accessible capability now operate as one coherent runtime across people, systems, and time.
Changes
What changed
Source-first large-media execution
Record, Seal, Verify, Append, PBI authorship, and Export retain one immutable source File, hash and verify incrementally, append only a bounded proof trailer, and materialize whole bytes only at an explicit boundary that requires them.
Technical and authority boundary
Record, Seal, Verify, Append, PBI authorship, and Export retain one immutable source File, hash and verify incrementally, append only a bounded proof trailer, and materialize whole bytes only at an explicit boundary that requires them.
- Why
- The reconciliation proves a broader release law. Compiler casts, UI labels, transport convenience, memory ownership, QR composition, and loading policy become constitutional mechanics when they cross a proof boundary. Each must preserve the stronger source and name its exact uncertainty. That is how verified reality becomes durable infrastructure rather than a claim that survives only inside one application.
- Capability enabled
- Record, Seal, Verify, Append, PBI authorship, and Export retain one immutable source File, hash and verify incrementally, append only a bounded proof trailer, and materialize whole bytes only at an explicit boundary that requires them.
- Compatibility
- The v124.0.3 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.3 migration record remains the exact adoption boundary for this outcome.
One canonical verifier law
Workbench, /seal, /verify, Offline Studio, the standalone Offline Verifier, and SDK projection consume the same completed canonical verification result. Resource failure remains an execution failure and can never be presented as an invalid-proof verdict.
Technical and authority boundary
Workbench, /seal, /verify, Offline Studio, the standalone Offline Verifier, and SDK projection consume the same completed canonical verification result. Resource failure remains an execution failure and can never be presented as an invalid-proof verdict.
- Why
- The reconciliation proves a broader release law. Compiler casts, UI labels, transport convenience, memory ownership, QR composition, and loading policy become constitutional mechanics when they cross a proof boundary. Each must preserve the stronger source and name its exact uncertainty. That is how verified reality becomes durable infrastructure rather than a claim that survives only inside one application.
- Capability enabled
- Workbench, /seal, /verify, Offline Studio, the standalone Offline Verifier, and SDK projection consume the same completed canonical verification result. Resource failure remains an execution failure and can never be presented as an invalid-proof verdict.
- Compatibility
- The v124.0.3 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.3 migration record remains the exact adoption boundary for this outcome.
Truthful typed projection
Generic streaming-verifier bundle data is validated before it becomes ReceizProofBundle. The unsafe reseal assertion and the incompatible Workbench projection boundary are removed; a representation cannot be promoted into stronger proof truth by a TypeScript cast.
Technical and authority boundary
Generic streaming-verifier bundle data is validated before it becomes ReceizProofBundle. The unsafe reseal assertion and the incompatible Workbench projection boundary are removed; a representation cannot be promoted into stronger proof truth by a TypeScript cast.
- Why
- The reconciliation proves a broader release law. Compiler casts, UI labels, transport convenience, memory ownership, QR composition, and loading policy become constitutional mechanics when they cross a proof boundary. Each must preserve the stronger source and name its exact uncertainty. That is how verified reality becomes durable infrastructure rather than a claim that survives only inside one application.
- Capability enabled
- Generic streaming-verifier bundle data is validated before it becomes ReceizProofBundle. The unsafe reseal assertion and the incompatible Workbench projection boundary are removed; a representation cannot be promoted into stronger proof truth by a TypeScript cast.
- Compatibility
- The v124.0.3 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.3 migration record remains the exact adoption boundary for this outcome.
Canonical PBI authorship succession
PBI signing appends authorship after the exact verified predecessor without transferring ownership. The descendant is admitted only after canonical verification, including Signature V4 payload binding and ownership-continuity checks.
Technical and authority boundary
PBI signing appends authorship after the exact verified predecessor without transferring ownership. The descendant is admitted only after canonical verification, including Signature V4 payload binding and ownership-continuity checks.
- Why
- The reconciliation proves a broader release law. Compiler casts, UI labels, transport convenience, memory ownership, QR composition, and loading policy become constitutional mechanics when they cross a proof boundary. Each must preserve the stronger source and name its exact uncertainty. That is how verified reality becomes durable infrastructure rather than a claim that survives only inside one application.
- Capability enabled
- PBI signing appends authorship after the exact verified predecessor without transferring ownership. The descendant is admitted only after canonical verification, including Signature V4 payload binding and ownership-continuity checks.
- Compatibility
- The v124.0.3 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.3 migration record remains the exact adoption boundary for this outcome.
Exact PBI descendant export
Workbench exports the exact canonically verified PBI descendant. Optional badges or previews may render beside that proof object, but no signed-image representation may replace its bytes or inherit continuity from a different artifact basis.
Technical and authority boundary
Workbench exports the exact canonically verified PBI descendant. Optional badges or previews may render beside that proof object, but no signed-image representation may replace its bytes or inherit continuity from a different artifact basis.
- Why
- The reconciliation proves a broader release law. Compiler casts, UI labels, transport convenience, memory ownership, QR composition, and loading policy become constitutional mechanics when they cross a proof boundary. Each must preserve the stronger source and name its exact uncertainty. That is how verified reality becomes durable infrastructure rather than a claim that survives only inside one application.
- Capability enabled
- Workbench exports the exact canonically verified PBI descendant. Optional badges or previews may render beside that proof object, but no signed-image representation may replace its bytes or inherit continuity from a different artifact basis.
- Compatibility
- The v124.0.3 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.3 migration record remains the exact adoption boundary for this outcome.
Completed-proof Offline Studio QR
Offline Studio projects the completed compact ?c= proof URL as a clickable 92×92 QR after canonical success. It never substitutes the weaker ?ms= historical lookup and never rewrites the recorded Moment source to embed a future-derived URL.
Technical and authority boundary
Offline Studio projects the completed compact ?c= proof URL as a clickable 92×92 QR after canonical success. It never substitutes the weaker ?ms= historical lookup and never rewrites the recorded Moment source to embed a future-derived URL.
- Why
- The reconciliation proves a broader release law. Compiler casts, UI labels, transport convenience, memory ownership, QR composition, and loading policy become constitutional mechanics when they cross a proof boundary. Each must preserve the stronger source and name its exact uncertainty. That is how verified reality becomes durable infrastructure rather than a claim that survives only inside one application.
- Capability enabled
- Offline Studio projects the completed compact ?c= proof URL as a clickable 92×92 QR after canonical success. It never substitutes the weaker ?ms= historical lookup and never rewrites the recorded Moment source to embed a future-derived URL.
- Compatibility
- The v124.0.3 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.3 migration record remains the exact adoption boundary for this outcome.
Direct /v proof classification
A valid carried ?c= bundle verifies as Proof. Historical coordinate lookup remains available for historical receipts, but cannot relabel a completed self-carrying proof URL.
Technical and authority boundary
A valid carried ?c= bundle verifies as Proof. Historical coordinate lookup remains available for historical receipts, but cannot relabel a completed self-carrying proof URL.
- Why
- The reconciliation proves a broader release law. Compiler casts, UI labels, transport convenience, memory ownership, QR composition, and loading policy become constitutional mechanics when they cross a proof boundary. Each must preserve the stronger source and name its exact uncertainty. That is how verified reality becomes durable infrastructure rather than a claim that survives only inside one application.
- Capability enabled
- A valid carried ?c= bundle verifies as Proof. Historical coordinate lookup remains available for historical receipts, but cannot relabel a completed self-carrying proof URL.
- Compatibility
- The v124.0.3 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.3 migration record remains the exact adoption boundary for this outcome.
Settled Profile with bounded media work
The complete verified showcase remains held; the 24/18 monotonic presentation window and every admitted card shell remain unchanged. Grid cover loading is viewport-bounded beneath those shells, while one-column feature media stays eager, so secondary image requests no longer hold the cold navigation indicator open.
Technical and authority boundary
The complete verified showcase remains held; the 24/18 monotonic presentation window and every admitted card shell remain unchanged. Grid cover loading is viewport-bounded beneath those shells, while one-column feature media stays eager, so secondary image requests no longer hold the cold navigation indicator open.
- Why
- The reconciliation proves a broader release law. Compiler casts, UI labels, transport convenience, memory ownership, QR composition, and loading policy become constitutional mechanics when they cross a proof boundary. Each must preserve the stronger source and name its exact uncertainty. That is how verified reality becomes durable infrastructure rather than a claim that survives only inside one application.
- Capability enabled
- The complete verified showcase remains held; the 24/18 monotonic presentation window and every admitted card shell remain unchanged. Grid cover loading is viewport-bounded beneath those shells, while one-column feature media stays eager, so secondary image requests no longer hold the cold navigation indicator open.
- Compatibility
- The v124.0.3 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.3 migration record remains the exact adoption boundary for this outcome.
Playable Profile continuity preserved
The working image and audio global-sync paths are unchanged. Native image, native video, uploaded video, and text-only Recorded Moments retain their exact proof identity; video playback remains an explicit Profile Composer/Profile Showcase presentation boundary beneath the proof object.
Technical and authority boundary
The working image and audio global-sync paths are unchanged. Native image, native video, uploaded video, and text-only Recorded Moments retain their exact proof identity; video playback remains an explicit Profile Composer/Profile Showcase presentation boundary beneath the proof object.
- Why
- The reconciliation proves a broader release law. Compiler casts, UI labels, transport convenience, memory ownership, QR composition, and loading policy become constitutional mechanics when they cross a proof boundary. Each must preserve the stronger source and name its exact uncertainty. That is how verified reality becomes durable infrastructure rather than a claim that survives only inside one application.
- Capability enabled
- The working image and audio global-sync paths are unchanged. Native image, native video, uploaded video, and text-only Recorded Moments retain their exact proof identity; video playback remains an explicit Profile Composer/Profile Showcase presentation boundary beneath the proof object.
- Compatibility
- The v124.0.3 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.3 migration record remains the exact adoption boundary for this outcome.
Native-image URL continuity restored
Native-capture images reopen their exact payload from the self-contained carried proof URL after the composer-owned blob is released. The bounded-video held-source exception remains video-only, so this correction does not alter working video or image/audio global sync.
Technical and authority boundary
Native-capture images reopen their exact payload from the self-contained carried proof URL after the composer-owned blob is released. The bounded-video held-source exception remains video-only, so this correction does not alter working video or image/audio global sync.
- Why
- The reconciliation proves a broader release law. Compiler casts, UI labels, transport convenience, memory ownership, QR composition, and loading policy become constitutional mechanics when they cross a proof boundary. Each must preserve the stronger source and name its exact uncertainty. That is how verified reality becomes durable infrastructure rather than a claim that survives only inside one application.
- Capability enabled
- Native-capture images reopen their exact payload from the self-contained carried proof URL after the composer-owned blob is released. The bounded-video held-source exception remains video-only, so this correction does not alter working video or image/audio global sync.
- Compatibility
- The v124.0.3 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.3 migration record remains the exact adoption boundary for this outcome.
Showcase membership and owner signing access reconciled
Identity Seal and Identity Record stay identity artifacts unless an actual showcase publication admits them; local session fallback no longer fabricates owner-only posts. A global post hands its authenticated owner profile to the already-open profile surface, so the existing signature control is present immediately instead of waiting for refresh to replace a logged-out/public viewer projection. Signing mechanics are unchanged.
Technical and authority boundary
Identity Seal and Identity Record stay identity artifacts unless an actual showcase publication admits them; local session fallback no longer fabricates owner-only posts. A global post hands its authenticated owner profile to the already-open profile surface, so the existing signature control is present immediately instead of waiting for refresh to replace a logged-out/public viewer projection. Signing mechanics are unchanged.
- Why
- The reconciliation proves a broader release law. Compiler casts, UI labels, transport convenience, memory ownership, QR composition, and loading policy become constitutional mechanics when they cross a proof boundary. Each must preserve the stronger source and name its exact uncertainty. That is how verified reality becomes durable infrastructure rather than a claim that survives only inside one application.
- Capability enabled
- Identity Seal and Identity Record stay identity artifacts unless an actual showcase publication admits them; local session fallback no longer fabricates owner-only posts. A global post hands its authenticated owner profile to the already-open profile surface, so the existing signature control is present immediately instead of waiting for refresh to replace a logged-out/public viewer projection. Signing mechanics are unchanged.
- Compatibility
- The v124.0.3 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.3 migration record remains the exact adoption boundary for this outcome.
Coordinated release identity
Application, @receiz/sdk, @receiz/mcp-server, and @receiz/ai-skills align at 124.0.3 while RECEIZRULESETVERSION and the V124 registry remain 124.0.0.
Technical and authority boundary
Application, @receiz/sdk, @receiz/mcp-server, and @receiz/ai-skills align at 124.0.3 while RECEIZRULESETVERSION and the V124 registry remain 124.0.0.
- Why
- The reconciliation proves a broader release law. Compiler casts, UI labels, transport convenience, memory ownership, QR composition, and loading policy become constitutional mechanics when they cross a proof boundary. Each must preserve the stronger source and name its exact uncertainty. That is how verified reality becomes durable infrastructure rather than a claim that survives only inside one application.
- Capability enabled
- Application, @receiz/sdk, @receiz/mcp-server, and @receiz/ai-skills align at 124.0.3 while RECEIZRULESETVERSION and the V124 registry remain 124.0.0.
- Compatibility
- The v124.0.3 compatibility record remains the exact boundary for this outcome.
- Migration
- The v124.0.3 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
The reconciliation proves a broader release law. Compiler casts, UI labels, transport convenience, memory ownership, QR composition, and loading policy become constitutional mechanics when they cross a proof boundary. Each must preserve the stronger source and name its exact uncertainty. That is how verified reality becomes durable infrastructure rather than a claim that survives only inside one application.
Available outcomes
Capabilities now available
Source-first large-media execution
Record, Seal, Verify, Append, PBI authorship, and Export retain one immutable source File, hash and verify incrementally, append only a bounded proof trailer, and materialize whole bytes only at an explicit boundary that requires them.
One canonical verifier law
Workbench, /seal, /verify, Offline Studio, the standalone Offline Verifier, and SDK projection consume the same completed canonical verification result. Resource failure remains an execution failure and can never be presented as an invalid-proof verdict.
Truthful typed projection
Generic streaming-verifier bundle data is validated before it becomes ReceizProofBundle. The unsafe reseal assertion and the incompatible Workbench projection boundary are removed; a representation cannot be promoted into stronger proof truth by a TypeScript cast.
Canonical PBI authorship succession
PBI signing appends authorship after the exact verified predecessor without transferring ownership. The descendant is admitted only after canonical verification, including Signature V4 payload binding and ownership-continuity checks.
Exact PBI descendant export
Workbench exports the exact canonically verified PBI descendant. Optional badges or previews may render beside that proof object, but no signed-image representation may replace its bytes or inherit continuity from a different artifact basis.
Completed-proof Offline Studio QR
Offline Studio projects the completed compact ?c= proof URL as a clickable 92×92 QR after canonical success. It never substitutes the weaker ?ms= historical lookup and never rewrites the recorded Moment source to embed a future-derived URL.
Direct /v proof classification
A valid carried ?c= bundle verifies as Proof. Historical coordinate lookup remains available for historical receipts, but cannot relabel a completed self-carrying proof URL.
Settled Profile with bounded media work
The complete verified showcase remains held; the 24/18 monotonic presentation window and every admitted card shell remain unchanged. Grid cover loading is viewport-bounded beneath those shells, while one-column feature media stays eager, so secondary image requests no longer hold the cold navigation indicator open.
Playable Profile continuity preserved
The working image and audio global-sync paths are unchanged. Native image, native video, uploaded video, and text-only Recorded Moments retain their exact proof identity; video playback remains an explicit Profile Composer/Profile Showcase presentation boundary beneath the proof object.
Native-image URL continuity restored
Native-capture images reopen their exact payload from the self-contained carried proof URL after the composer-owned blob is released. The bounded-video held-source exception remains video-only, so this correction does not alter working video or image/audio global sync.
Showcase membership and owner signing access reconciled
Identity Seal and Identity Record stay identity artifacts unless an actual showcase publication admits them; local session fallback no longer fabricates owner-only posts. A global post hands its authenticated owner profile to the already-open profile surface, so the existing signature control is present immediately instead of waiting for refresh to replace a logged-out/public viewer projection. Signing mechanics are unchanged.
Coordinated release identity
Application, @receiz/sdk, @receiz/mcp-server, and @receiz/ai-skills align at 124.0.3 while RECEIZRULESETVERSION and the V124 registry remain 124.0.0.
Primitive boundary
Primitives affected
- proof
- identity
- ownership
- provenance
- media
- transfer
- verification
- public-witness
- local-truth
- continuity
- sealed-artifact
- governance
Compatibility
Compatibility
Coordinated package identity
Application, @receiz/ai-skills, @receiz/sdk, @receiz/mcp-server, and the constitutional verifier are prepared at 124.0.3; publication is not claimed by the manifest.
This exact v124.0.3 compatibility boundary remains binding.
Application compatibility
Application and SDK compatibility remains exactly >=124.0.0 <125.0.0.
This exact v124.0.3 compatibility boundary remains binding.
Constitutional registry
V124.0.3 inherits the byte-identical 124.0.0 registry at digest d02429151b0bcebdaeb89485792e377afc55130f9a25e07982c1c88221314247; no V124.0.3 registry is created.
This exact v124.0.3 compatibility boundary remains binding.
Ruleset identity
RECEIZ_RULESET_VERSION remains 124.0.0; package identity 124.0.3 does not reinterpret constitutional law.
This exact v124.0.3 compatibility boundary remains binding.
Historical proof objects
Historical sealed proof-object bytes, schemas, signatures, Groth16 verification, payload binding, ownership continuity, append law, and verification semantics remain unchanged and require no reseal.
This exact v124.0.3 compatibility boundary remains binding.
Exact-byte verification
SDK, Workbench, /verify, Offline Studio, and standalone verification reject current-basis/native-ownership drift with the same law.
This exact v124.0.3 compatibility boundary remains binding.
PBI authorship
Existing valid PBI descendants remain valid. New Workbench exports release the exact descendant and add no export-only verifier exception or ownership transfer.
This exact v124.0.3 compatibility boundary remains binding.
Fully inline material
rma2 remains a fully inline exact proof-object carrier for image, audio, video, PDF, text, and binary material.
This exact v124.0.3 compatibility boundary remains binding.
Large-material transport
rmc1 remains a bounded head over exact ordered committed segments; a fresh viewer retrieves those segments before complete proof-object verification and playback.
This exact v124.0.3 compatibility boundary remains binding.
Offline verification
Held artifacts verify from their own exact bytes without account, session, database, or network authority.
This exact v124.0.3 compatibility boundary remains binding.
Compact proof links
Existing rpb1 and rpb2 meanings remain stable. A carried ?c= proof remains additive and never replaces an existing /v proof coordinate.
This exact v124.0.3 compatibility boundary remains binding.
Profile playback
Working image/audio publication is unchanged. Video playback remains an explicit presentation beneath the exact admitted Profile proof object.
This exact v124.0.3 compatibility boundary remains binding.
Public QR
Offline Studio carries its completed compact ?c= proof URL in a clickable 92×92 QR without changing recorded source bytes.
This exact v124.0.3 compatibility boundary remains binding.
V125 boundary
Closed external-source-free reconstruction for arbitrarily large files remains a V125 Kai-Turah/HRC objective and is not complete in V124.0.3.
This exact v124.0.3 compatibility boundary remains binding.
Migration
Migration
Required: false
The Production Runtime for Verified Civilization. No migrations are required. V124.0.3 reconciles mechanics beneath constitutional ruleset 124.0.0; it does not rewrite sealed proof objects or create a new authority.
- No database schema migration.
- No proof-object rewrite, normalization, reseal, or artifact backfill.
- No identity reissue or PBI reenrollment.
- No ownership-history or append-history rewrite.
- No registry, signature, Groth16, payload-binding, operation-name, stable schema, rpb1, rpb2, rma2, or rmc1 semantic change.
- No network, account, session, server, database, or package authority added to offline verification.
Qualification
Conformance
Receiz Docs consumes the independently published 124.0.3 package pins while its frozen Workbench verifier remains synchronized to the exact canonical V124.0.3 SDK runtime.
Passed · Receiz Docs consumes the independently published 124.0.3 package pins while its frozen Workbench verifier remains synchronized to the exact canonical V124.0.3 SDK runtime.
Full local release freeze, main build, Docs build, and governance controls verified for the final tree.
Passed · Full local release freeze, main build, Docs build, and governance controls verified for the final tree.
Control boundary
Governance
- Verification
- Passed
- Declared change class
- No separate classification record
- Release approval
- No separate approval record
- Risk owner
- No separate assignment recorded
Package publication, production deployment, and production smoke are independently confirmed; signed release attestation remains absent and is not inferred from the live release.
Registry boundary
Registry
- Version
- 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
- Change kinds
- correction · capability · 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 3ebfc12a23c5c60e0d928f3d0409edc90108df25b285991f3ebc77390831e2f2. Source-family inventory: complete.
SHA-256 4e781346d3623ec0f40dac7687094fbb4d7e75ddb4ce77f2b202e3bbefb2b55fSHA-256 c0a91d163dfd0a160decdea18d4b86e6407ff8c65676b73b0da36ed9f70e236eSHA-256 63e1f31f10e4893a9e2e119d7777c077db99d3f633083cf089042f239c999746SHA-256 e8e2a1693cd5cbaeae52863efa1f1ddccf8297db1ad6345245f95d28007ebd3fSHA-256 537e8c367bae64bda9625427dc285b6155e908260f6e0d518c97d8bb540e345cSHA-256 18e037ed13820d20ecdfe119b5107a45698ae15ebf6cee9b921f1480454d51caSHA-256 56b363162a02ac109f20eca660b78522b3620313583b1390fd39dff2e5995feaSHA-256 7b6f8d777dc71238855ca4495e8b92c4ab8e133407bf51848333c48afeaccdf3SHA-256 f620fff2829e20239821b0cfe1be298a98b2af73edf3fe0702d9094a64e50918SHA-256 3507a361a367766e832497085109a67340fb76c571a72479e94f724f277bb3d9SHA-256 acd540dab3f1885d4a2c97b03166b1418168daebb1ee259ca4f64c47fd932125SHA-256 5160adc616c97dd55ccbbd0bdb3f01d046fd812a904120df8f4364e8b08134e5SHA-256 7050b1af7465b3378e0f22602e26178db1f31ba5500bd0ff1f999b5ec6fa20b5SHA-256 697066cbe4fc0f4f3ece2872be79172d6e3ac6d223d2797c5e05d2c2b863b79eSHA-256 44bc4fc57128b2742c9c78d6d1fdeb12b9b26099db1a87ba04139cc77be83318SHA-256 4793450794b0bd9f8c67e4c81f492c03afa9b87ab9cd896e170d31fe2142d584SHA-256 65f25f8ce3771691188877e1789208101c524749a8ffcf622fc2dbba7e0396dcSHA-256 1e04bb42c037358d7966885f18cd99a7a189c60829afc72f108cfbaa89fc5cafSHA-256 9691e75db8a52218610546a616431af231bb2dece9d8424ed54f77eecc346536SHA-256 b0317267850d9d19581dae5bbea72ba826f2fb37eccb5d93f4a11c2adae4dc9c