A matching JSON schema helps construct a payload. The complete original artifact, its canonical verification and its domain continuity establish what can be admitted.
01 · Existing canonical workflows
One proof system. Use its native tools.
Install the coordinated 129.0.0 packages. Choose the existing operation for your artifact and preserve its authority, custody, consent and causal requirements. These downloads add a reference surface to those packages.
Use assets.createProofObject for native Record → Seal issuance. Save its exact original through artifacts.download, then reopen the saved file with artifacts.verifyAndOpen. Inspect verifiedPayload.bytes only after enclosing verification succeeds.
Use createReceizNodeOfflineSealer or createReceizOfflineSealer with the packaged resources and admitted device custody. Verify saved output with verifyReceizOfflineSealedFile. Owner-bound sources require genuine identity admission; a supplied owner string cannot establish it.
Use receiz_artifact_verify for complete originals. The offline file workflow uses receiz_offline_seal_status, explicit device enrollment when needed, receiz_offline_seal_file and receiz_offline_verify_file. Discover the actual tools and input schemas exposed by the configured host.
receiz-proof-skill and receiz-offline-verifier-skill carry the same exact-byte, enclosing-artifact and continuity requirements. Skills guide the existing SDK and MCP operations; model text does not grant proof authority.
Generic sealing proves the supported file binding. Ownership, public disclosure, domain admission and any financial effect keep their existing independent requirements.
SDK release 129.0.0 retains schema generations v120, v122, v125, v126, v127. Their original names, $id, $schema and $ref values remain unchanged. Schema generations retain their original identities independently of the package release.
Keep the downloaded directory structure so relative references resolve. Canonical absolute IDs are retained as authored, including historical IDs shared by later generations. The manifest maps each file to its original ID; register the intended generation from local files in your schema tooling. Schema validation is developer shape checking.
Bankeiz’s public Ledger reader uses the same canonical v129 verifier and trusted roots. Its supported public view is an application publication scope beneath Receiz proof law. Valid JSON, a digest, a URL, a picture or a transported verdict cannot replace the enclosing original.
Original proof
Complete, verified source.
The reader first opens the complete original under the canonical pinned roots. A supported public proof also needs its genuine owner binding and carried Kai coordinate. Preserve object identity, payload, provenance, ownership history and unknown namespaces through the existing SDK rails.
Ledger statement
Existing native history.
The supported receiz.public-action-ledger.v1 disclosure must verify its existing native issuer, public-action-history scope and complete source continuity. Unsigned rows and arbitrary sealed JSON cannot become that writer’s history. Its financialAdmission remains false.
Public Ledger Crystal
Exact carried original.
The supported Ledger PNG carries a receiz.ledger_proof_bundle v2 transport with the exact original and bound artifact/payload digests. The reader extracts and verifies that original before reading its domain. Artwork, QR and metadata remain transport.
Private custody
Choose public material deliberately.
Private Identity Records, account or custody files, credentials and spendable Notes are outside this public input scope. Publication requires the owner’s separate explicit disclosure consent. Reading a proof establishes no new ownership, account credit, spending right or publication permission.
The private intelligence-source Memory Crystal uses the existing receiz_offline_crystal_append / receiz_offline_crystal_open workflow. It carries verified source and predecessor bytes with signer and KKS continuity. That private workflow does not itself create a public Ledger disclosure. Read the canonical MCP Crystal contract.
The distribution manifest records each schema’s package path, original ID, byte size and SHA-256 digest, the ZIP digest, and the installed SDK/MCP/AI Skills versions. It also identifies the exact package documentation referenced here. Hashes establish byte consistency; proof authority remains with canonical verified originals.
The existing complete native source archive remains available, including the Bankeiz public reader and source contract. These schema downloads contain schema definitions only; device enrollment, private signing material and native verification resources stay in their existing distributions and custody.