lorentz/wulf-pulse
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

docs(23): mark phase complete — milestone v3.0 finished

Browse source
This commit is contained in:
lorentz 2026-07-16 23:34:15 -04:00
parent 2e55e5e91d
commit 369ae31dba
2 changed files with 23 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

24
.planning/REQUIREMENTS.md
View file

@ -139,25 +139,25 @@ destructive remediation gated behind explicit human approval.
### Classification Disposition + Automation Gate
- [ ] **CLASSDISP-01**: The classifier assigns a dedicated `USER_AWARENESS`
- [x] **CLASSDISP-01**: The classifier assigns a dedicated `USER_AWARENESS`
verdict to campaigns confirmed as phishing-simulation-vendor (KnowBe4/Breach
Secure Now) reports, replacing the previous forced-`UNWANTED` disposition
for these confirmed-simulation cases
- [ ] **CLASSDISP-02**: `USER_AWARENESS` maps to a new non-destructive
- [x] **CLASSDISP-02**: `USER_AWARENESS` maps to a new non-destructive
`acknowledge_user` action that posts a customer-visible thank-you note
(Autotask `noteType: 18`, "Client Portal Note") to the reporting employee
- [ ] **CLASSDISP-03**: The campaign review UI surfaces `USER_AWARENESS` and
- [x] **CLASSDISP-03**: The campaign review UI surfaces `USER_AWARENESS` and
`acknowledge_user` distinctly from the existing SPAM/UNWANTED/THREAT
verdicts and their actions
- [ ] **AUTOGATE-01**: A per-company `phishing_automation_gate` table and
- [x] **AUTOGATE-01**: A per-company `phishing_automation_gate` table and
admin-gated `GET`/`PATCH`/`DELETE` API let an operator read and set three
independent opt-in automation flags (`auto_parse`, `auto_classify`,
`auto_report`) per Autotask company, defaulting to all-OFF when no row
exists
- [ ] **AUTOGATE-02**: An `/admin/phishing-automation` page lists companies
- [x] **AUTOGATE-02**: An `/admin/phishing-automation` page lists companies
with three independent per-company `Switch` toggles (one per automation
stage), backed by the `AUTOGATE-01` API
- [ ] **AUTOGATE-03**: When a company's automation gate stages are enabled,
- [x] **AUTOGATE-03**: When a company's automation gate stages are enabled,
the Autotask webhook automatically runs the gated parse→classify→acknowledge
chain for that company's phishing reports, with the `acknowledge_user`
auto-post carve-out narrowly scoped to `USER_AWARENESS` verdicts only — all
@ -236,12 +236,12 @@ Populated during roadmap creation.
| REVIEW-04 | Phase 22 | Complete |
| REVIEW-05 | Phase 22 | Complete |
| REVIEW-06 | Phase 22 | Complete |
| CLASSDISP-01 | Phase 23 | Pending |
| CLASSDISP-02 | Phase 23 | Pending |
| CLASSDISP-03 | Phase 23 | Pending |
| AUTOGATE-01 | Phase 23 | Pending |
| AUTOGATE-02 | Phase 23 | Pending |
| AUTOGATE-03 | Phase 23 | Pending |
| CLASSDISP-01 | Phase 23 | Complete |
| CLASSDISP-02 | Phase 23 | Complete |
| CLASSDISP-03 | Phase 23 | Complete |
| AUTOGATE-01 | Phase 23 | Complete |
| AUTOGATE-02 | Phase 23 | Complete |
| AUTOGATE-03 | Phase 23 | Complete |
**Coverage:**
- v1 requirements: 38 total

21
.planning/STATE.md
View file

@ -2,15 +2,15 @@
gsd_state_version: 1.0
milestone: v3.0
milestone_name: Phishing Triage Automation
status: executing
stopped_at: Phase 23 context gathered
last_updated: "2026-07-17T03:14:55.707Z"
status: milestone_complete
stopped_at: Milestone complete (Phase 23 was final phase)
last_updated: 2026-07-17T03:33:49.428Z
last_activity: 2026-07-17 -- Phase 23 execution started
progress:
total_phases: 9
completed_phases: 8
total_plans: 30
completed_plans: 29
completed_plans: 30
percent: 89
---
@ -21,14 +21,14 @@ progress:
See: .planning/PROJECT.md (updated 2026-07-14)
**Core value:** A manager/security operator can see every phishing/spam report ticket automatically triaged, deduplicated into campaigns, and classified — with any destructive remediation gated behind explicit human approval.
**Current focus:** Phase 23 — classification-disposition-per-client-automation-gate
**Current focus:** Milestone complete
## Current Position
Phase: 23 (classification-disposition-per-client-automation-gate) — EXECUTING
Plan: 1 of 6
Status: Executing Phase 23
Last activity: 2026-07-17 -- Phase 23 execution started
Phase: 23
Plan: Not started
Status: Milestone complete
Last activity: 2026-07-17
Progress: [░░░░░░░░░░] 0%
@ -36,7 +36,7 @@ Progress: [░░░░░░░░░░] 0%
**Velocity:**
- Total plans completed: 60 (v1.0: 42, v2.0: 20 across phases 10-14 — see per-phase table)
- Total plans completed: 66 (v1.0: 42, v2.0: 20 across phases 10-14 — see per-phase table)
- Average duration: —
- Total execution time: 0.0 hours (v3.0)
@ -50,6 +50,7 @@ Progress: [░░░░░░░░░░] 0%
| 15 | 3 | - | - |
| 18 | 5 | - | - |
| 21 | 2 | - | - |
| 23 | 6 | - | - |
**Recent Trend:**