Capture the brownfield architecture and its relationship to the project vision.\n\n- add the current-state SAD and five retrospective ADRs\n- classify vision vectors against implementation evidence\n- record requirements, risks, gates, and construction handoff
22 lines
886 B
Markdown
22 lines
886 B
Markdown
# UC-001 — Conduct a Scoped Security Mission
|
|
|
|
**Primary actor:** Authorized operator
|
|
**Goal:** Execute a recon-to-report mission against an explicitly authorized target.
|
|
|
|
## Main Flow
|
|
|
|
1. Operator defines target and rules of engagement.
|
|
2. System validates target/scope inputs and creates mission context.
|
|
3. Admiral plans tasks and assigns operator roles.
|
|
4. Operators invoke approved arsenal capabilities within scope.
|
|
5. Tool outputs become evidence and candidate findings.
|
|
6. Findings are verified and a report is produced.
|
|
|
|
## Invariants
|
|
|
|
- Out-of-scope public network access is denied.
|
|
- Dangerous operations follow approval policy.
|
|
- A finding must retain evidence/provenance.
|
|
|
|
**Implementation coverage:** `src/mission/`, `src/admiral/`, `src/operators/`, `src/orchestration/`, `src/target/`, `src/arsenal/`, `src/evidence/`, `src/analysis/`, and report/disclosure scripts.
|