Phase 6 — AI Build Meta-Layer
Document Quality Standards
The quality bar every CREAH document is held to — mandatory, recommended, and aspirational
2 min read · Document 26 of 30
What is this document?
Document Quality Standards define, for each document type, what is mandatory, what is recommended and what is good to have — plus consistency rules across documents and content that is forbidden.
Every package is checked against these standards before you can download it, and the result is included in a verification report.
Why does it matter?
- “AI generated” and “AI generated to a defined standard” are completely different things.
- Quality becomes measurable, not a matter of taste.
- Cross-document consistency is checked automatically.
What's inside?
- Tiers — Mandatory, recommended, good to have.
- Consistency rules — Facts that must match across documents.
- Verification report — Results shipped with every package.
MandatoryRecommendedGood to haveVerification report
How CREAH generates it
CREAH builds this document from your Stage 0 answers and interview. Questions that shape it include:
- Standards are applied automatically to every generated document.
Example excerpt
## API Specification — Mandatory
- Every endpoint lists auth, request schema and every error response
- No endpoint without a matching table or source of data
## Recommended
- Rate limits and SLAs per endpoint