Operations and receipts

Solved outcome

What this enables

Separate verified artifact truth, operation admission, atomic acceptance, and report-only receipts without collapsing them.

Installed identity

@receiz/sdk

Version

129.0.0

Package SHA-256

53337aab33882e945d4243802b8013e3af523644a329c71a64f669a6360c8629

Record source

node_modules/@receiz/sdk/dist/index.d.ts

Exact form

Signature or request

verify exact bytes → admit profile → plan → seal and stage → independently resolve → atomically commit → inspect receipt

Stable recovery

Failures

Permanent anchor · #operations-receipts-operation-order

Operation order

Verify exact artifact bytes, admit the verified result in the same runtime, plan with verified history and actor evidence, seal and durably stage, independently resolve staged bytes, atomically commit, then inspect the receipt.

Permanent anchor · #operations-receipts-admission

Admission

Admission classifies a runtime-custodied verified artifact against the declared profile. It performs no operation authorization and cannot be reconstructed from caller-shaped JSON.

Permanent anchor · #operations-receipts-planning

Planning

Planning binds canonical event, expected verified-history head, commit domain, verified actor, registry law, and idempotency identity. A plan performs zero writes.

Permanent anchor · #operations-receipts-staging

Staging

Seal the plan-bound candidate and stage immutable neutral bytes without advancing the accepted head. The staging reference is a locator, not proof authority.

Permanent anchor · #operations-receipts-atomic-acceptance

Atomic acceptance

Commit independently resolves and reverifies the staged candidate inside the named domain, then advances the head atomically or returns a stable failure with zero accepted writes.

Permanent anchor · #operations-receipts-receipt-anatomy

Receipt anatomy

A receipt reports commit domain, actor, resource, operation, plan, capability, transition, artifact, prior head, accepted head, command, and idempotency digests. It cannot re-enter authority-bearing APIs.

Permanent anchor · #operations-receipts-end-to-end-example

End-to-end example

The universal example stops at verified sealed bytes and download evidence. Admission, plan, stage, and commit are later operations with their own exact authority inputs.

Copyable path

Authenticated SDK issuance → Verify → inspect receipt

import { createReceizClient } from "@receiz/sdk";

// Begin with the complete proof object already held by the person or runtime.
const encoded = process.env.RECEIZ_ARTIFACT_BASE64;
if (!encoded) throw new Error("RECEIZ_ARTIFACT_BASE64 is required");
const artifactBytes = Uint8Array.from(Buffer.from(encoded, "base64"));

// Local verification is account-free and precedes every transport projection.
const receiz = createReceizClient();
const verification = await receiz.verification.verifyArtifact(artifactBytes);
if (verification.status !== "verified-artifact") {
  throw new Error(`Artifact verification status: ${verification.status}`);
}
console.log(verification.status);