01 / Chapter 13
Demo Evaluation Decision Card
Ask for evidence before treating a convincing demo as a production system.
Read and download Demo Evaluation Decision Card →Thirteen practical tools for evaluating software, working with AI, and taking responsibility for what reaches production.
Free to read, download, and use with your team. No account or email address required.
01 / Chapter 13
Ask for evidence before treating a convincing demo as a production system.
Read and download Demo Evaluation Decision Card →02 / Chapter 14
Choose a change strategy after understanding the system and its dependencies.
Read and download Rewrite or Modernize Decision Tree →03 / Chapter 15
Assess the ability to understand, stabilize, and improve an inherited system.
Read and download Cleanup Crew Role Specification →04 / Chapter 16
Build judgment through reading, testing, user contact, and supported operational work.
Read and download New Apprenticeship Checklist →05 / Chapter 17
A repeatable check before accepting AI-assisted changes.
Read and download Daily AI Workflow →06 / Chapter 18
Review code, access boundaries, and model-connected tools before release.
Read and download AI Security Red Flags Card →07 / Chapter 19 and Appendix G
Record evidence for the level of use a system must support.
Read and download Production Readiness Scorecard →08 / Chapter 20
Use consistent questions and evidence to evaluate ownership of real systems.
Read and download Hiring Scorecard →09 / Conclusion
Turn the book into a bounded plan for one system or one area of practice.
Read and download 30 / 60 / 90 Day Action Plan →10 / Appendix C
Ask for explanations and evidence without needing to review the code yourself.
Read and download Executive Question Card →11 / Appendix H
Organize the first week of recovery while responding immediately to urgent harm.
Read and download Day-Zero Recovery Tracker →12 / Appendix D
Check the problem, operating boundaries, and evidence before and after adding AI.
Read and download AI Integration Checklist →13 / Appendix F
Review a defined change or module and record evidence that another engineer can check.
Read and download AI-Generated Code Audit Checklist →Use the questions to gather evidence and decide what to do next. These worksheets support judgment; a completed checklist alone does not establish that a system is safe or compliant.
Found something unclear? Send Kevin a correction.