spatial-thread-interface.md
1 # Spatial Thread Interface 2 3 *Memory palace for parallel processing* 4 5 --- 6 7 ## Core Insight 8 9 > **We evolved to remember through space.** The linear text interface wastes this cognitive architecture. 10 11 The dinner party memory: you remember faces AND where they stood. The podcast run: concepts anchor to physical locations on the route. This is how memory actually works. 12 13 **The interface should leverage spatial anchoring for thread management.** 14 15 --- 16 17 ## The Problem 18 19 Current state: 20 - Threads exist as text lists 21 - No spatial differentiation 22 - Forks are "somewhere else" (vague) 23 - Cognitive load: "where did I put that?" 24 - Human spatial memory unutilized 25 26 --- 27 28 ## The Vision 29 30 ``` 31 ┌─────────────────────────────────────────────────────────────────────┐ 32 │ SCREEN REAL ESTATE │ 33 │ │ 34 │ ┌──────────────┐ ┌──────────────┐ │ 35 │ │ three-repo │ │ permeability │ │ 36 │ │ architecture │ │ contracts │ │ 37 │ │ │ │ │ │ 38 │ │ FORKABLE │ │ BLOCKED │ │ 39 │ │ ──────── │ │ (waiting) │ │ 40 │ └──────────────┘ └──────────────┘ │ 41 │ │ 42 │ ┌─────────────────────┐ │ 43 │ │ │ │ 44 │ │ CURRENT THREAD │ │ 45 │ │ alignment-protocol │ │ 46 │ │ │ │ 47 │ │ ████████████████ │ ← Active focus │ 48 │ │ RUNNING │ │ 49 │ │ │ │ 50 │ └─────────────────────┘ │ 51 │ │ 52 │ ┌──────────────┐ ┌──────────────┐ │ 53 │ │ ai-judges │ │ f-calculation│ │ 54 │ │ │ │ code │ │ 55 │ │ FORKABLE │ │ │ │ 56 │ │ (theoretical)│ │ FORKABLE │ │ 57 │ └──────────────┘ └──────────────┘ │ 58 │ │ 59 └─────────────────────────────────────────────────────────────────────┘ 60 ``` 61 62 **Properties:** 63 - Center = current focus (RUNNING) 64 - Periphery = available threads (FORKABLE) 65 - Position = memory anchor 66 - Proximity to center = relevance to current work 67 - Visual weight = urgency/importance 68 69 --- 70 71 ## Gradient Visualization 72 73 Thread states map to visual properties: 74 75 | State | Visual Treatment | 76 |-------|------------------| 77 | **RUNNING** | Center, full color, largest | 78 | **FORKABLE** | Periphery, ready to grab | 79 | **BLOCKED** | Grayed, shows blocker | 80 | **FORKED** | Shows which instance, linked | 81 | **COMPLETED** | Fades out, archives spatially | 82 83 **Cognitive load indicator:** 84 ``` 85 Thread Load: ████████░░ (8/10) 86 ^ Visual bar showing cognitive saturation 87 88 When this fills: 89 - AI automatically reports all threads 90 - Suggests forking lowest-priority 91 - Offers to park/export threads 92 ``` 93 94 --- 95 96 ## Interaction Model (Future) 97 98 ### Thread Placement 99 - Drag thread tiles to screen locations 100 - Position persists across sessions 101 - "I put architecture in top-left" → rememberable 102 103 ### Fork Action 104 - Click FORKABLE thread 105 - Opens new window/tab at that location 106 - Thread tile shows "FORKED → Instance 2" 107 108 ### Pickup Action 109 - New instance shows thread tile 110 - Click to load context 111 - Position inherited or user-placed 112 113 --- 114 115 ## Automated Cognitive Load Detection 116 117 The AI should detect cognitive overload signals: 118 1. **Thread count** - More than N active threads 119 2. **Context switches** - Jumping between topics rapidly 120 3. **Repetition** - Asking about same thing twice 121 4. **Time on thread** - Long threads accumulate load 122 5. **Dependency depth** - Deep chains are harder to track 123 124 **When load detected, AI outputs:** 125 126 ```markdown 127 --- 128 ## Thread Status (Cognitive Load: HIGH) 129 130 **RUNNING:** `alignment-protocol` (this thread) 131 132 **FORKABLE (ready to spin up):** 133 - `three-repo-architecture` - Top-left ↖ 134 - `permeability-contracts` - Top-right ↗ (blocked) 135 - `intermediate-ai-judges` - Bottom-left ↙ 136 137 **Recommendation:** Fork `three-repo` to parallel instance? 138 --- 139 ``` 140 141 --- 142 143 ## Implementation Levels 144 145 ### Level 0: Current (Text-based) 146 - Thread registry as markdown 147 - Human imagines spatial placement 148 - AI reports thread status on request or load detection 149 150 ### Level 1: Near-term (Window management) 151 - Each thread = terminal window 152 - Position on screen = memory anchor 153 - Human manages placement manually 154 155 ### Level 2: Mid-term (Custom UI) 156 - Thread tiles as visual elements 157 - Drag-and-drop positioning 158 - State visualization (color, size, glow) 159 - Fork/pickup buttons 160 161 ### Level 3: Future (Spatial computing) 162 - AR/VR thread objects 163 - Walk around your threads 164 - Physical memory palace 165 - Gesture-based forking 166 167 --- 168 169 ## Integration with Thread Forking Protocol 170 171 The spatial interface IS the thread registry made visual: 172 173 ``` 174 Thread Registry (Text) Spatial Interface (Visual) 175 ───────────────────── ────────────────────────── 176 | ID | State | Loc | [three-repo] [permeability] 177 | three-repo | FORKABLE | TL | ↖ ↗ 178 | permeability | BLOCKED | TR | [alignment-protocol] 179 | alignment | RUNNING | C | CENTER 180 | ai-judges | FORKABLE | BL | ↙ ↘ 181 [ai-judges] [f-calc] 182 ``` 183 184 --- 185 186 ## The Promise 187 188 > **Your screen is your memory palace.** 189 > 190 > Threads anchor to locations. 191 > Position persists, location remembers. 192 > Cognitive load made visible. 193 > Parallel processing through spatial organization. 194 > The interface leverages how you actually think. 195 196 --- 197 198 *Spatial Thread Interface v0.1 | 2026-01-15 | DESIGN CONCEPT* 199 --- 200 201 ## Related 202 203 - [[thread-tracking-protocol]] - resonance: 28% 204