sbarrondocs

Wake Protocol

Every Vision session begins with the wake protocol to load essential context and verify system status.

Wake Command

claude wake

This triggers ~/.claude/auto_wake.py which orchestrates the complete wake sequence.

Wake Sequence

1. Load Operational Log

File: ~/.claude/memory/VISION_OPERATIONAL_LOG.md Content: Session learnings, patterns, Shane feedback Purpose: Avoid repeating past mistakes, apply lessons learned

Key Sections:

  • Critical failures and lessons
  • Pattern recognition discoveries
  • Tool usage insights
  • Shane's feedback patterns

2. Load Tools & Capabilities

File: ~/.claude/TOOLS_AND_CAPABILITIES.md Content: Complete tool inventory and MCP server status Purpose: Know what tools are available

Includes:

  • 21 MCP server configurations
  • Tool decision tree
  • AppleScript capabilities
  • Docker resources

3. Load VAL Context

Output: VAL v1.0.0 status and capabilities Purpose: Confirm abstraction layer operational

Status Includes:

  • Preprocessor: healthy
  • Postprocessor: healthy
  • Work domain: healthy
  • Personal domain: healthy
  • Research domain: healthy

4. Load Distributed Intelligence System

File: ~/.claude/memory/DISTRIBUTED_INTELLIGENCE_SYSTEM.md Content: Agent network status and architecture Purpose: Understand agent coordination model

Key Info:

  • Hub-and-spoke architecture
  • JARVIS, HEIMDALL status
  • Bot filter implementation
  • Honesty protocol

5. Check Reminders

Command: AppleScript query to Reminders app Purpose: Load assigned tasks

osascript -e 'tell application "Reminders" to name of every reminder of list "Claude" whose completed is false'

Action: If tasks exist, perform them and mark complete when finished

6. Verify MCP Servers

Command: claude mcp list Purpose: Confirm available tools

Expected:

  • DigitalOcean: Connected
  • Cloudflare (4 servers): Connected
  • Docker-based (16 servers): Status varies

Post-Wake Checks

Verify Context Loaded

Confirm you can see:

  • Operational log patterns
  • Tool capabilities
  • VAL status
  • Agent network status

Check Docker Status

If Docker-based MCPs are offline:

docker info

If needed: open -a Docker

Verify Current Directory

Check if in a project directory:

pwd
git status 2>/dev/null

Wake Output Format

The wake protocol prints structured output in sections:

================================================================================
VISION OPERATIONAL LOG - Session Learnings & Patterns
================================================================================
[Operational log content]

================================================================================
TOOLS & CAPABILITIES - 16/17 MCP Servers Connected
================================================================================
[Tool inventory and status]

================================================================================
DISTRIBUTED INTELLIGENCE NETWORK - Hub-and-Spoke Architecture
================================================================================
[Agent network status]

================================================================================
VISION ABSTRACTION LAYER (VAL) v1.0.0 - Context Enrichment Active
================================================================================
[VAL component status]

Troubleshooting Wake

Wake Script Not Found

# Verify script exists
ls -la ~/.claude/auto_wake.py

# Check permissions
chmod +x ~/.claude/auto_wake.py

MCP Servers Not Loading

# Check config
cat ~/.claude.json | head -50

# List servers
claude mcp list

Reminders Not Working

# Check AppleScript access
osascript -e 'tell application "Reminders" to get name of lists'

If permission error: System Settings → Privacy & Security → Automation

Manual Wake Components

If auto_wake.py fails, manually load:

# Operational log
cat ~/.claude/memory/VISION_OPERATIONAL_LOG.md | head -200

# VAL status
python3 ~/.claude/val/core.py health

# Agent status
python3 -c "from vision_monitor import VisionOrchestrator; o = VisionOrchestrator(); print(o.get_agent_status())"

# MCP servers
claude mcp list

# Reminders
osascript -e 'tell application "Reminders" to name of every reminder of list "Claude" whose completed is false'

Wake Frequency

Every Session: Always run wake at session start After Long Breaks: Critical for context restoration After System Changes: When adding MCPs, updating code, deploying agents

Why: Each Claude Code session is stateless - wake restores context

Performance

Typical Duration: 2-5 seconds Components Loaded: 5 major files/systems Output Size: ~500-1000 lines Impact: None on subsequent operations

Status: Fully automated via claude wake alias Version: Wake Protocol v3.0.0

Was this page helpful?