verify-claims

Verify Claims

Extract verifiable claims from a text and verify each one.

Input

$ARGUMENTS

If a file path was given, read it. If text was given, use it directly. If nothing was given, ask the user what to verify.

If the text references user-facing written artifacts (answer files, scripts, code, reports), read those artifacts and extract claims from them too — not just from the conversational response.

Step 1: Extract claims

Split the text into individual, self-contained factual claims. Write them to /workspace/verify/claims.json.

Rules:

• Each claim should be a single, specific, verifiable statement.
• Claims must be self-contained — understandable without reading the full source text.
• Include claims about commands, parameter values, file paths, physics reasoning, expected outputs, and any other factual assertions.
• Preserve qualifying language ("roughly", "approximately") — do not rephrase approximate guidance as hard facts.
• Do NOT include subjective opinions or meta-commentary.

Output format — a JSON array, each object with a claim key:

[
  {"claim": "The MadGraph command to generate Drell-Yan at LO is: generate p p > e+ e-"},
  {"claim": "The default number of events in run_card.dat is 10000"}
]

Step 2: Verify each claim

For each claim, determine whether it is correct.

Environment

You may install any software needed for verification (e.g. MadGraph5_aMC@NLO, Pythia8, Delphes).

Evidence rules

Only the following count as evidence, and only when the result is unambiguous:

• Execution output: Run a MG5 script or command that tests the claim. Observe the output.
• Source code inspection: Read the relevant Python source files in the MadGraph installation directory.
• Physics reasoning: Explicit derivation from established principles (conservation laws, symmetries, kinematics, coupling structure) showing every step of the proof. MadGraph's implementation may differ from textbook physics in conventions, approximations, and defaults — for any claim about how MadGraph actually behaves, use execution or source inspection instead.