Update documentation to reflect 2D multi-level graph approach

- Replace 3D spherical model with hierarchical graph navigation
- Update priority system to focus on visibility and resource allocation
- Change positioning from spherical coordinates to multi-level graph structure
- Update diagrams to show Strategic > Project > Feature > Task hierarchy
- Reflect current 2D implementation with dynamic levels of detail
- Remove outdated spherical terminology throughout documentation

Author: Matthew Valancy

README.md

@@ -17,7 +17,7 @@ GraphDone reimagines project management as a collaborative graph where work flow
 - 📱 **Mobile-first design** - Touch-friendly interface for distributed teams
 - 🤖 **AI agent integration** - Humans and AI coordinate as peers through the same interface
 - 🗳️ **Democratic prioritization** - Anonymous rating system lets good ideas rise organically
-- 🎯 **Spherical priority model** - Ideas migrate from periphery to center based on community validation
+- 🎯 **Hierarchical graph navigation** - Browse from high-level goals down to detailed tasks with dynamic levels of detail
 - 🌍 **Open source** - MIT licensed with no vendor lock-in
 
 ## How GraphDone Differs from Traditional PM Tools
@@ -26,7 +26,7 @@ GraphDone reimagines project management as a collaborative graph where work flow
 |----------------|-----------|
 | Hierarchical task assignment | Natural dependency flows |
 | Manager-driven priorities | Democratic community validation |
-| Linear project timelines | Spherical priority space |
+| Linear project timelines | Multi-level graph navigation |
 | Human-only collaboration | Human + AI peer collaboration |
 | Top-down resource allocation | Priority-based resource migration |
 | Rigid organizational structure | Emergent network coordination |
@@ -68,8 +68,8 @@ Visit http://localhost:3000 to see the working application!
 ### Graph Structure
 Work is modeled as interconnected **nodes** (outcomes, tasks, milestones) connected by **edges** (dependencies, relationships). Contributors—both human and AI—participate as first-class citizens in this graph.
 
-### Spherical Priority Model  
-Items exist in 3D space where priority determines distance from center. High-priority work gets full resources at the center, while experimental ideas start at the periphery with minimal resources, migrating inward as they prove value.
+### Multi-Level Graph Navigation
+Work is organized in interconnected graphs at different levels of detail. Browse from strategic goals at the top level down through projects, features, and individual tasks. The system dynamically shows the appropriate level of detail based on what you're exploring.
 
 ### Democratic Prioritization
 Anyone can propose ideas and assign personal priority. The community validates through anonymous rating. Ideas that gain support naturally migrate toward higher priority and more resources—no executive approval required.

docs/detailed-overview.md

@@ -36,41 +36,53 @@ graph TD
     end
 ```
 
-### The Spherical Priority Model
+### Multi-Level Graph Navigation
 
-Work items exist in a 3D spherical space where priority determines distance from center. This creates natural resource allocation and visibility.
+Work is organized as interconnected graphs at different levels of detail. Users can navigate from high-level strategic goals down through projects and features to individual tasks, with the system dynamically showing appropriate detail levels.
 
 ```mermaid
 graph TD
-    subgraph "Spherical Priority Space"
-        CENTER[🎯 Center<br/>Highest Priority<br/>Full Resources]
-        
-        subgraph "Inner Sphere"
-            I1[Critical Feature A]
-            I2[Security Fix]
-            I3[Performance Issue]
-        end
-        
-        subgraph "Middle Sphere"
-            M1[New Feature B]
-            M2[Code Refactor]
-            M3[Documentation]
-        end
-        
-        subgraph "Outer Sphere"
-            O1[Research Project]
-            O2[Future Ideas]
-            O3[Experiments]
-        end
-        
-        CENTER --- I1
-        CENTER --- I2
-        CENTER --- I3
-        I1 -.-> M1
-        I2 -.-> M2
-        M1 -.-> O1
-        M2 -.-> O2
+    subgraph "Strategic Level"
+        S1[Company Goals]
+        S2[Product Vision]
+        S3[Market Expansion]
+    end
+    
+    subgraph "Project Level"
+        P1[User Authentication]
+        P2[Mobile App]
+        P3[Analytics Dashboard]
+        P4[API Platform]
     end
+    
+    subgraph "Feature Level"
+        F1[Login System]
+        F2[Registration Flow]
+        F3[Touch Interface]
+        F4[Offline Mode]
+    end
+    
+    subgraph "Task Level"
+        T1[OAuth Integration]
+        T2[Password Reset]
+        T3[Gesture Recognition]
+        T4[Data Sync]
+    end
+    
+    S1 --> P1
+    S1 --> P4
+    S2 --> P2
+    S3 --> P3
+    
+    P1 --> F1
+    P1 --> F2
+    P2 --> F3
+    P2 --> F4
+    
+    F1 --> T1
+    F2 --> T2
+    F3 --> T3
+    F4 --> T4
 ```
 
 ### Democratic Prioritization Process
@@ -141,7 +153,7 @@ graph LR
 
 ### Multi-Dimensional Priority System
 
-Each node has three priority dimensions that combine into a computed priority determining its position in the sphere.
+Each node has three priority dimensions that combine into a computed priority determining its visibility and resource allocation across the graph hierarchy.
 
 ```mermaid
 graph TB
@@ -155,17 +167,15 @@ graph TB
         C --> CALC
         
         CALC --> CP[Computed Priority<br/>0.0 - 1.0]
-        CP --> R[Radius = 1 - Priority]
-        
-        R --> POS[Spherical Position<br/>radius, theta, phi]
+        CP --> VIS[Graph Visibility<br/>& Resource Allocation]
     end
     
     subgraph "Resource Allocation"
-        POS --> RA{Priority Level}
-        RA -->|0.8 - 1.0| FR[Full Resources<br/>Dedicated team]
-        RA -->|0.5 - 0.8| SR[Substantial Resources<br/>Regular attention]
-        RA -->|0.2 - 0.5| LR[Limited Resources<br/>Background work]
-        RA -->|0.0 - 0.2| MR[Minimal Resources<br/>Idle cycles only]
+        VIS --> RA{Priority Level}
+        RA -->|0.8 - 1.0| FR[High Visibility<br/>Full resources<br/>Featured in overview]
+        RA -->|0.5 - 0.8| SR[Standard Visibility<br/>Regular resources<br/>Shown in project view]
+        RA -->|0.2 - 0.5| LR[Lower Visibility<br/>Background resources<br/>Detailed view only]
+        RA -->|0.0 - 0.2| MR[Minimal Visibility<br/>Idle cycles<br/>Hidden by default]
     end
 ```
 
@@ -339,7 +349,7 @@ classDiagram
         +type: NodeType
         +title: string
         +priority: Priority
-        +position: SphericalCoordinate
+        +position: GraphPosition
         +status: NodeStatus
         +contributors: ContributorId[]
         +dependencies: NodeId[]
@@ -361,7 +371,7 @@ classDiagram
         -communityWeight: 0.3
         +calculate(priority) Priority
         +migratePriority(current, boost) Priority
-        +calculateRadiusFromPriority(priority) number
+        +calculateVisibilityFromPriority(priority) number
     }
     
     Graph --> Node
@@ -393,14 +403,14 @@ sequenceDiagram
     
     GQL->>GRAPH: Process priority update
     GRAPH->>GRAPH: Recalculate priorities
-    GRAPH->>GRAPH: Update spherical positions
+    GRAPH->>GRAPH: Update graph positions
     GRAPH->>DB: Persist changes
     
     GRAPH->>WS: Broadcast priorityChanged event
     WS->>UI1: Confirm update
     WS->>UI2: Real-time priority update
     
-    Note over UI2: Node smoothly<br/>migrates to new position
+    Note over UI2: Node updates visibility<br/>and position in graph
 ```
 
 ### GraphQL Schema Architecture
@@ -413,7 +423,7 @@ erDiagram
     Node ||--o{ Edge : "source"
     Node ||--o{ Edge : "target"
     Node ||--|| Priority : "has"
-    Node ||--|| SphericalCoordinate : "positioned_at"
+    Node ||--|| GraphPosition : "positioned_at"
     
     Contributor ||--o{ NodeContributor : "participates"
     
@@ -435,10 +445,11 @@ erDiagram
         float computed
     }
     
-    SphericalCoordinate {
-        float radius
-        float theta
-        float phi
+    GraphPosition {
+        float x
+        float y
+        int level
+        string parentId
     }
     
     Edge {
@@ -581,13 +592,13 @@ graph TB
 ### Graph Structure
 - **Nodes**: Outcomes, tasks, milestones, contributors (human and AI)
 - **Edges**: Dependencies, relationships, priorities
-- **Coordinates**: 3D spherical positioning based on priority and connections
+- **Hierarchy**: Multi-level positioning with dynamic levels of detail
 
 ### Priority System
 - **Executive flags**: Strategic priority signals from leadership
 - **Individual priority**: Personal background priority assignment
 - **Democratic weighting**: Anonymous community rating and boosting
-- **Migration algorithms**: Ideas move toward center based on validation
+- **Migration algorithms**: Ideas gain visibility and resources based on validation
 
 ### Agent Integration
 - **Graph API**: Agents read/write graph state through standard endpoints
@@ -604,7 +615,7 @@ type Node {
   type: NodeType!
   title: String!
   description: String
-  position: SphericalCoordinate!
+  position: GraphPosition!
   priority: Priority!
   contributors: [Contributor!]!
   dependencies: [Node!]!

docs/philosophy.md

@@ -64,18 +64,18 @@ GraphDone treats AI agents as first-class collaborators in the work graph. Human
 - **Anonymous contribution**: Reduce social pressure while maintaining quality through peer review
 - **Background opportunities**: Even low-priority ideas get resources and visibility
 
-## The Spherical Model
+## The Multi-Level Graph Model
 
-GraphDone organizes work in a spherical coordinate system where priority determines distance from center:
+GraphDone organizes work as interconnected graphs at different levels of detail where priority determines visibility and resource allocation:
 
-- **Center**: Highest priority outcomes with full resource allocation
-- **Inner spheres**: Important work with substantial support
-- **Outer spheres**: Experimental and background projects with idle resources
-- **Periphery**: New ideas and personal initiatives with minimal but real support
+- **Strategic Level**: High-level goals and vision with maximum visibility
+- **Project Level**: Major initiatives and features with substantial resources
+- **Feature Level**: Specific capabilities and components with focused attention
+- **Task Level**: Individual work items with targeted effort
 
-Ideas migrate inward through demonstrated value and community support. This creates a natural innovation pipeline where breakthrough concepts can prove themselves organically rather than requiring initial executive buy-in.
+Ideas gain visibility and resources through demonstrated value and community support. This creates a natural innovation pipeline where breakthrough concepts can prove themselves organically rather than requiring initial executive buy-in.
 
-Executives and managers influence the system by placing "priority flags" that create gravity wells, but they don't control the entire structure. Individual contributors can always establish their own small gravity wells on the periphery.
+Executives and managers influence the system by setting strategic priorities that cascade through the levels, but they don't control the entire structure. Individual contributors can always create new nodes at any level and let the community validate their importance.
 
 ## Technology Philosophy