docs(design): direction approved

docs/design/002-direction-round-notes.md

@@ -348,6 +348,22 @@ and brief one agent from a copy of 16, using `/content/library.json`, `parseLrc`
   recordings). Open: passage start points are keyword guesses; parts/motifs aren't timed to the
   recordings yet (report proposes a small mapping file in the content folder).
 
+### 20. Direction approved
+
+*(Claude's question)* "If this is the direction, say so. I'll then write it up and build the real app
+(full album, all sagas) without stopping for more reviews…"
+
+> "Yes. But listen wit hthe lyrics and watch should probably both be in the listen & lyrics tab. Threads
+> on the sea toggle works nicely. If hide timeline is off, maybe just put it into paths or something."
+
+- **Approved:** the direction of 16/17 (look 2, frieze accents, curtain-call voyage, stylised 3D,
+  side panel, bottom timeline with threads, real content) → build the real app. Per the user's global
+  rule: spec → plan → execution with no extra review stops; report decisions at the end.
+- **Changes on top of 17:**
+  - "Listen with the lyrics" and **Watch** both live in the **Listen & lyrics** tab (not in About).
+  - **"Threads on the sea"** toggle: keep as is ("works nicely").
+  - When the timeline is hidden, the motif strip goes **into the Paths tab** (not pinned above the tabs).
+
 ## Open questions (in priority order)
 
 1. ~~Which sea-chart approach (08–11) reads best, or which mix?~~ 11's navigation + 10's style (§9).