This page maps how Claude operates across Welch Wellbeing — which mode does what, what each mode can access, how context flows between systems, and where data lives. It’s the single reference point for understanding the AI architecture so that both Lee and Claude stay aligned on structure.
Claude Modes
Three modes, three distinct roles. Each has different capabilities, memory, and system access.
The Thinking Layer — strategy, philosophy, deep conversation, decision-making
Memory
Persistent cross-session Past chat searchSystem Access
Google Drive Gmail Calendar ClickUp P: Drive C: Drive Web SearchBest For
Strategic planning, IK/Sovereign Fields thinking, member decisions, complex problem-solving, content strategy, philosophical exploration
The Production Layer — file creation, bulk operations, scheduled tasks, repetitive output
Memory
Project-scoped No cross-session memorySystem Access
C: Drive (primary) P: Drive ClickUp Web SearchBest For
Kartra HTML pages, vault file operations, Hub page builds, YouTube descriptions, WhatsApp messages, bulk content production, scheduled tasks
The Automation Layer — scripts, integrations, Empire Build pipeline
Memory
Session onlySystem Access
Full filesystem APIs (programmatic)Planned For
Empire Build L2/L3, Kartra replacement automation, PWA development, API integrations, CI/CD pipelines
Context Flow
How information moves between Claude modes and the four core systems.
System Access Matrix
What each Claude mode can reach. This is the wiring diagram.
| System | Chat | Co-Work | Code (Future) | Access Method |
|---|---|---|---|---|
| ClickUp | ✓ MCP | ✓ MCP | Planned | ClickUp MCP Connector |
| Google Drive | ✓ MCP | Limited | Planned | Drive Search + Fetch |
| Gmail | ✓ MCP | Limited | Planned | Gmail MCP Connector |
| Google Calendar | ✓ MCP | Limited | Planned | Calendar MCP Connector |
| C: Drive (Vault) | ✓ Filesystem | ✓ Native | Planned | Filesystem MCP / Direct |
| P: Drive (Output) | ✓ Filesystem | ✓ Native | Planned | Filesystem MCP / Direct |
| Kartra | ✗ Manual | ✗ Manual | L2 Target | Copy-paste HTML upload |
| Web Search | ✓ Native | ✓ Native | — | Built-in tool |
| Persistent Memory | ✓ Cross-session | Project only | ✗ None | Anthropic memory system |
| Past Chat Search | ✓ Native | ✗ None | ✗ None | Chat-only feature |
| Skill Files | ✓ /mnt/skills/ | ✓ /mnt/skills/ | — | Mounted read-only |
Data Boundaries
What’s cloud vs local, what persists vs what’s session-scoped, what syncs where.
Co-Work Projects (Recommended)
Scoped workspaces for production work where context persistence matters most. Skills remain portable across all projects.
These are recommended project scopes for Co-Work, aligned to the departments where context loss costs the most time. Chat remains open-plan — no Chat projects.
Kartra lesson pages, YouTube descriptions, course architecture, movement library builds. Claude remembers which lesson you’re on, naming conventions, and series state.
Absence handling, new member follow-ups, taster communications, class register management. Context carries across member interactions.
L1/L2/L3 infrastructure work, Cloudflare migration, Hub development, automation pipeline. Deeply technical, high context overhead.
System Maps
Interactive maps of key platforms. Deep-dive views into how each system is wired.
Key Paths
Canonical file locations. One source of truth — no duplicates.