docs: start milestone v1.2 Extended Protocol Coverage
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
+14
-2
@@ -46,7 +46,7 @@ All 16 v1.0 requirements + 11 v1.1 requirements validated. Full pipeline with cu
|
|||||||
|
|
||||||
### Active
|
### Active
|
||||||
|
|
||||||
(No active requirements — next milestone not yet defined)
|
(See REQUIREMENTS.md for v1.2 requirements)
|
||||||
|
|
||||||
### Out of Scope
|
### Out of Scope
|
||||||
|
|
||||||
@@ -92,6 +92,18 @@ All 16 v1.0 requirements + 11 v1.1 requirements validated. Full pipeline with cu
|
|||||||
| LoadResult struct over tuple return | Clean single return value, extensible for future fields | Good |
|
| LoadResult struct over tuple return | Clean single return value, extensible for future fields | Good |
|
||||||
| --print-config as flag (not subcommand) | Consistent with --list-interfaces pattern, simpler CLI surface | Good |
|
| --print-config as flag (not subcommand) | Consistent with --list-interfaces pattern, simpler CLI surface | Good |
|
||||||
|
|
||||||
|
## Current Milestone: v1.2 Extended Protocol Coverage
|
||||||
|
|
||||||
|
**Goal:** Expand traffic classification with grouped protocol families that share recognizable sound signatures
|
||||||
|
|
||||||
|
**Target features:**
|
||||||
|
- Research common network protocols and identify missing ones beyond the current 10
|
||||||
|
- Group related protocols into families (Mail, Web, Remote Access, Database, Discovery, File Transfer, VoIP)
|
||||||
|
- Within-group sound design: shared base frequency, different waveforms or slight detuning
|
||||||
|
- Frequency rebalancing to accommodate new classes without overcrowding the spectrum
|
||||||
|
- New classification rules for all identified protocols
|
||||||
|
- Updated --print-config output reflecting groups
|
||||||
|
|
||||||
## Shipped Milestones
|
## Shipped Milestones
|
||||||
|
|
||||||
<details>
|
<details>
|
||||||
@@ -127,4 +139,4 @@ This document evolves at phase transitions and milestone boundaries.
|
|||||||
4. Update Context with current state
|
4. Update Context with current state
|
||||||
|
|
||||||
---
|
---
|
||||||
*Last updated: 2026-03-26 after v1.1 milestone*
|
*Last updated: 2026-03-27 after v1.2 milestone start*
|
||||||
|
|||||||
+9
-8
@@ -1,9 +1,9 @@
|
|||||||
---
|
---
|
||||||
gsd_state_version: 1.0
|
gsd_state_version: 1.0
|
||||||
milestone: v1.1
|
milestone: v1.2
|
||||||
milestone_name: Custom Sound Mappings
|
milestone_name: Extended Protocol Coverage
|
||||||
status: milestone_complete
|
status: defining_requirements
|
||||||
stopped_at: v1.1 milestone shipped
|
stopped_at: Milestone v1.2 started
|
||||||
last_updated: "2026-03-26T21:02:36.710Z"
|
last_updated: "2026-03-26T21:02:36.710Z"
|
||||||
last_activity: 2026-03-26
|
last_activity: 2026-03-26
|
||||||
progress:
|
progress:
|
||||||
@@ -21,13 +21,14 @@ progress:
|
|||||||
See: .planning/PROJECT.md (updated 2026-03-26)
|
See: .planning/PROJECT.md (updated 2026-03-26)
|
||||||
|
|
||||||
**Core value:** Network traffic patterns are instantly recognizable as distinct sounds — a ping sounds different from HTTPS noise, which sounds different from a port scan.
|
**Core value:** Network traffic patterns are instantly recognizable as distinct sounds — a ping sounds different from HTTPS noise, which sounds different from a port scan.
|
||||||
**Current focus:** Planning next milestone
|
**Current focus:** Defining requirements for v1.2
|
||||||
|
|
||||||
## Current Position
|
## Current Position
|
||||||
|
|
||||||
Phase: All v1.1 phases complete
|
Phase: Not started (defining requirements)
|
||||||
Plan: N/A
|
Plan: —
|
||||||
Status: Milestone v1.1 shipped — ready for next milestone
|
Status: Defining requirements
|
||||||
|
Last activity: 2026-03-27 — Milestone v1.2 started
|
||||||
Last activity: 2026-03-26
|
Last activity: 2026-03-26
|
||||||
|
|
||||||
Progress: [░░░░░░░░░░] 0%
|
Progress: [░░░░░░░░░░] 0%
|
||||||
|
|||||||
Reference in New Issue
Block a user