Add Requirements template (Layer 4) — Aggregator approved
This commit is contained in:
+51
@@ -0,0 +1,51 @@
|
||||
# Requirements – [Client Name]
|
||||
|
||||
**Status:** Draft / Human Review / Locked
|
||||
**Last Updated:** YYYY-MM-DD
|
||||
**Reviewed by:**
|
||||
**Source Threat Register:** Link to locked Threat Register
|
||||
**Source Economics:** Link to client economics file (if available)
|
||||
|
||||
## Purpose
|
||||
Derive what the system must be capable of doing, based only on verified threats and the economic reality of what the client will pay.
|
||||
This is not workflow design and not agent design. Requirements are expressed as outcomes.
|
||||
|
||||
## Requirements
|
||||
|
||||
### Requirement ID: R-001
|
||||
- **Linked Threat ID:** T-00X
|
||||
- **Outcome Statement:** (e.g. “Loss of bookings from unanswered GMB Q&A must be detected within 24 hours”)
|
||||
- **Pricing Band Ceiling:** A / B / C (must stay within the band the client indicated)
|
||||
- **Verification Tier of Source Threat:** Tier 1 / Tier 2
|
||||
- **Speculative?** Yes / No (Yes only if required data is still missing)
|
||||
- **Notes:**
|
||||
- **Human Decision:** Accepted / Scoped down / Rejected / Deferred
|
||||
|
||||
### Requirement ID: R-002
|
||||
- **Linked Threat ID:**
|
||||
- **Outcome Statement:**
|
||||
- **Pricing Band Ceiling:** A / B / C
|
||||
- **Verification Tier of Source Threat:** Tier 1 / Tier 2
|
||||
- **Speculative?** Yes / No
|
||||
- **Notes:**
|
||||
- **Human Decision:** Accepted / Scoped down / Rejected / Deferred
|
||||
|
||||
*(Add additional Requirement ID blocks as needed)*
|
||||
|
||||
## Summary
|
||||
- Total requirements drafted:
|
||||
- Accepted:
|
||||
- Scoped down:
|
||||
- Rejected / Deferred:
|
||||
- Speculative (data still missing):
|
||||
|
||||
## Human Review Gate
|
||||
- [ ] Every requirement is traceable to a locked Threat ID
|
||||
- [ ] Every requirement is expressed as an outcome, not a feature
|
||||
- [ ] Every requirement respects the client’s indicated pricing band
|
||||
- [ ] Speculative requirements are clearly marked
|
||||
- [ ] Human has recorded a decision on each entry
|
||||
|
||||
Once this gate is signed off, the Requirements document is **Locked** and Layer 5 (Workflow Engineering) may begin.
|
||||
|
||||
**Reviewer sign-off:** _________________ Date: _________
|
||||
Reference in New Issue
Block a user