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

docs(phase-23): update tracking after wave 3

Browse source
This commit is contained in:
lorentz 2026-07-16 23:21:24 -04:00
parent 273ac9cb89
commit f44cdd2910
2 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

4
.planning/ROADMAP.md
View file

@ -654,7 +654,7 @@ Phases execute in numeric order. v1.0 (Phases 1-9.1) shipped 2026-07-10. v2.0 (P
**Goal:** Add a dedicated "User Awareness" verdict for confirmed phishing-simulation-vendor (KnowBe4/Breach Secure Now) reports — today forced into the generic UNWANTED bucket despite the classifier already detecting the simulation vendor and explicitly skipping the THREAT tier — and add an admin UI gate page letting an admin choose, per Autotask company, whether the phishing pipeline's parse/classify/report-to-ticket stages run automatically (now that the previously-dead Autotask webhook is fixed) or require the existing manual Analyze/Classify/triage-note triggers.
**Requirements**: CLASSDISP-01, CLASSDISP-02, CLASSDISP-03, AUTOGATE-01, AUTOGATE-02, AUTOGATE-03
**Depends on:** Phase 17, Phase 18, Phase 19, Phase 20, Phase 21, Phase 22
**Plans:** 6 plans (5 complete, 1 gap-closure pending)
**Plans:** 6/6 plans complete
Plans:
**Wave 1**
@ -670,7 +670,7 @@ Plans:
**Gap closure** *(from 23-VERIFICATION.md, Truth #18 / CR-01)*
- [ ] 23-06-PLAN.md — Idempotent + audited auto-post: autoPostAcknowledgment prevents duplicate customer-visible notes on repeat campaign webhooks (AUTOGATE-03)
- [x] 23-06-PLAN.md — Idempotent + audited auto-post: autoPostAcknowledgment prevents duplicate customer-visible notes on repeat campaign webhooks (AUTOGATE-03)
---
*Roadmap created: 2026-05-03*

10
.planning/STATE.md
View file

@ -4,8 +4,8 @@ milestone: v3.0
milestone_name: Phishing Triage Automation
status: executing
stopped_at: Phase 23 context gathered
last_updated: "2026-07-17T02:53:52.042Z"
last_activity: 2026-07-17 -- Phase 23 planning complete
last_updated: "2026-07-17T03:14:55.707Z"
last_activity: 2026-07-17 -- Phase 23 execution started
progress:
total_phases: 9
completed_phases: 8
@ -26,9 +26,9 @@ See: .planning/PROJECT.md (updated 2026-07-14)
## Current Position
Phase: 23 (classification-disposition-per-client-automation-gate) — EXECUTING
Plan: 1 of 5
Status: Ready to execute
Last activity: 2026-07-17 -- Phase 23 planning complete
Plan: 1 of 6
Status: Executing Phase 23
Last activity: 2026-07-17 -- Phase 23 execution started
Progress: [░░░░░░░░░░] 0%