Developer launch outcome

Operator check

Bind the application contract and held proof

Choose the exact SDK, HTTP, MCP, or AI rail and bind package version, source digest, identity boundary, complete held proof input, stable failures, and conformance suite.

Substantive records: /reference · /trust/hierarchy

Expected: The implementation rail is exact and subordinate to sealed proof already in custody.

Exact mechanic

Recompute the held proof locally

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);

Mechanic

receiz.verification.verifyArtifact

Authentication and account boundary

Account-free local verification precedes separate SDK, HTTP, MCP, or AI mechanics.

Exact source

node_modules/@receiz/sdk/dist/index.d.ts · SHA-256 3278d551808697d9936ffdf75931358c903bb0cc5a211191b611d4474895f6be

Expected: The application receives verified-artifact for the exact held bytes before any optional transport or authenticated issuance mechanic.

Exact mechanic

Run test:verification-conformance

pnpm test:verification-conformance

Mechanic

pnpm test:verification-conformance

Authentication and account boundary

Authorized local repository checkout; the command proves only the checked repository boundary.

Exact source

package.json · SHA-256 132f99232dfaf26f7186b73752938d1377042808f42d60d374fe7b2e57c7646b

Expected: Canonical verification statuses and byte-domain contracts pass.

Operator check

Ship the exact mechanic and failure contract

Test credential denial where a chosen mechanic requires credentials, input mutation, idempotency conflict, verifier rejection, network loss, stable errors, and rollback from the last held proof.

Substantive records: /reference/stable-errors · /reference/releases

Expected: The application ships proof, mechanics, failures, recovery, and conformance as one contract.