docs(phase-23): update tracking after wave 1
This commit is contained in:
parent
9aadbcdeea
commit
b69558aae8
2 changed files with 11 additions and 11 deletions
|
|
@ -654,14 +654,14 @@ 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:** 5 plans (2 waves)
|
||||
**Plans:** 3/5 plans executed
|
||||
|
||||
Plans:
|
||||
**Wave 1**
|
||||
|
||||
- [ ] 23-01-PLAN.md — USER_AWARENESS verdict + acknowledge_user action + customer-visible note writer (noteType 18) (CLASSDISP-01, CLASSDISP-02)
|
||||
- [ ] 23-02-PLAN.md — Review UI: USER_AWARENESS badge + acknowledge_user manual action (CLASSDISP-03)
|
||||
- [ ] 23-03-PLAN.md — Migration 100 phishing_automation_gate + admin GET/PATCH/DELETE API (AUTOGATE-01)
|
||||
- [x] 23-01-PLAN.md — USER_AWARENESS verdict + acknowledge_user action + customer-visible note writer (noteType 18) (CLASSDISP-01, CLASSDISP-02)
|
||||
- [x] 23-02-PLAN.md — Review UI: USER_AWARENESS badge + acknowledge_user manual action (CLASSDISP-03)
|
||||
- [x] 23-03-PLAN.md — Migration 100 phishing_automation_gate + admin GET/PATCH/DELETE API (AUTOGATE-01)
|
||||
|
||||
**Wave 2** *(blocked on Wave 1 completion)*
|
||||
|
||||
|
|
|
|||
|
|
@ -4,8 +4,8 @@ milestone: v3.0
|
|||
milestone_name: Phishing Triage Automation
|
||||
status: executing
|
||||
stopped_at: Phase 23 context gathered
|
||||
last_updated: "2026-07-16T23:31:43.767Z"
|
||||
last_activity: 2026-07-16 -- Phase 23 planning complete
|
||||
last_updated: "2026-07-16T23:33:45.377Z"
|
||||
last_activity: 2026-07-16 -- Phase 23 execution started
|
||||
progress:
|
||||
total_phases: 9
|
||||
completed_phases: 8
|
||||
|
|
@ -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 22 — approval-ui-livelink-addressable-campaign-review-and-approve
|
||||
**Current focus:** Phase 23 — classification-disposition-per-client-automation-gate
|
||||
|
||||
## Current Position
|
||||
|
||||
Phase: 22 — COMPLETE
|
||||
Plan: 1 of 6
|
||||
Status: Ready to execute
|
||||
Last activity: 2026-07-16 -- Phase 23 planning complete
|
||||
Phase: 23 (classification-disposition-per-client-automation-gate) — EXECUTING
|
||||
Plan: 1 of 5
|
||||
Status: Executing Phase 23
|
||||
Last activity: 2026-07-16 -- Phase 23 execution started
|
||||
|
||||
Progress: [░░░░░░░░░░] 0%
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue