An auto-validation pattern where a persistent script checks every AI-generated document against personal quality criteria (tone, length, structure, required sections, no-overwrite rules) before commit — letting Claude iterate autonomously through drafts until all checks pass. ## Key Characteristics - **Validator as test suite**: a script encodes document rules that persist across sessions - **Autonomous iteration**: Claude runs the validator after every write, fixes failures, re-validates - **Rules encoded, not repeated**: a script enforces expectations permanently instead of re-explaining each session - **Pre-commit integration**: validation runs before commit, catching issues before they enter history ## Example Rules Never overwrite an existing file (create a suffixed copy); require YAML frontmatter (date, status, source); CVs must include Summary/Experience/Skills/Education; strategic plans must include Current State/Options/Recommendations/Next Steps; split files over 500 lines. With 22 rejected actions and 13 excessive changes across sessions, auto-validation shifts quality control from reactive human review to proactive machine checking (the CV-overwrite incident is the canonical motivator). ## Related Concepts - [[Plan-First Workflow Gates]] - [[Self-Healing Git Workflow]] - [[Documentation-as-Verification Loop]]