Add member work history and learning docs

docs/graph-discovery/README.md

@@ -0,0 +1,38 @@
+# Graph Discovery
+
+Status: demo-backed / active
+
+Graph discovery owns how MongoDB records become the Team memory graph. It
+materializes a sparse, auditable graph from real records first, seeded graph
+second, and demo fallback third.
+
+## Files
+
+| File | Purpose |
+| --- | --- |
+| [`spec.md`](spec.md) | Source data, graph contract, and discovery rules |
+| [`policy.md`](policy.md) | Graph hygiene, evidence thresholds, and truthfulness |
+| [`prompt.md`](prompt.md) | Graph materialization and review prompt |
+| [`plan.md`](plan.md) | Risk-path and observatory build plan |
+
+## What Is Implemented Now
+
+- `GET /api/pods/:podId/graph`.
+- `GET /api/pods/:podId/graph/reach/:id` backed by MongoDB `$graphLookup`.
+- Live graph materialization from `pods`, `engineer_states`, `observations`,
+  `collisions`, `interventions`, and `outcomes`.
+- Seeded graph in `team_model.graph` and mirrored `graph_nodes` / `graph_edges`.
+- Demo graph fallback so the stage never shows an empty canvas.
+
+## What Is Intentionally Cut
+
+- A separate graph database.
+- A broad analytics dashboard.
+- Showing every historical event by default.
+- Treating seeded demo data as live learning.
+
+## Demo Proof Path
+
+Observe screen/git state -> detect collision -> send intervention -> accept or
+dismiss outcome -> recall similar event -> show changed graph or changed
+behavior.

docs/graph-discovery/plan.md

@@ -1,6 +1,6 @@
 # Graph Discovery Plan
 
-Status: draft  
+Status: demo-backed / active
 Goal: make MongoDB graph discovery visible as a dynamic learning observatory
 
 ## Must-Have
@@ -66,4 +66,3 @@ Goal: make MongoDB graph discovery visible as a dynamic learning observatory
 - Learned path is visible when data exists.
 - Whole graph mode exists but is not the default.
 - The graph remains backed by MongoDB, not hardcoded mock data.
-

docs/graph-discovery/policy.md

@@ -1,6 +1,6 @@
 # Graph Discovery Policy
 
-Status: draft  
+Status: demo-backed / active
 Scope: graph hygiene, evidence thresholds, and UI truthfulness
 
 ## Prime Rule
@@ -80,4 +80,3 @@ Semantic colors stay stable:
 - Learned: violet dashed edge.
 
 Chrome should use the app's light shadcn tokens.
-

docs/graph-discovery/spec.md

@@ -1,7 +1,7 @@
 # Graph Discovery Spec
 
-Status: draft  
-Scope: how PodMan discovers graph nodes, edges, risk paths, and learning paths from MongoDB  
+Status: demo-backed / active
+Scope: how PodMan discovers graph nodes, edges, risk paths, and learning paths from MongoDB
 Owner: graph discovery / Team memory observatory
 
 ## Purpose
@@ -18,6 +18,20 @@ The graph must answer:
 4. What did PodMan do?
 5. What outcome changed memory?
 
+## What Is Implemented Now
+
+- Live materializer first: build from current MongoDB records.
+- Seeded graph second: read `team_model.graph` and mirrored graph collections.
+- Demo fallback third: return a grounded demo graph when live data is empty or
+  unavailable.
+- Reachability uses MongoDB `$graphLookup` over `graph_edges`.
+
+## What Is Intentionally Cut
+
+- A graph database migration.
+- Whole-history rendering as the default view.
+- Claims that seeded graph data is live learning.
+
 ## Source Data
 
 Graph discovery reads:
@@ -143,4 +157,3 @@ Optional metrics:
 - Every selected node can explain why it matters.
 - Activity stream matches graph events.
 - Graph can be rebuilt from MongoDB source records.
-