Documented release
v109.0.0
Coordinated Local-Offline Developer Release
Release date 2026-07-18
Outcome
Outcome
MCP artifact tools compose the same SDK verifier and remain orchestration beneath sealed artifact truth.
Changes
What changed
receiz.verification.verifyArtifact(file) verifies complete .receizbundle proof objects locally from their bytes
receiz.verification.verifyArtifact(file) verifies complete .receizbundle proof objects locally from their bytes.
Technical and authority boundary
receiz.verification.verifyArtifact(file) verifies complete .receizbundle proof objects locally from their bytes.
- Why
- MCP artifact tools compose the same SDK verifier and remain orchestration beneath sealed artifact truth.
- Capability enabled
- receiz.verification.verifyArtifact(file) verifies complete .receizbundle proof objects locally from their bytes.
- Compatibility
- The v109.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v109.0.0 migration record remains the exact adoption boundary for this outcome.
receiz.artifacts.verifyAndOpen(file) verifies before extraction and returns the enclosing artifact separately…
receiz.artifacts.verifyAndOpen(file) verifies before extraction and returns the enclosing artifact separately from the verified payload.
Technical and authority boundary
receiz.artifacts.verifyAndOpen(file) verifies before extraction and returns the enclosing artifact separately from the verified payload.
- Why
- MCP artifact tools compose the same SDK verifier and remain orchestration beneath sealed artifact truth.
- Capability enabled
- receiz.artifacts.verifyAndOpen(file) verifies before extraction and returns the enclosing artifact separately from the verified payload.
- Compatibility
- The v109.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v109.0.0 migration record remains the exact adoption boundary for this outcome.
Public verification/opening performs zero network calls and requires no access…
Public verification/opening performs zero network calls and requires no access token, cookie, database, registry lookup, or running Receiz.com process.
Technical and authority boundary
Public verification/opening performs zero network calls and requires no access token, cookie, database, registry lookup, or running Receiz.com process.
- Why
- MCP artifact tools compose the same SDK verifier and remain orchestration beneath sealed artifact truth.
- Capability enabled
- Public verification/opening performs zero network calls and requires no access token, cookie, database, registry lookup, or running Receiz.com process.
- Compatibility
- The v109.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v109.0.0 migration record remains the exact adoption boundary for this outcome.
Signature V4 roots, the document-seal Groth16 verification key, and the…
Signature V4 roots, the document-seal Groth16 verification key, and the snarkjs runtime are packaged with the SDK.
Technical and authority boundary
Signature V4 roots, the document-seal Groth16 verification key, and the snarkjs runtime are packaged with the SDK.
- Why
- MCP artifact tools compose the same SDK verifier and remain orchestration beneath sealed artifact truth.
- Capability enabled
- Signature V4 roots, the document-seal Groth16 verification key, and the snarkjs runtime are packaged with the SDK.
- Compatibility
- The v109.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v109.0.0 migration record remains the exact adoption boundary for this outcome.
One-byte mutation, malformed carrier, artifact-binding mismatch, Signature V4 failure, Groth16…
One-byte mutation, malformed carrier, artifact-binding mismatch, Signature V4 failure, Groth16 failure, and invalid portable continuity fail closed.
Technical and authority boundary
One-byte mutation, malformed carrier, artifact-binding mismatch, Signature V4 failure, Groth16 failure, and invalid portable continuity fail closed.
- Why
- MCP artifact tools compose the same SDK verifier and remain orchestration beneath sealed artifact truth.
- Capability enabled
- One-byte mutation, malformed carrier, artifact-binding mismatch, Signature V4 failure, Groth16 failure, and invalid portable continuity fail closed.
- Compatibility
- The v109.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v109.0.0 migration record remains the exact adoption boundary for this outcome.
MCP artifact tools compose the same SDK verifier and remain…
MCP artifact tools compose the same SDK verifier and remain orchestration beneath sealed artifact truth.
Technical and authority boundary
MCP artifact tools compose the same SDK verifier and remain orchestration beneath sealed artifact truth.
- Why
- MCP artifact tools compose the same SDK verifier and remain orchestration beneath sealed artifact truth.
- Capability enabled
- MCP artifact tools compose the same SDK verifier and remain orchestration beneath sealed artifact truth.
- Compatibility
- The v109.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v109.0.0 migration record remains the exact adoption boundary for this outcome.
Artifact-related AI skills require Network calls during verification
Artifact-related AI skills require Network calls during verification: 0 and a recorded local-verifier result before a production-ready claim.
Technical and authority boundary
Artifact-related AI skills require Network calls during verification: 0 and a recorded local-verifier result before a production-ready claim.
- Why
- MCP artifact tools compose the same SDK verifier and remain orchestration beneath sealed artifact truth.
- Capability enabled
- Artifact-related AI skills require Network calls during verification: 0 and a recorded local-verifier result before a production-ready claim.
- Compatibility
- The v109.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v109.0.0 migration record remains the exact adoption boundary for this outcome.
ARTIFACT-011 makes zero-network complete-artifact verification constitutional release law
ARTIFACT-011 makes zero-network complete-artifact verification constitutional release law.
Technical and authority boundary
ARTIFACT-011 makes zero-network complete-artifact verification constitutional release law.
- Why
- MCP artifact tools compose the same SDK verifier and remain orchestration beneath sealed artifact truth.
- Capability enabled
- ARTIFACT-011 makes zero-network complete-artifact verification constitutional release law.
- Compatibility
- The v109.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v109.0.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
MCP artifact tools compose the same SDK verifier and remain orchestration beneath sealed artifact truth.
Available outcomes
Capabilities now available
receiz.verification.verifyArtifact(file) verifies complete .receizbundle proof objects locally from their bytes
receiz.verification.verifyArtifact(file) verifies complete .receizbundle proof objects locally from their bytes.
receiz.artifacts.verifyAndOpen(file) verifies before extraction and returns the enclosing artifact separately…
receiz.artifacts.verifyAndOpen(file) verifies before extraction and returns the enclosing artifact separately from the verified payload.
Public verification/opening performs zero network calls and requires no access…
Public verification/opening performs zero network calls and requires no access token, cookie, database, registry lookup, or running Receiz.com process.
Signature V4 roots, the document-seal Groth16 verification key, and the…
Signature V4 roots, the document-seal Groth16 verification key, and the snarkjs runtime are packaged with the SDK.
One-byte mutation, malformed carrier, artifact-binding mismatch, Signature V4 failure, Groth16…
One-byte mutation, malformed carrier, artifact-binding mismatch, Signature V4 failure, Groth16 failure, and invalid portable continuity fail closed.
MCP artifact tools compose the same SDK verifier and remain…
MCP artifact tools compose the same SDK verifier and remain orchestration beneath sealed artifact truth.
Artifact-related AI skills require Network calls during verification
Artifact-related AI skills require Network calls during verification: 0 and a recorded local-verifier result before a production-ready claim.
ARTIFACT-011 makes zero-network complete-artifact verification constitutional release law
ARTIFACT-011 makes zero-network complete-artifact verification constitutional release law.
Primitive boundary
Primitives affected
- proof
- provenance
- verification
- public-witness
- local-truth
- continuity
- sealed-artifact
Compatibility
Compatibility
Archive compatibility evidence boundary
No dedicated compatibility record is bound to this projection.
Treat compatibility as unknown; version or date proximity is not evidence.
Migration
Migration
Required: unknown
No explicit migration source is bound; no migration is inferred from dates.
Qualification
Conformance
SDK typecheck and 120-test package suite.
Passed · SDK typecheck and 120-test package suite.
MCP typecheck and 32-test package suite.
Passed · MCP typecheck and 32-test package suite.
Full release-freeze gate; the isolated v108 profile-database fixture was scope-skipped because every protected profile/database source is byte-identical and no live database may be used for its mutating fixture.
Passed · Full release-freeze gate; the isolated v108 profile-database fixture was scope-skipped because every protected profile/database source is byte-identical and no live database may be used for its mutating fixture.
Governance controls, evidence, and artifact-signature verification.
Passed · Governance controls, evidence, and artifact-signature verification.
Control boundary
Governance
- Verification
- Passed
- Declared change class
- No separate classification record
- Release approval
- No separate approval record
- Risk owner
- No separate assignment recorded
Governance verification passed against the exact checked release evidence bound below.
No separate release approval reference or risk-owner assignment is inferred from conformance evidence.
Registry boundary
Registry
- Version
- 109.0.0
- Digest
17f76b37c9fcd46f710239b5c1660b03cc34ec64bed30d1cc45c18d5d40eab70- Predecessor
126ca9283fee4ef4c398dbcb958e861cbea191724fdab8eb08df55ff0c14bb79
Archive projection
Audience, domain, and change-kind facets
- Audiences
- developers · businesses · creators · institutions · people
- Domains
- proof · provenance · verification · public-witness · local-truth · continuity · sealed-artifact
- Change kinds
- capability
Independent dimensions
Release boundary status
- Repository release
- Documented
- Git tag
- Present
- Package publication
- Not Performed
- Deployment
- Not Performed
- Production smoke
- Unknown
- Signed attestation
- Absent
Exact source bytes
Provenance
This Academy record is a projection beneath its sources. Record SHA-256 05d6984120289883e8c1ed05b26ee876c44c81b3a154a6021d00b22f3c7dcd81. Source-family inventory: complete.
SHA-256 c59b40a8d956196db87e1ef4791df2621f8b035234ad4a204d8ca4b9ea19ebffSHA-256 4c87fc9d8fc2be9abfeb00f2292c950946ed4e0f4126cc38e288dff987dc5739SHA-256 4fa1101a5e3ae7078db0bc27ebbcc38bce471351122cf0d6a9eb15fbfa742468SHA-256 07b6f84308326718abd6cb156923f248e1ef1047c7271aecd764c72e9f28b87eSHA-256 74b4dea2291db16513c59573cde23acc9cf2fd8cb4cbec3403105f6b26d5e0cdSHA-256 62c28a5b4b06967a266b37f63d0dfcabb18a453aef1184bd375ea3f85bbeee0cSHA-256 08b236ba5535c9253304c60fc466e82fe236d255b57c1b01a8cc35b083ee78bbSHA-256 794cc5e97f5e6532bf513fe09b1cef89e345e90417a34741e24dc113ece627d4SHA-256 48bed93530dc335c340eedc984b819332e44b15a442c69b87bd315a6be20a19e