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

docs(phase-21): update tracking after wave 1

Browse source
This commit is contained in:
lorentz 2026-07-16 12:08:43 -04:00
parent 818f1fe0ae
commit 4bbea170b2
2 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

4
.planning/ROADMAP.md
View file

@ -469,7 +469,7 @@ of a functional dependency on Phase 21.
2. The posted (or returned) note text is sanitized — no raw secrets/tokens/full malicious URL query strings appear in it
3. If no safe note-writing path exists, the same note content is returned via the API response instead of attempting any Autotask write, and no partial/unsanitized write is ever attempted as a fallback
**Plans**: 2 plans
- [ ] 21-01-PLAN.md — Pure text layer: triage-note-sanitize (URL query/secret stripping) + triage-note-format (TriageNoteEvidence + formatTriageNote) with Vitest coverage (NOTE-01)
- [x] 21-01-PLAN.md — Pure text layer: triage-note-sanitize (URL query/secret stripping) + triage-note-format (TriageNoteEvidence + formatTriageNote) with Vitest coverage (NOTE-01)
- [ ] 21-02-PLAN.md — triage-note-service (evidence gather + per-ticket TicketNotes post loop + partial-failure result) + POST /api/phishing/campaigns/[id]/triage-note route (NOTE-01)
**UI hint**: no
@ -502,7 +502,7 @@ Phases execute in numeric order. v1.0 (Phases 1-9.1) shipped 2026-07-10. v2.0 (P
| 18. Campaign Grouping & Phishing Analysis API | v3.0 | 5/5 | Complete | 2026-07-16 |
| 19. Classification Engine | v3.0 | 2/2 | Complete | 2026-07-16 |
| 20. Remediation, Approval & Audit Safety | v3.0 | 2/2 | Complete | 2026-07-16 |
| 21. Autotask Triage Note | v3.0 | 0/2 | Planned | - |
| 21. Autotask Triage Note | v3.0 | 1/2 | In Progress| |
| 22. Approval UI (LiveLink) | v3.0 | 0/TBD | Not started | - |
### Phase 22: Approval UI (LiveLink)

14
.planning/STATE.md
View file

@ -4,12 +4,12 @@ milestone: v3.0
milestone_name: Phishing Triage Automation
status: executing
stopped_at: Phase 21 context gathered
last_updated: "2026-07-16T15:17:01.109Z"
last_activity: 2026-07-16 -- Phase 20 execution started
last_updated: "2026-07-16T16:03:23.367Z"
last_activity: 2026-07-16 -- Phase 21 execution started
progress:
total_phases: 8
completed_phases: 6
total_plans: 16
total_plans: 18
completed_plans: 16
percent: 75
---
@ -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 20 — remediation-approval-audit-safety
**Current focus:** Phase 21 — autotask-triage-note
## Current Position
Phase: 20 (remediation-approval-audit-safety) — EXECUTING
Phase: 21 (autotask-triage-note) — EXECUTING
Plan: 1 of 2
Status: Executing Phase 20
Last activity: 2026-07-16 -- Phase 20 execution started
Status: Executing Phase 21
Last activity: 2026-07-16 -- Phase 21 execution started
Progress: [░░░░░░░░░░] 0%