Skip to content

CLAIM-EVIDENCE WORKBENCH / V124

Structure the claim before you write the conclusion.

Build a reviewable matrix around public source and simulation metadata. Keep counter-evidence, limitations, unresolved gaps, and unrun work visible.

Registry sources
778
Simulations
121
Reference IDs
899
Remote writes
0
01Declare every state.

PASS, FAIL, and NOT_RUN stay distinct.

02Keep the challenge visible.

Counter-evidence and gaps cannot disappear from export.

03Export the structure.

JSON and Markdown preserve IDs, states, timestamps, and limits.

04Do not automate belief.

Completeness is checked; scientific truth is not.

CURRENT-TAB WORKSPACE

Build the inspectable matrix.

Incomplete fields stay visible. Exports record structure and user-entered states, not scientific endorsement.

Current-tab state only. Nothing has been sent or saved remotely.
01
Document timestamp
Initializing current-tab timestamp...
State location
Current browser tab

CLAIM MATRIX

Separate what was asked, run, observed, challenged, and left open.

01

CLAIM ROW

claim-01

EXPLICIT STATES

No positive state is assumed.

PUBLIC METADATA REFERENCES

Attach canonical IDs, then inspect their limits.

0 / 8

Loading public metadata...

No reference selected. Validation keeps this gap visible.

EVIDENCE BOUNDARY

A complete matrix can still be scientifically wrong.

Verify authorship, rights, method fidelity, metrics, uncertainty, counter-examples, and applicability at the primary source. User-entered states are worksheet records, not SemiAgora conclusions, confidence scores, signoff, or production guidance.