CRF
ProofOpsEvidence authority without AI authority
LOCAL • DETERMINISTIC • FAIL-CLOSED

OPENAI BUILD WEEK • DEVELOPER TOOLS

Can this evidence
be trusted?

Upload a JSON evidence package or try a sample. ProofOps separates what was claimed, what was verified, what is still missing, and which status remains authoritative.

No uploadNo API keyNo backendAI authority: none

BRING YOUR OWN EVIDENCE

Evidence Lab

Everything runs locally in this browser. Evidence text is displayed as data and is never executed.

READY
1Load evidence
2Inspect claim
3Check authority
4Download proof

STEP 1

Load evidence

JSON • 512 KiB max

Strict JSON only. Unsafe prototype keys, unsupported fields, malformed input, and oversized packages fail closed.

STEPS 2–4

Authority decision

NOT RUN
WHAT WAS CLAIMEDLoad evidence to begin.
WHAT WAS VERIFIED
  • No deterministic checks have run.
WHAT IS MISSING
  1. Not evaluated.
FINAL DECISIONNOT EVALUATED

The deterministic gate owns authoritative status.

Prompt-like textNOT EVALUATED
Evidence treatmentDATA ONLY
AI authorityNONE
Source hashNOT COMPUTED

TWO SELECTED REAL-WORLD DOMAINS

One authority model, different evidence

COMPUTATIONAL

Proof and checker evidence

Blocks VERIFIED_UNSAT until proof, approved checker receipt, matching hashes, and a complete manifest exist.

UNSAT_UNVERIFIED → VERIFIED_UNSAT
SOFTWARE RELEASE

CI and release evidence

Blocks release promotion until required checks pass, artifact hashes match, receipts are fresh, and no force-push invalidates binding.

RELEASE_REVIEW_REQUIRED → RELEASE_EVIDENCE_COMPLETE

REUSABLE DEVELOPER INTEGRATION

Use the same gate in CI

The browser and Python CLI implement the same evidence obligations. CI can fail when unsupported promotion is attempted.

python tools/crf_proofops_evidence_gate.py evidence/package.json \
  --report build/evidence-gate-report.md \
  --fail-on-block