CTO Toolkit
Evidence Contract
What a completed change must demonstrate before anyone is entitled to call it done. No claim without evidence.
How to use this
Attach to every change at autonomy level A2 and above. Reviewers assess the evidence, not only the diff. If a field cannot be filled in, that is the finding.
What was intended
- Intent — which requirement or contract this implements
- Change — what actually changed, in reviewable summary
- Provenance — which human and which agent produced it
- Agent trace — which tools and actions were executed
What was demonstrated
- Tests — which suites ran and what they proved
- Security — which checks ran and what they found
- Static analysis — which quality gates passed
- Architecture — whether ownership boundaries were preserved
- Dependencies — what was added, removed or upgraded
What remains uncertain
- Residual risk, and the named person who accepted it
- Known gaps in coverage for this change
- Observability — how we will know this works in production
- Rollback or mitigation path if it does not
Quality bar
- A reviewer who was absent for the work can assess it from the pack alone
- Every claim maps to something that actually ran
- Absence of evidence is recorded as absence, never as success
- Done is never asserted — it is demonstrated
This is an original, generic framework for reuse. It is not proprietary employer material.