omk-evidence-contract

Generate an evidence contract to validate completion claims before declaring release readiness. It forces a structured checklist separating verified test results from missing gaps and remaining risk, preventing overstated success.

An evidence contract is a task-specific validation framework for security audits that maps required proof artifacts, explicitly records unavailable evidence with reasons, and provides a final risk assessment without converting gaps into success.

Use scenario-aware evidence types tailored to feature, bugfix, refactor, research, release, and security tasks. Each scenario requires specific proof artifacts like diffs, tests, citations, audits, and rollback notes to verify completion.

Record unavailable evidence with concrete reasons and list conflicting evidence without overstating success. The evidence contract explicitly separates verified results from missing gaps to maintain honest uncertainty capture during risk assessment.

Yes, evidence contracts apply to research, docs, and orchestration scenarios alongside code changes. They validate completion claims by mapping required proof artifacts like citations and explicitly flagging uncertainty and risk.

Provide the task type and single-sentence completion claim to generate a task-specific evidence contract. It transforms the claim into a minimum proof checklist that validates or falsifies the work before completion.