diff --git a/.planning/PROJECT.md b/.planning/PROJECT.md
index f1e1678..2706956 100644
--- a/.planning/PROJECT.md
+++ b/.planning/PROJECT.md
@@ -34,14 +34,14 @@ All 16 v1 requirements validated. Full pipeline working: capture -> classify ->
 
 ### Active
 
-(None — next milestone requirements TBD)
+(See REQUIREMENTS.md for v1.1 requirements)
 
 ### Out of Scope
 
-- Real-time audio playback — v1 is file output only
+- Real-time audio playback — file output only
 - GUI or web interface — CLI only
-- Custom sound mapping configuration — predefined + auto-cluster only
 - Rhythmic/percussive output — ambient/drone style only
+- Stereo position configuration — v1.1 focuses on frequency, waveform, and custom rules
 
 ## Context
 
@@ -73,9 +73,33 @@ All 16 v1 requirements validated. Full pipeline working: capture -> classify ->
 | Ordered []Rule classifier over switch | Configurable, extensible, first-match-wins semantics | Good |
 | 500ms window duration | Balances temporal resolution against snapshot frequency for synthesis | Good |
 
+## Current Milestone: v1.1 Custom Sound Mappings
+
+**Goal:** Users can customize how traffic sounds via a TOML config file
+
+**Target features:**
+- Custom frequency per traffic class (override built-in Hz values)
+- Custom waveform per class (sine, square, sawtooth, triangle)
+- User-defined classification rules with custom sounds
+- Auto-discover config from ./netsynth.toml or ~/.config/netsynth/config.toml
+- --config flag for explicit config path
+
 ## Evolution
 
 This document evolves at phase transitions and milestone boundaries.
 
+**After each phase transition:**
+1. Requirements invalidated? -> Move to Out of Scope with reason
+2. Requirements validated? -> Move to Validated with phase reference
+3. New requirements emerged? -> Add to Active
+4. Decisions to log? -> Add to Key Decisions
+5. "What This Is" still accurate? -> Update if drifted
+
+**After each milestone:**
+1. Full review of all sections
+2. Core Value check — still the right priority?
+3. Audit Out of Scope — reasons still valid?
+4. Update Context with current state
+
 ---
-*Last updated: 2026-03-26 after v1.0 milestone*
+*Last updated: 2026-03-26 after v1.1 milestone start*
diff --git a/.planning/STATE.md b/.planning/STATE.md
index af22285..91f0388 100644
--- a/.planning/STATE.md
+++ b/.planning/STATE.md
@@ -1,15 +1,15 @@
 ---
 gsd_state_version: 1.0
-milestone: v1.0
-milestone_name: MVP
-status: v1.0 milestone complete
-stopped_at: Milestone v1.0 archived
-last_updated: "2026-03-26T14:50:00.000Z"
+milestone: v1.1
+milestone_name: Custom Sound Mappings
+status: Defining requirements
+stopped_at: Milestone v1.1 started
+last_updated: "2026-03-26T15:00:00.000Z"
 progress:
-  total_phases: 4
-  completed_phases: 4
-  total_plans: 11
-  completed_plans: 11
+  total_phases: 0
+  completed_phases: 0
+  total_plans: 0
+  completed_plans: 0
 ---
 
 # Project State
@@ -19,12 +19,12 @@ progress:
 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.
-**Current focus:** Planning next milestone
+**Current focus:** Milestone v1.1 — Custom Sound Mappings
 
 ## Current Position
 
-Phase: All v1.0 phases complete
-Plan: N/A
+Phase: Not started (defining requirements)
+Plan: —
 
 ## Performance Metrics