ds-verification-before-completion

What problem does it solve?

It prevents stale, cached, or non-representative analysis outputs from being used to make final, significant, trustworthy, or decision-ready claims.

Core Features & Use Cases

• Verification Gate for Final Claims: Enforces reruns and rechecks of the relevant notebook cells or script entry point before stating results are final or decision-ready.
• Claim Scoping for Intermediate Updates: Allows narrow, scoped progress claims only after verifying the specific artifacts that support that claim.
• Consistency Checks Between Numbers and Narrative: Requires recomputing the estimate, interval, and significance metrics and confirming that charts, tables, and written conclusions agree.
• Minimum Evidence & Red-Flag Prevention: Mandates explicit evidence inputs (data window, units, sample sizes, metric definition, statistical method) and blocks common failure patterns like “ran yesterday,” “looks right,” or screenshot-only p-values.

Quick Start

Use ds-verification-before-completion right before you write the final results paragraph of an experiment notebook to rerun the analysis and confirm that the recomputed estimate, confidence interval, sample sizes, and written conclusion match exactly.