docs: Add data architecture separation + VPS deployment notes

Architecture Changes (2025-10-22):
- 3-layer data flow: Supabase (AI) → JSONL (analytics) → Obsidian (human)
- Eliminated duplicate work between AI memory and human vault
- Auto-rollup system: daily summaries → weekly → monthly
- Human effort reduced to 15 min/month (from 2+ hours/week)

VPS Deployment Planning:
- Direct Supabase client planned (bypassing unreliable MCP)
- Migration path documented for $500/month revenue milestone
- Cron automation for weekly/monthly rollups
- Z840 workstation option documented

Updated Files:
- DATA-ARCHITECTURE-SEPARATION.md (new, 582 lines)
- Soulfield-Development-Workflow.md (added Layer 1/2/3 architecture)
- AGENT-VAULT-WORKFLOW-EXPLANATION.md (created earlier)
- KILO-CODE-WEB-DEVELOPMENT.md (landing page docs)

Philosophy: Make money FIRST, upgrade infrastructure with earnings

Author: Michael

workspace/docs/Obsidian/docs/reference/workflows/Soulfield-Development-Workflow.md

@@ -445,13 +445,173 @@ claude agent lens-validator "Verify doc accuracy"
 
 ---
 
+## Data Architecture (2025-10-22)
+
+### Separation: AI Memory vs Human Vault
+
+**Problem Solved**: Eliminated duplicate work between Supabase (AI memory) and Obsidian (human knowledge).
+
+**Architecture**: Three-layer automated rollup system
+
+#### Layer 1: AI Memory (Machine-Readable)
+
+**Storage**: Supabase pgvector (direct access, bypassing MCP)
+
+**Why Direct Access**: MCP can be unreliable; production requires direct Supabase client
+
+**Purpose**:
+- Agent memory recall
+- Semantic search (milliseconds)
+- Complete interaction history
+- Vector embeddings for context
+
+**Auto-Storage**: Every agent call writes to Supabase automatically
+
+**Human Access**: Never (machine-only)
+
+**Code Location**: [backend/services/memory/memory-supabase.cjs](backend/services/memory/memory-supabase.cjs)
+
+**Migration Plan (VPS Deployment)**:
+```javascript
+// CURRENT: Via MCP (unreliable)
+await mcpClient.callTool('supabase', 'insertData', { ... });
+
+// FUTURE (VPS): Direct Supabase client
+import { createClient } from '@supabase/supabase-js';
+const supabase = createClient(SUPABASE_URL, SUPABASE_KEY);
+await supabase.from('agent_memories').insert({ ... });
+```
+
+**Cost**: $0/month (free tier), scales to $25/month at 500k interactions
+
+---
+
+#### Layer 2: JSONL Archive (Analytics)
+
+**Storage**: `/home/michael/Documents/soulfield-archive/2025-10/session-summaries/`
+
+**Format**: Newline-delimited JSON (append-only)
+
+**Purpose**:
+- Audit trail (forever)
+- Analytics source data
+- Rollup generation input
+- Debugging history
+
+**Auto-Storage**: Every agent call appends to daily JSONL file
+
+**Human Access**: Rarely (scripts read for rollups)
+
+**Example Entry**:
+```json
+{"timestamp":"2025-10-22T14:32:15Z","agent":"marketing","prompt":"Create campaign...","success":true,"lenses":["truth","causality"],"response_length":2450,"files_created":["campaigns/email-q4.md"]}
+```
+
+**Code Location**: [backend/services/auto-obsidian-sync.cjs](backend/services/auto-obsidian-sync.cjs)
+
+**Cost**: $0/month (~18MB/year, local storage)
+
+---
+
+#### Layer 3: Obsidian Vault (Human-Readable)
+
+**Storage**: `workspace/docs/Obsidian/`
+
+**Purpose**: Your source of truth, graph view, planning
+
+**Update Frequency**:
+- Daily notes: Real-time (lightweight summaries only)
+- Weekly rollups: Auto-generated Sunday or manual
+- Monthly rollups: Auto-generated end-of-month or manual
+- Reference files: Monthly review
+
+**Human Effort**: 15 min/month (reviewing auto-generated rollups)
+
+**Directory Structure**:
+```
+workspace/docs/Obsidian/
+├── daily/          # 3KB summaries (7-day retention → archive)
+├── weekly/         # Auto-generated rollups (permanent)
+├── monthly/        # Auto-generated rollups (permanent)
+└── docs/reference/ # AI-extracted knowledge (monthly updates)
+```
+
+**Data Flow**:
+```
+Agent executes
+  ↓
+Supabase + JSONL (auto, 50ms)
+  ↓
+Daily note summary (auto, ~3KB)
+  ↓
+[Sunday 11:59 PM or manual]
+  ↓
+Weekly rollup auto-generated from JSONL
+  ↓
+[End of month or manual]
+  ↓
+Monthly rollup auto-generated from weeklies
+  ↓
+Reference files updated (AI-extracted)
+```
+
+**Code Locations**:
+- Auto-sync: [backend/services/auto-obsidian-sync.cjs](backend/services/auto-obsidian-sync.cjs)
+- Rollup service: [backend/services/rollup-service.cjs](backend/services/rollup-service.cjs)
+- Knowledge extraction: [tools/extract-knowledge.cjs](tools/extract-knowledge.cjs)
+
+**Cost**: ~$2/month (Claude API for weekly/monthly summaries)
+
+**Automation Commands**:
+```bash
+# Weekly rollup (auto via cron or manual)
+node backend/services/rollup-service.cjs generateWeeklySummary 2025-W43
+
+# Monthly rollup (auto via cron or manual)
+node backend/services/rollup-service.cjs generateMonthlyRollup 2025-10
+
+# Cron setup (VPS deployment):
+# Weekly: 0 23 * * 0 (Sunday 11:59 PM)
+# Monthly: 0 23 L * * (Last day of month 11:59 PM)
+```
+
+**Full Architecture**: [[DATA-ARCHITECTURE-SEPARATION.md]]
+
+---
+
+### VPS Deployment Notes (Future)
+
+**When**: $500/month revenue milestone
+
+**Server Strategy**:
+- **Option 1**: VPS ($5-20/month) - DigitalOcean, Linode, Vultr
+- **Option 2**: Z840 Workstation (home server, $0/month after hardware)
+
+**Direct Supabase Benefits on VPS**:
+- ✅ No MCP reliability issues
+- ✅ Connection pooling for performance
+- ✅ Transaction support
+- ✅ Batch operations (faster)
+- ✅ Real-time subscriptions (future feature)
+
+**Migration Path**:
+1. Revenue hits $500/month → Purchase VPS or Z840 upgrade
+2. Install direct Supabase client (`@supabase/supabase-js`)
+3. Replace MCP calls with direct client calls
+4. Keep MCP as fallback for local development
+5. Set up cron jobs for automated rollups
+
+**Z840 Deployment Checklist**: [[docs/Z840-DEPLOYMENT-CHECKLIST.md]]
+
+---
+
 ## MCP Server Integration
 
 Both Claude Code Web and CLI subagents can access MCP servers:
 
 ### Available MCP Servers
 
-1. **Supabase** - Database operations, vector memory
+1. **Supabase** - Database operations, vector memory (⚠️ unreliable, moving to direct access on VPS)
 2. **Google Workspace** - Calendar, Docs, Sheets, Gmail, Drive
 3. **Playwright** - Browser automation, testing
 4. **Perplexity** - Research, reasoning, search
@@ -462,6 +622,9 @@ Both Claude Code Web and CLI subagents can access MCP servers:
 
 - **Claude Code Web**: Can connect to remote MCP servers
 - **CLI Subagents**: Can use MCP if specified in subagent definition
+- **Production (VPS)**: Direct Supabase client, MCP for other services
+
+**Note**: Supabase MCP is suitable for development but unreliable for production. VPS deployment will use direct `@supabase/supabase-js` client.
 
 ---