AI ENGINEER / EVIDENCE

Trust the run, not the claim.

Every public capability must resolve to a fresh input, a native output and a machine-readable verification record.

Concept illustration of native assembly component facts being inspected and verified after execution — Concept illustration — public evidence must come from an actual fresh product run, not from this visual.

01 / REAL PRODUCT RUN

One continuous engineering trace.

The public recording is being prepared as a fresh, traceable run. Historical replay, rendered animation or prebuilt CAD will not be substituted.

PUBLIC RECORDING IN PREPARATION

Evidence first—footage second

Until the full recording is published, inspect the evidence contract below or request a live technical challenge.

New task ID Input hash Native artifact Oracle verdict

02 / EVIDENCE CONTRACT

What an investor or engineer can independently inspect.

The evidence package separates observation, inference, CAD execution and final verdict so a reviewer can locate the exact point of failure.

01 Original engineering inputs HASHED

02 Parsed topology and provenance TRACEABLE

03 Approved component and interface facts BOUND

04 CAD execution log and native output CREATED

05 Reopened assembly facts READ BACK

06 Deterministic verdict and refusal reason GATED

SEPARATE EVIDENCE PAGE

Generalization and refusal need their own benchmark contract.

The benchmark page defines controlled variation, expected outcomes, calibrated refusal and publication rules without mixing them into the evidence-model page.

Open Benchmark Method