# Requirements Audit > Feature identifier: `-` > Date: `YYYY-MM-DD` > Audited document: `/requirements.md` ## Summary | Metric | Value | |--------|-------| | Total items | | | Passed | | | Failed | | | Verdict | Passed / Passed with reservations / Failed | ## Items by category ### Clarity - [ ] Q-001 | Clarity | Every sentence in requirements has an explicit subject, verb, and object - [ ] Q-002 | Clarity | No sentence starts with "perhaps", "probably", or "if possible" without a numeric qualifier - [ ] Q-003 | Clarity | Project glossary terms are defined on their first occurrence ### Completeness - [ ] Q-004 | Completeness | All mandatory template sections are filled with content, not placeholders - [ ] Q-005 | Completeness | Each Functional Requirement has a verifiable acceptance criterion - [ ] Q-006 | Completeness | Gherkin scenarios exist for happy-path cases AND negative cases ### Consistency - [ ] Q-007 | Consistency | Key domain terms appear with the same spelling across all sections - [ ] Q-008 | Consistency | IDs referenced in one section exist in the section that defines them - [ ] Q-009 | Consistency | Confidence (🟢 / 🟡 / 🔴) is coherent with the cited source from `_reversa_sdd/` ### Coverage - [ ] Q-010 | Coverage | Every Functional Requirement has at least one Gherkin scenario - [ ] Q-011 | Coverage | Every new or changed Business Rule cites the original rule from `_reversa_sdd/domain.md` when applicable ### EdgeCases - [ ] Q-012 | EdgeCases | Relevant numeric limits have a concrete value (not "many", "few") - [ ] Q-013 | EdgeCases | Empty, null, and initial states have been considered - [ ] Q-014 | EdgeCases | Concurrency, retry, and timeout have been considered where applicable ### Jargon - [ ] Q-015 | Jargon | A new team member would understand the requirements without a glossary - [ ] Q-016 | Jargon | Acronyms are expanded on their first occurrence ### ImpliedSolution - [ ] Q-017 | ImpliedSolution | The requirements describe the what, not the how - [ ] Q-018 | ImpliedSolution | No library, framework, or commercial product name appears in the document ### Principles - [ ] Q-019 | Principles | Each Business Rule respects the active principles in `.reversa/principles.md` - [ ] Q-020 | Principles | Conflicts with principles are explicitly recorded, not hidden ## Failed items, detail ### Q-NNN > reason: > suggestion: ## Verdict **Passed / Passed with reservations / Failed** ## Change history | Date | Change | Author | |------|--------|--------| | YYYY-MM-DD | Audit generated by `/reversa-quality` | reversa |