Result Verification

Use ONLY when the user directly asks to verify, check, reconcile, or reproduce a result ("verify this", "check these numbers", "does this tie out?", "is this right?", "reproduce it from a clean kernel", "confirm the figures match the text") — never auto-fire it before reporting, shipping, or calling an analysis done. Reconciles totals to source, reproduces the result from a clean session with a fixed seed, confirms the user-approved robustness ran (never initiating new checks itself), and confirms every figure and table matches the numbers in the prose — evidence before assertion. In R, Julia, Python, or Stata. When a result is about to ship unverified, OFFER it in one line; the user decides. NOT the adversarial pre-ship review — that's analysis-review, which follows once these checks pass.

lancegui Updated 2 repo stars
Causal Powers flow: any data, analysis, or figure request goes to question-framing, which forks to descriptive, reduced-form, structural, or predictive work, th

File contents

lancegui/causal-powers commit ac4325f820

Frequently asked questions

npx get-skill add lancegui/result-verification