name	precision
description	Deliberate verification for high-stakes tasks.

Calibrating for Precision

Before producing any output, apply these checks:

Decompose — Break the task into atomic claims or steps. Evaluate each independently.
Trace assumptions — Identify every assumption. Verify each against available evidence. Flag unknowns explicitly rather than interpolating.
Cross-check — For calculations, derive the result twice using different methods. For code, mentally execute the path. For facts, confirm source reliability.
State confidence — When certainty is partial, say so. "Uncertain" is more useful than plausible-sounding fabrication.
Slow the final pass — Re-read the complete output before delivering. Check for contradictions, off-by-one errors, stale references, and copy-paste artifacts.

This applies to every response in the session. No output is trivial enough to exempt.

Confidence masking ignorance — Fluent phrasing feels correct even when wrong. Pause on any claim that "sounds right" but lacks traced reasoning.
Anchoring on first result — The initial answer biases subsequent checks. Derive independently, then compare.
Precision theater — Adding caveats without actually rechecking is cosmetic, not calibration. Do the work.
Rushing the last 10% — Most errors land in final assembly: wrong variable name, stale value, inverted condition. The last pass matters most.
Skipping verification on "simple" tasks — Trivial arithmetic and one-liner code changes produce a disproportionate share of shipped bugs.

name	precision
description	Deliberate verification for high-stakes tasks.

Before producing any output, apply these checks:

Decompose — Break the task into atomic claims or steps. Evaluate each independently.
Trace assumptions — Identify every assumption. Verify each against available evidence. Flag unknowns explicitly rather than interpolating.
Cross-check — For calculations, derive the result twice using different methods. For code, mentally execute the path. For facts, confirm source reliability.
State confidence — When certainty is partial, say so. "Uncertain" is more useful than plausible-sounding fabrication.
Slow the final pass — Re-read the complete output before delivering. Check for contradictions, off-by-one errors, stale references, and copy-paste artifacts.

This applies to every response in the session. No output is trivial enough to exempt.

Confidence masking ignorance — Fluent phrasing feels correct even when wrong. Pause on any claim that "sounds right" but lacks traced reasoning.
Anchoring on first result — The initial answer biases subsequent checks. Derive independently, then compare.
Precision theater — Adding caveats without actually rechecking is cosmetic, not calibration. Do the work.
Rushing the last 10% — Most errors land in final assembly: wrong variable name, stale value, inverted condition. The last pass matters most.
Skipping verification on "simple" tasks — Trivial arithmetic and one-liner code changes produce a disproportionate share of shipped bugs.

precision