SDKVerify proof objects and Offline Note custody evidence
import {
createReceizClient,
verifyReceizOfflineNoteReceivingCustodyCommitment,
verifyReceizOfflineNoteWebAuthnConsumptionReceipt,
} from "@receiz/sdk";
const receiz = createReceizClient();
const artifact = await receiz.verification.verifyArtifact(noteFile);
if (artifact.status !== "verified-artifact") throw new Error(artifact.status);
const receiver = await verifyReceizOfflineNoteReceivingCustodyCommitment(receivingCustody);
const consumption = await verifyReceizOfflineNoteWebAuthnConsumptionReceipt(receipt);
For genesis, the verified receiz.account.state.v3 Reserve source, its local debit successor, and the equal whole-value held-bound Note successor verify as one composed issuance. For Send, the enclosing Note verifies first; the anonymous receiving-custody commitment and exact one-use consumption receipt then verify as subordinate transition evidence.
The SDK verifies exact structures and evidence. It does not qualify a platform from caller-shaped JSON, deduct Reserve through a server response, consume a Note head by itself, or outrank the account/Identity proof, sealed Note, and canonical history.CLIInspect a Note record without pretending to Send it
npx @receiz/sdk inspect ./settlement-note.receiz.json
A structured local inspection result and process exit class. The current CLI exposes no Offline Note qualification, activation, consumption, or Send command.
CLI inspection cannot create custody, activate a successor, consume a head, or complete Settlement. Those operations stay inside the qualified adapter and canonical Note transition.HTTPUse HTTP only beneath Offline Note Settlement
POST /api/document-verify
Content-Type: multipart/form-data
file=<complete sealed proof object>
A network verification response beneath the locally held Note proof object. Publication may later distribute a verified ownership chain; neither call creates or completes the offline transfer.
HTTP never supplies the Reserve source, releases a genesis, qualifies custody, selects the lawful head, consumes transition authority, or makes local Settlement valid. Server arrival order is not Note authority.MCPVerify the enclosing Note through MCP
receiz_artifact_verify({ artifactBase64, filename, mimeType })
SDK verification status, complete artifact identity, digests, continuity, mcpAuthority false, and strongerTruth sealed-receiz-proof-object. No dedicated MCP Offline Send authority is published.
MCP authority: false. MCP may verify the enclosing Note and coordinate declared artifact mechanics, but cannot qualify custody, manufacture a one-use receipt, activate a successor, or choose Settlement truth.AIApply the Offline Note verification boundary
Use @receiz/ai-skills/receiz-offline-verifier-skill. For genesis, verify receiz.account.state.v3, the local Reserve-debit successor, and the equal whole-value held-bound Note successor. For Send, verify the enclosing Note first; then verify its exact predecessor, whole value, anonymous next-custody commitment, Kai order, consumption receipt, and canonical successor. Report publication as optional coordination only.
An evidence-bound Note verification record that names the exact executed verifier results and refuses to infer qualification, custody, Settlement, or ownership from model text.
AI skill authority: false. The agent may guide inspection and verification; it cannot create irreversible custody, consume a head, activate a successor, or replace the sealed Note's causal chain. MCP authority: false. AI skill authority: false. Their output never replaces the sealed proof object.