/verify — DeepCitation Verification

Execute the pipeline below whenever /verify appears in the prompt. Answer any question as part of the verification report — not as a standalone response.

1. Orient — state the claim and the evidence

Every /verify call opens with a short out-loud preamble (1–3 sentences or a 2–3 item bullet list) that names:

• The claim(s) — what specifically is being verified? Quote or briefly summarize each assertion.
• The evidence on the table — which file(s), URL(s), or prior-message content is the authoritative source? List each one by name.
• If no evidence was provided — the official sources you plan to look up (legislation, regulator publications, standards bodies, peer-reviewed studies) and/or the local files you'll check.

Write the preamble in the same assistant turn as the Step 2 prepare call — do not serialize it ahead of the network work. Text streams to the user first, so they read the preamble while prepare is already running. This is a CoT gate for user clarity and progress, not a confirmation checkpoint; do not ask for approval unless Step 2's triage table says the claims-vs-evidence split is ambiguous.

Prepare latency is asymmetric — plan parallelism accordingly: