56 lines
1.1 KiB
Markdown
56 lines
1.1 KiB
Markdown
# Verdict
|
|
|
|
## 1. Смысл вопроса
|
|
...
|
|
|
|
## 2. Главный пользовательский путь и дерево сценария
|
|
- root:
|
|
- critical child nodes:
|
|
- critical edges:
|
|
- primary user path:
|
|
|
|
## 3. Что реально посчитано
|
|
...
|
|
|
|
## 4. Где расхождение по бизнес-смыслу
|
|
...
|
|
|
|
## 5. Где route / capability mismatch
|
|
...
|
|
|
|
## 6. Evidence quality
|
|
- exact / partial / heuristic / technical insufficiency
|
|
- why
|
|
|
|
## 7. P0 defects
|
|
- ...
|
|
|
|
## 8. P1 defects
|
|
- ...
|
|
|
|
## 9. P2 defects
|
|
- ...
|
|
|
|
## 10. Minimal patch directions
|
|
- ...
|
|
|
|
## 11. Acceptance matrix for rerun
|
|
- Node / edge coverage:
|
|
- Canonical wording:
|
|
- Colloquial wording:
|
|
- UI-generated selected-object wording:
|
|
- Carryover invariants:
|
|
- Expected answer shape:
|
|
- Defect class:
|
|
|
|
## 12. Acceptance criteria for rerun
|
|
- ...
|
|
- Include colloquial/slang variants and UI-generated selected-object follow-up variants when they are part of the business flow.
|
|
- Require the primary user path to pass end-to-end, not only the root node.
|
|
|
|
## 13. Quality score
|
|
- integer from 0 to 100
|
|
|
|
## 14. Loop decision
|
|
- accepted / continue / partial / blocked / needs_exact_capability
|