MOEModels.ai
Open workbench

DEPLOYMENT PASSPORT / LOCAL VERIFIER

NO UPLOAD · NO CERTIFICATION BY IMPLICATION

CONTENT-ADDRESSED DEPLOYMENT EVIDENCE

Verify the run.
Not the claim.

A Deployment Passport binds exact trial bytes, declared configuration, reproducibility gaps, operator authorship, and evidence limits into one portable receipt.

Try the 90-second check Create an Execution Manifest
EXECUTIONBrowser-localYour file remains on this device
CONTENT ADDRESSSHA-256Deterministic canonical payload
SIGNATUREOptionalEd25519 operator authorship
ADMISSIONSeparateVerification ≠ comparison eligibility

PASSPORT INSPECTOR

Drop the evidence.
Keep control of it.

Import a DeployBench Passport JSON file or paste its contents. Verification runs in your browser; this production surface does not publish or admit the result.

PLANNING ARTIFACT ≠ EVIDENCE PASSPORTThe Workbench Execution Manifest is not accepted by this verifier.

Run its DeployBench command, repeat the same configuration, and pack those compatible trial JSON files into a Deployment Passport first.

Create manifest
LOCAL INPUT / JSONMAX 5 MB
OR PASTE

Parsing, hashing and signature verification execute in this browser. No result is submitted to MOEModels.

AWAITING PASSPORT

Evidence enters.
Boundaries stay attached.

The verifier checks four different layers without turning any of them into certification.

  1. 01 Canonical payload integrity
  2. 02 Self-signed operator authorship
  3. 03 Trial and summary consistency
  4. 04 Reproducibility completeness

FOUR DIFFERENT QUESTIONS

Trust is a stack.
Never a badge.

MOEModels keeps cryptographic integrity, operator authorship, evidence completeness, and corpus admission separate so one green check cannot overstate what a result proves.

01INTEGRITY

Do the bytes still match?

RFC 8785 canonicalization and a SHA-256 content address reveal whether any trial, measurement, manifest field, or declared right changed after packing.

02AUTHORSHIP

Who signed this exact pack?

An optional Ed25519 operator signature binds a key to the content digest. It proves control of that key—not the truth of the declared hardware or model.

03COMPLETENESS

Can the method be inspected?

The verifier recomputes summaries, checks compatible trials, preserves failures, and reports missing artifact, runtime, topology, usage, and repetition context.

04ADMISSION

Has anyone independently accepted it?

Local verification is deliberately separate from MOEModels review, trusted-signer policy, independent reproduction, and comparison admission.

CLOSED EVIDENCE LOOP

Plan → Run → Verify → Share

The Passport is the portable handoff between the Workbench, local runner, code review, CI policy, and a future reviewed deployment corpus.

  1. 01PlanBind artifact, runtime, topology, workload and targets
  2. 02RunMeasure, repeat, and pack compatible DeployBench trials
  3. 03VerifyRecompute integrity, summaries and evidence gates
  4. 04ShareExport a reviewable receipt without upgrading its claims
NEXT ACTION

Generate the exact run contract first.

Create an Execution Manifest in the Workbench, run its command, pack compatible trials, then return here with the resulting Passport.

Create an Execution Manifest