Skip to content
WASID
Request access

Method

Tally. Compare. Filter. Predict.

How a verdict is reached, and why a measurement stands on its own while a claim needs a person.

Four steps

From a claim to a verdict.

Measured, or reported

A reading stands on its own. A claim needs a person.

Measured

A seismic reading, a fire detection, an airspace count. It is kept as an observation with its source and its revisions, is never given a claim verdict, and never enters the claim queue.

Reported

Someone says a thing happened. The six signals weigh it. Before it reaches the customer feed a person verifies it with a confidence score; dismissing it takes a reason, and each decision is audited.

The verdict format

Every verdict shows its working.

Illustrative — the verdict format, not a live event
VERIFIED
The six verification signals and what each says about this illustrative claim
cross-source corroborationSUPPORTS
the fact-check recordNEUTRAL
spread velocityNEUTRAL
prior-narrative correlationNEUTRAL
known manipulation patternsNEUTRAL
models weigh, humans verifySUPPORTS
The verdicts WASID returns, and what each means
VERIFIEDThe signals weigh clearly for the claim, and at least one corroborates it.
UNVERIFIEDNothing corroborates it, or the signals do not settle it either way.
DISPUTEDThe signals lean against the claim.
LIKELY FALSEThe signals weigh clearly against it.
FABRICATEDFact-checkers have rated it false, or the signals weigh overwhelmingly against it.

A check that could not run, because a source was down or a key is not configured, is listed as unavailable. It counts neither for nor against the claim.

Next

The product the method runs in.

Sentinel See the entry offer