Operate / Creators

Creator launch outcome

Record authorship moments, seal media or records, publish proof, and preserve provenance and custody across sharing and transfer.

authorship proof object and public witnessRecord and Seal, public proof, and optional identity continuityComplete production checklist

Implementation rail · Record and Seal, public proof, and optional identity continuity

Exact execution and operator checks

  1. 01

    Operator check

    Hold the creator original

    Use Record Moment for a moment or Seal File for existing media, retain the returned proof-object bytes, and name intended public disclosure and optional identity or custody bindings.

    Substantive records: /learn/proof-object · /build/proof-object

    Expected: The creator holds the sealed original before publication.

  2. 02

    Exact mechanic

    Verify the original

    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; identity adds continuity only.
    Exact source
    node_modules/@receiz/sdk/dist/index.d.ts · SHA-256 3278d551808697d9936ffdf75931358c903bb0cc5a211191b611d4474895f6be

    Expected: The exact original returns verified-artifact independently of publication.

  3. 03

    Exact mechanic

    Read 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 public no-auth route returns the published proof record.

  4. 04

    Operator check

    Qualify authorship and custody

    Compare public identity, artifact digest, provenance, and disclosed custody with the held original. Reject account gates, digest drift, missing provenance, or ownership claims without a transfer receipt.

    Substantive records: /operate/public-proof · /operate/ownership-transfer

    Expected: Authorship proof and optional custody remain independently legible.

Complete operating anatomy

Every boundary required to ship.

Solved outcome
A creator holds a sealed original, publishes an account-free proof surface, and carries provenance through custody or sale.
Prerequisites
Hold the moment claim or exact original file, creator custody, the selected Record Moment or Seal File operation identity, sealed proof-object export, intended public disclosure, optional identity binding, optional transfer authority, and independent verifier.
Exact primitive
authorship proof object and public witness
Governing law
Creator launch outcome 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. market-conformance: A passing execution confirms the checked market ownership 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 sealed creator artifact with stable identity, exact bytes, provenance, verification, and optional custody state.
Inspection
Inspect the original artifact bytes, proof identity, provenance, public witness route, and ownership disclosure. Inspection exposes structure and receipt fields; inspection never establishes verification.
Independent verification
Independent verification for creator-outcome: pnpm test:verification-conformance. This establishes only the authorship proof object and public witness boundary named by the bound sources; The implementation rail remains beneath proof authority: Record and Seal, public proof, and optional identity continuity.
Offline behavior
The downloaded original verifies without the publishing service. Identity adds continuity but never gates public inspection.
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
Publish only intended payloads; keep identity recovery and custody credentials private; verify before transfer or sale.
Conformance command
pnpm test:verification-conformance
Deployment checks
Qualify Record Moment for a moment claim or Seal File for existing source material, local and offline verification, account-free public proof, provenance disclosure, share metadata, identity privacy, optional transfer and Settlement separation, takedown boundaries, and recovery.
Production checklist
Choose Record Moment or Seal File; execute it; export; hash; verify; publish public proof signed out; download and verify offline; inspect provenance; test mutation; test identity privacy; test optional custody transfer separately; recover the original proof object.
Rollback and containment
Containment for creator-outcome: The public projection is rejected. Restore publication from the held sealed proof object. The public witness primitive fails. Restore account-free read, download, and verification. Ownership or payment is unproven. Complete and reconcile the separate governed operations. Preserve every stronger held artifact and admitted state while the named boundary is corrected.

Fail closed

Mutation and failure matrix

F1

Published bytes or digest differ from the held creator original.

Effect
The public projection is rejected.
Retry
Do not overwrite the original.
Recovery
Restore publication from the held sealed proof object.
F2

Public authorship proof requires account access.

Effect
The public witness primitive fails.
Retry
Do not ask viewers to sign in.
Recovery
Restore account-free read, download, and verification.
F3

A sale or transfer claim lacks custody and Settlement receipts.

Effect
Ownership or payment is unproven.
Retry
Do not infer from listing or checkout UI.
Recovery
Complete and reconcile the separate governed operations.

Exact authority

Claim-to-source bindings

  1. Public verification is account-free. Identity is optional and additive.

    docs/literal-product-law.mdnormative-doctrine · SHA-256 5548a8f32bbdf35f2ba5e4545cd31ef6e2842d2c3127a3e39e10e6eb6bc5efa1
  2. The verifier classifies the supplied artifact. Embedded subpayloads and remote responses remain subordinate.

    packages/receiz-sdk/src/artifactVerification.tsimplementation-verifier · SHA-256 c10cdba92568fea273e1d9e7a3321083d52945378ab0cc83aee9720d44f0bba3
  3. A passing execution confirms the checked market ownership invariants for the exact repository state exercised.

    scripts/test_market_conformance.tsexecutable-conformance · SHA-256 47c7ebb7eb9f3854f31dbc7266909f9e4c9726908930d236f3a76eaacae54eb7