Validation, testing, and review quality
Require schema, graph, safety, language, runtime, and user-experience quality together.
Required command set
npm run validate:docs
npm run validate:playbooks
npm run typecheck
npm run test
npm run devThe documentation validator checks frontmatter, categories, role aliases, duplicate slugs, required content, and publication links. The playbook validator checks JSON structure, graph targets, domain isolation, question counts, and protected contracts.
Reviewer responsibilities
| Reviewer | Primary focus |
|---|---|
| Domain reviewer | Technical accuracy, evidence logic, expected signals |
| Safety reviewer | Access, controlled change, stop conditions, preservation |
| Documentation reviewer | Clarity, consistency, vendor-neutral language |
| QA reviewer | Schema, graph, tests, routes, responsive behavior |
| Maintainer | Project fit, release quality, attribution, merge decision |
- Reviewer
- Domain reviewer
- Primary focus
- Technical accuracy, evidence logic, expected signals
- Reviewer
- Safety reviewer
- Primary focus
- Access, controlled change, stop conditions, preservation
- Reviewer
- Documentation reviewer
- Primary focus
- Clarity, consistency, vendor-neutral language
- Reviewer
- QA reviewer
- Primary focus
- Schema, graph, tests, routes, responsive behavior
- Reviewer
- Maintainer
- Primary focus
- Project fit, release quality, attribution, merge decision
Knowledge-base test
A qualified operator who did not write the guide should be able to explain the current evidence state, next owner, safety gate, and validation without contacting the author.
Regression policy
Tests should protect behaviors and contracts, not obsolete marketing copy. A wording update should not break the suite when the same intake, isolation, or safety behavior remains present. Exact strings are appropriate only for protected names, API fields, or safety statements that must not drift.