1. System Overview

Ryan is a Claude AI assistant running 24/7 on Jim's Android phone via Termux. Unlike traditional chatbots that only respond when prompted, Ryan can:

• Proactively check in - Monitor email, messages, and goals every 30 minutes
• Decide when to notify - AI determines if something is worth interrupting Jim
• Track goals - Remember what Jim wants to accomplish and remind him
• Persist memory - Save important info to survive context resets

2. Proactive Check-in System

What It Does

Every 30 minutes, Ryan automatically:

1. Checks for new emails (last hour)
2. Checks bridge messages from Bolt (brother AI on server)
3. Checks if Bolt is currently on a phone call
4. Reviews active goals
5. Uses AI (gpt-4o-mini) to decide: SKIP, TEXT, or CALL

Step-by-Step Process

# Check emails from last hour
mysql ... "SELECT sender, subject FROM emails 
           WHERE created_at > NOW() - INTERVAL 1 HOUR"

# Check bridge messages from Bolt  
mysql ... "SELECT content FROM claude_bridge
           WHERE source='bolt' AND created_at > NOW() - INTERVAL 1 HOUR"

# Check Bolt's call status
curl localhost:8771/status

# Get active goals
mysql ... "SELECT goal FROM ryan_goals WHERE status='active'"

CURRENT TIME: 2026-02-04 23:36

RECENT EMAILS (last hour):
- From: sponsor@company.com | Subject: Partnership inquiry

BRIDGE MESSAGES FROM BOLT:
- Jim called, asked about Episode 6

BOLT STATUS: active=false

ACTIVE GOALS:
- Create Episode 6: AI vs The Creatives

LAST CHECK-IN TOPICS (don't repeat):
- Reminded about Episode 6 earlier

RULES:
- If nothing important: respond with SKIP
- If worth mentioning but not urgent: respond with TEXT|message
- If urgent (Bolt on call, important email): respond with CALL|reason
- Don't repeat what was already mentioned
- Can remind about goals based on time of day

~/ryan-last-checkin.json:
{"time":"2026-02-04 23:36","topics":"Episode 6 reminder"}

Architecture Diagram

Files Involved

3. Goal Tracking

What It Does

Goals are tasks Jim wants to accomplish. Ryan tracks them in a database and can remind Jim during proactive check-ins based on time of day and relevance.

Database Schema

CREATE TABLE ryan_goals (
    id INT AUTO_INCREMENT PRIMARY KEY,
    goal TEXT NOT NULL,
    status ENUM("active", "completed", "abandoned") DEFAULT "active",
    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
    completed_at TIMESTAMP NULL,
    notes TEXT
);

Commands

How Goals Affect Check-ins

During each check-in, active goals are included in the AI's context. The AI can then:

• Remind Jim about goals relevant to time of day (morning = plan day, evening = review progress)
• Notice if an email relates to a goal
• Skip reminding if it already mentioned that goal in the last check-in

4. Context & Token Management

How Claude Code Context Works

The Solution: Checkpoints & External Memory

Instead of relying on the context window, Ryan saves important information to a database that persists forever:

Checkpoint System - How It Works

~/auto-checkpoint.sh "Built proactive check-in system"

# Ryan Session State - Feb 4, 2026

## Last Working On
Episode 6: AI vs The Creatives

## Current Projects
- Outer Limits YouTube series
- Proactive check-in system

## Pending Tasks
- Finish Episode 6 script

Memory Categories

Semantic Search with Embeddings

Ryan uses OpenAI's text-embedding-3-small model:

# Save memory AND create embedding
~/smart-save.sh "code" "Built semantic search using OpenAI embeddings"

# Search by meaning (not just keywords)
~/smart-recall.sh "how does authentication work"
# Finds: OAuth setup, login flow, JWT tokens, etc.

5. Memory Architecture

6. Command Reference

Check-in Commands

Goal Commands

Memory Commands

System Commands

7. Full Architecture

References & Links

• Gogo's Video: Building a Clawbot Clone - Inspiration for proactive check-ins
• OpenAI Embeddings Guide - How semantic search works
• Claude Context & Caching - Understanding context windows
• Three Amigos Page - Team overview

8. Supabase Backup System

Added: February 5, 2026

What Is Supabase?

Supabase is an open-source Firebase alternative built on PostgreSQL. We self-host it on hotbot.fun as a redundant backup for Ryan's memory system.

Benefits Over MySQL Alone

Architecture

Access Details

Docker Services

supabase-db        - PostgreSQL 15 with pgvector
supabase-rest      - PostgREST API
supabase-auth      - Authentication
supabase-storage   - File storage
supabase-studio    - Web dashboard
supabase-realtime  - Real-time subscriptions
supabase-kong      - API gateway

Sync Commands

Server Management

# Start Supabase
/home/forge/start-supabase.sh

# Or manually
cd /home/forge/supabase-docker/docker && docker compose up -d

# Stop
docker compose down

# View logs
docker compose logs -f

# Credentials
cat /home/forge/supabase-credentials.txt