Operate / Publishers and independent verifiers

Public proof operations

Publish and inspect a public proof surface without requiring identity, account, session, or server permission to verify.

public proof surfacepublic artifact route and canonical verifierComplete production checklist

Implementation rail · public artifact route and canonical verifier

Exact execution and operator checks

01
Operator check
Hold public proof identity and bytes
Hold the complete artifact, record its public proof identifier and expected digest, and keep public reading and verification account-free.
Substantive records: /learn/proof-object · /reference/http-openapi
Expected: Exact held bytes and their expected identity exist before public lookup.

Exact mechanic

Verify held artifact bytes

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

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"));
const receiz = createReceizClient();
const verification = await receiz.verification.verifyArtifact(artifactBytes);
if (verification.status !== "verified-artifact") throw new Error(verification.status);
console.log(verification.status);

Mechanic: receiz.verification.verifyArtifact
Authentication and account boundary: Account-free local verification.
Exact source: node_modules/@receiz/sdk/dist/index.d.ts · SHA-256 3278d551808697d9936ffdf75931358c903bb0cc5a211191b611d4474895f6be

Expected: The exact held artifact returns verified-artifact independently of the public route.

03
Exact mechanic
Compare the public proof projection
```
curl --fail-with-body "https://receiz.com/api/public-proof/${RECEIZ_PROOF_ID:?RECEIZ_PROOF_ID is required}"
```
Mechanic
GET /api/public-proof/{id}
Authentication and account boundary
No Auth
Exact source
receiz-docs/generated/openapi-reference.json · SHA-256 2278eb9ab1dfcc90d61d4a6f9daac1bc55e17aeeab0d2d5d39228f88654bc20a
Expected: The no-auth route returns the distributed public proof projection or a stable not-found response.
04
Operator check
Reject gates and projection drift
Fail qualification if the public record requires sign-in, omits proof identity or provenance, or conflicts with the independently verified artifact.
Substantive records: /trust/hierarchy
Expected: Public proof remains an account-free witness surface beneath held artifact truth.

Complete operating anatomy

Every boundary required to ship.

Solved outcome: Anyone can hold exact public artifact bytes, inspect provenance, and independently verify the proof object.
Prerequisites: Hold the public proof identifier, expected artifact digest, intended disclosure, canonical public route, account-free requirement, provenance disclosure, and independent verifier.
Exact primitive: public proof surface
Governing law: Public proof operations is governed by public-proof-boundary: Public verification is account-free. Identity is optional and additive. canonical-artifact-verifier: The verifier classifies the supplied artifact. Embedded subpayloads and remote responses remain subordinate. verification-conformance: A passing execution confirms the checked artifact verification invariants for the exact repository state exercised.
Source-of-truth order: Receiz law → sealed artifact truth → deterministic proof object state → verified durable local or register truth → authenticated snapshot → server distribution, synchronization, indexing, and publication → database, session, observability, and interface projections.
Expected artifact, receipt, or state: A publicly reachable proof object or export whose exact bytes and verification material remain independently inspectable.
Inspection: Inspect the public object identity, exact artifact digest, provenance, custody disclosure, and verification affordance. Inspection exposes structure and receipt fields; inspection never establishes verification.
Independent verification: Independent verification for public-proof: pnpm test:verification-conformance. This establishes only the public proof surface boundary named by the bound sources; The implementation rail remains beneath proof authority: public artifact route and canonical verifier.
Offline behavior: Download once, then verify the exact held bytes offline with pinned roots and the canonical verifier.
Identity and account boundary: Public Record Moment, Seal File, Verify, Export, and public proof reading are account-free. Identity is optional and adds continuity, custody, recovery, and governed private controls after proof admission.
Security boundary: Public verification exposes only intended public proof material. Private custody controls, secrets, and non-public payloads remain separate.
Conformance command: pnpm test:verification-conformance && pnpm test:interoperability-conformance
Deployment checks: Qualify no-auth cold access, exact object identity, artifact download, provenance and custody disclosure, local verification, offline repeat, stable not-found behavior, canonical metadata, and absence of session-dependent first paint.
Production checklist: Test signed out, no cookies, network loss after download, invalid ID, digest mutation, missing provenance, mobile, print, canonical route, and local verification; fail on every sign-in gate.
Rollback and containment: Containment for public-proof: The public proof surface violates its primitive. Restore account-free read, download, inspection, and verification. The projection is rejected as weaker conflicting state. Rebuild the public projection from the admitted artifact and preserve conflict evidence. Publication is unavailable; held proof remains verifiable. Verify offline and restore publication later from the unchanged already-verified artifact. Preserve every stronger held artifact and admitted state while the named boundary is corrected.

Fail closed

Mutation and failure matrix

Public proof requires account, session, or permission to read or verify.

Effect: The public proof surface violates its primitive.
Retry: Do not authenticate around the defect.
Recovery: Restore account-free read, download, inspection, and verification.

Public projection digest or provenance conflicts with held verified bytes.

Effect: The projection is rejected as weaker conflicting state.
Retry: Do not replace held truth.
Recovery: Rebuild the public projection from the admitted artifact and preserve conflict evidence.

The public route is unavailable after artifact download.

Effect: Publication is unavailable; held proof remains verifiable.
Retry: Retry the route without blocking local use.
Recovery: Verify offline and restore publication later from the unchanged already-verified artifact.

Exact authority

Claim-to-source bindings

Public verification is account-free. Identity is optional and additive.
docs/literal-product-law.mdnormative-doctrine · SHA-256 5548a8f32bbdf35f2ba5e4545cd31ef6e2842d2c3127a3e39e10e6eb6bc5efa1
The verifier classifies the supplied artifact. Embedded subpayloads and remote responses remain subordinate.
packages/receiz-sdk/src/artifactVerification.tsimplementation-verifier · SHA-256 c10cdba92568fea273e1d9e7a3321083d52945378ab0cc83aee9720d44f0bba3
A passing execution confirms the checked artifact verification invariants for the exact repository state exercised.
scripts/test_verification_conformance.tsexecutable-conformance · SHA-256 8832d6deab2b117bfaefce67285dd3da6247957d5674eff74514ed1f75cb6678

One complete system

Exact execution and operator checks

Hold public proof identity and bytes