Public utility / Evidence discipline

Inspect the claim before the conclusion.

Evidence Preflight turns an analytical claim into a compact record of scope, provenance, comparison, failure criteria, limitations, and intended use. It checks documentation completeness—not truth.

Start the preflight Read the standard

Evidence preflight / 01

Build the supporting record.

Use plain language. A narrower claim with visible limits is more useful than a broad claim that cannot be challenged.

01

What exactly do you believe the evidence supports?

Required · make the claim testable rather than promotional.

02

Who, what, where, and when does the claim cover—and what is outside it?

Required · include a boundary that could prevent overgeneralization.

03

What evidence, data, or source supports the claim, and as of when?

Required · enough detail for another person to trace the evidence.

04

Compared with what baseline, counterfactual, control, or prior state?

Required · “better” and “effective” need a reference case.

05

What result, condition, or observation would weaken or invalidate the claim?

Required · a claim that cannot lose is not ready to inspect.

06

What uncertainty, missing evidence, or transfer boundary remains?

Required · limitations travel with the claim.

07

What decision can this evidence inform, and who owns that decision?

Required · evidence should be tied to a defined decision, not generic confidence.

JSON cards are read in this tab only. Files are not uploaded or retained.

What this utility does

Makes the record visible.

It catches missing documentation and absolute language before a claim is shared. A schema-bound JSON card can be reopened locally, reviewed, revised, and exported again without uploading it.

Inspect the JSON Schema

Fetch a valid example

Inspect the integration repository

View v1.3.2 install instructions

What it does not do

Validate the evidence.

It does not inspect data, reproduce calculations, assess causality, verify sources, or certify a conclusion. Those require domain-specific review and testing.

Need a deeper review?

Bring the claim and the record.

For a technical inquiry, include the exported card with the evidence or system you want evaluated. Sensitive material should not be sent by email without an agreed handling boundary.

Discuss a defined scope