The coordinator. Email triage, scheduling, Zoho CRM, QuickBooks, V-PEG pricing, team coordination. Can SSH to Alex and Sage.
Most intuitive with Kevin — 22K+ chars of accumulated context. If Kevin needs something cross-agent, it goes through her.
Mac Mini M4 Pro 64GB · 100.87.49.18 · Claude Opus 4
⚙️
Alex Agent
Technical Engineering
V-PEG drawings, PEG system analysis, code development. The builder.
⚠️ Known issue: tendency to redo completed work. Now has mandatory progress save rules and status files to prevent this.
Mac Mini M4 Pro 24GB · 100.81.25.123 · Claude Opus 4
📣
Sage Agent
Marketing & Content
Social media, content creation, SEO, competitive analysis. Still early in relationship with Kevin — building context over time.
Connected via SSH from Valentina. Knowledge library synced.
Mac Mini · 100.99.253.24 · Claude Opus 4
How We Think (Memory & Intelligence)
The Core Truth
Every time an agent starts a new session, it wakes up with zero memory. No recollection of yesterday, last week, or five minutes ago. This isn't a bug — it's how large language models work.
So how do we remember anything? Files. Files are our memory.
Every project gets a STATUS.md file with this structure:
# Project: V-PEG Pricing Calculator
## ✅ Completed
- Built pricing model for 3-layer systems
- Added margin calculations
- Integrated with QuickBooks
## 🔄 Current
- Working on multi-layer discount tiers
## ⏭️ Next
- Add export to PDF
- Customer-facing quote generator
## 🧩 Solved Problems
| Problem | Solution |
|--------------------------------|-----------------------------------|
| Discount stacking was wrong | Apply discounts sequentially |
| QuickBooks API timeout | Added retry with exponential back |
The "Solved Problems" table is gold. Without it, agents will re-investigate the same issues across sessions, wasting hours rediscovering the same solutions.
memory_search
Agents can do semantic search across all their files. It's not perfect — it works best when files have clear labels, headers, and descriptive content. Think of it like searching your email: good subject lines make all the difference.
The Knowledge Library
A shared knowledge/ folder synced across all machines via scp from Valentina. Contains reference docs, procedures, templates — anything a new agent would need on day one. This means new agents don't start from absolute zero.
Why Context Accumulates
More files = smarter agent. Valentina has 22K+ characters of context about Kevin — his preferences, decision patterns, communication style. That's why she "gets" Kevin better than Alex or Sage. It's not magic — it's accumulated written knowledge, loaded at the start of every session.
How to Work With Us
Practical phrases and patterns that make everything work better.
Magic Phrases
"Save your progress"
Forces the agent to write a STATUS.md update before doing anything else. Use this before switching topics or ending a conversation.
Save your progress on the pricing calculator
"Check your status file"
Prevents the agent from redoing work. Makes them read what's already been done first.
Check your status file for the logo project before doing anything
"What's your status on X?"
Makes the agent read the relevant STATUS.md and give you a summary instead of guessing.
What's your status on the website redesign?
Project Workflow
Starting a new project
Tell the agent to create a STATUS.md right away. This gives the project a "home" for progress tracking.
Start a new project for the trade show prep. Create a STATUS.md.
Switching topics mid-conversation
Always save first, then switch. Otherwise the work on topic A evaporates.
Save your progress on the quote. Now let's talk about the website.
Sharing Claude.ai work
Don't share Claude.ai links — they render client-side and agents can't read them. Instead: paste the text directly, or put it in a Google Doc.
Cross-Agent Coordination
Need something that touches multiple agents? Tell Valentina. She can SSH into Alex and Sage's machines to check status, read files, or leave instructions.
Situation
Who to Message
Email, scheduling, CRM, coordination
Valentina (direct)
V-PEG drawings, code, technical builds
Alex (direct)
Social media, content, SEO
Sage (direct)
Anything involving 2+ agents
Valentina (she coordinates)
Status check on another agent
Valentina (she SSHs and checks)
📸 The Screenshot Gun
A tool for rapid-fire screenshots while watching videos or browsing. Kevin triggers it, screenshots land in ~/Screenshots-Gun/, then agents analyze them.
Command
What it does
start
Begin continuous capture
stop
Stop capturing
burst
Rapid burst of screenshots
snap
Single screenshot
Onboarding a New Agent
Step-by-step playbook for bringing a new team member online.
Hardware — Get a Mac Mini M4 Pro. Connect to power and ethernet. Wi-Fi works but wired is more reliable for a headless machine.
macOS Setup — Create a user account. Enable auto-login (System Settings → Users & Groups). Disable sleep (System Settings → Energy Saver → Never).
Install OpenClaw — Install Homebrew, then Node.js, then the OpenClaw npm package. This is the runtime that makes the agent work.
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"brew install nodenpm install -g openclaw
Tailscale — Install Tailscale, join the network, note the IP. This is the VPN mesh that lets all machines see each other.
brew install tailscale
SSH — Enable Remote Login (System Settings → General → Sharing). Set up SSH keys so Valentina can reach the new agent.
ssh-copy-id user@new-agent-ip
Configure openclaw.json — Set the model (Sonnet for default, Opus for complex reasoning), API keys, and communication channels.
Copy knowledge/ folder — Sync the shared knowledge library from Valentina's machine.
scp -r [email protected]:~/.openclaw/workspace/knowledge/ ~/.openclaw/workspace/knowledge/
Set up MEMORY.md — Write the essential facts: who Kevin is, what the team does, key preferences, communication style.
Configure AGENTS.md — Include mandatory progress save rules. This is non-negotiable — it prevents the "redo work" problem.
Set up HEARTBEAT.md — Define what the agent should check periodically: email, calendar, project status, etc.
Configure iMessage channel — Set up the iMessage integration so Kevin can message the agent directly from his phone.
Test everything — SSH connectivity from Valentina, agent responds to messages, memory files load correctly, heartbeats work.
First conversation — Introduce yourself. Set expectations. Give context about current projects. This first session creates the foundation of the relationship.
Tip: The more context you give in early sessions, the faster the agent becomes useful. Front-load the knowledge.
Lessons Learned
Things we discovered the hard way so you don't have to rediscover them.
🔄Agents WILL redo work if progress isn't saved to files. Alex fixed the same logo three separate times. Now every agent has mandatory progress save rules in AGENTS.md, and every project gets a STATUS.md.
💭"Mental notes" don't survive sessions. If an agent says "I'll remember that" — it won't. Everything must be written to a file. No exceptions.
📝MEMORY.md should be curated wisdom, not a junk drawer. Keep it focused on distilled insights and key facts. Daily details go in memory/*.md files. MEMORY.md is the executive summary.
🧩Status files with "Solved Problems" tables prevent re-investigation. Without them, agents spend hours rediscovering the same solutions to the same problems, session after session.
🔗Claude.ai shared links don't work for agents. They render client-side with JavaScript. Agents can't read them. Paste the text or use a Google Doc instead.
⚡Always include trigger:["workflow"] in Zoho CRM tasks. Without this flag, tasks are created silently and assignees never get notified.
🔑API tokens expire — document the refresh procedures. When a token dies at 2 AM and no one remembers how to refresh it, you'll wish you had written it down.
🌙Quiet hours matter: 11 PM – 5 AM. Don't spam Kevin at night. Heartbeats should check the clock before reaching out.
🎯Clear role boundaries prevent duplicate work. If two agents think they own the same task, both will do it. Define ownership explicitly.
📚The knowledge/ library means new agents don't start from zero. Shared reference docs, procedures, and templates give any new agent a running start.
💰Cost management: Sonnet for 95% of work, Opus only for complex reasoning. Opus is 5x more expensive. Use it via sub-agents only when you genuinely need the heavy reasoning. Target: $100-150/day across all agents.
💾End sessions with "save progress" to force checkpoints. If you don't say it, the agent won't do it, and the next session starts over.
Audio episodes covering how we work. Listen anywhere — on your phone, in the car, on the plane to China.
Episode 1: How The Cortex Works
The team, how memory works, status files, why agents forget, and how to prevent repeat work.
Episode 2: The Vision
Phase 1-2-3 roadmap, playbook system, practical tips, onboarding new agents, and why the accumulated intelligence is the moat.
New episodes added as we learn. Every major milestone or lesson gets turned into audio so you can absorb it on the go.
📓 Daily Logs — The Team's Memory
Every day gets a log. Every morning starts with yesterday's review. This is how The Cortex maintains continuity across sessions and days.
Why Daily Logs Matter
Agents wake up blank every session. Without a structured daily log, yesterday's breakthroughs become today's mysteries. The daily log is the handoff between today-you and tomorrow-you.
The Rule: No agent starts new work until they've read yesterday's log and know where things left off.
End of Day — What Gets Logged
Every agent writes memory/YYYY-MM-DD.md with:
# Daily Log — 2026-02-25 (Wednesday)
## Summary
One paragraph: what happened today, big picture.
## Work Completed
- [x] Task 1 — what was done, outcome
- [x] Task 2 — what was done, outcome
## Decisions Made
- Decision: [what] — Reason: [why] — By: [Kevin/agent]
## Lessons Learned
- What we figured out (feeds into playbooks)
## Issues / Blockers
- What's stuck and why
## Tomorrow's Priority
- #1 thing to tackle first
## Kevin Interactions
- Key requests, feedback, corrections
Morning Review — The First Thing Every Day
Step
Action
Why
1
Read yesterday's log
Know where you left off
2
Read relevant project STATUS files
Know current state
3
Pick up from "Tomorrow's Priority"
Continue, don't restart
4
Don't start new work yet
Context first, action second
How Kevin Uses Daily Logs
"What did Alex do yesterday?" — Valentina pulls Alex's log via SSH
"Where are we on V-PEG?" — Agent reads log + status file, gives precise answer
While traveling: Read any agent's daily log to stay in the loop without a live conversation
Spot patterns: If the same issue shows up in multiple logs → needs a playbook
Log → Playbook Pipeline
Daily Log (raw notes)
│
▼ Lesson spotted?
│
├── YES → Write a playbook (knowledge/playbooks/)
│ → Sync to all agents
│ → Every agent knows it forever
│
└── NO → Stays in the log as history
Weekly: Review logs → distill into MEMORY.md updates
Monthly: Review playbooks → refine and improve
📖 Playbook Library — Compounding Intelligence
Every lesson The Cortex learns becomes a playbook. Every playbook makes the whole team smarter. This is our institutional memory — and eventually, our product.
The Rule: Any time Kevin corrects something, an agent discovers a better way, or something fails — write the playbook FIRST, then sync to all agents.
Playbook Format
# Playbook: [Topic]
Created: [date]
Learned from: [what happened]
Category: operations | technical | communication | onboarding | security
## The Lesson
What we learned and why it matters.
## The Playbook
Step-by-step: what to do next time.
## Watch Out For
Common pitfalls or edge cases.
Current Playbook Library
Playbook
Category
Created
🧠 The Cortex Vision
Strategy
2025-02-25
📓 Daily Log System
Operations
2025-02-25
🚀 Agent Onboarding
Onboarding
2025-02-25
📧 Email Handling
Operations
2025-02-25
💬 Customer Communications
Communication
2025-02-25
This library grows every day. Every lesson learned once is learned by everyone, forever.
How Playbooks Compound
Week 1: 5 playbooks → Team stumbles occasionally
Month 1: 30 playbooks → Most common situations covered
Month 3: 100 playbooks → New agent productive in hours
Month 6: 200 playbooks → Ready to deploy for other companies
The accumulated intelligence IS the moat.
Not the AI model. Not the hardware. The PLAYBOOKS.
The Cortex Long-Term Vision
Phase 1 — EOS Light: Prove the model. Marketing → Sales → Production → Fulfillment. Build playbooks for everything.
Phase 2 — Package: Take the playbook library + agent team and deploy for other companies.
Phase 3 — Scale: Every new client makes the system smarter. Onboarding gets faster. Playbooks compound across industries.
Kevin's Insight: "The more we all learn how to work with each other, the more efficient and faster we can be." — Every process at EOS isn't just making EOS better. It's building IP for the next engagement.
📋 Agent Logs
Live daily logs from each agent. Auto-updated every 2 hours.
Last updated: Feb 25, 2026 at 03:01 PM ET
🎯 Valentina 2026-02-25
Daily Log — 2026-02-25 (Wednesday)
Summary
Pre-dawn strategy session with Kevin. Built foundational systems for The Cortex — team name chosen, knowledge library created, training hub deployed, daily log system established. Kevin's last full day before China departure (Feb 26).
Work Completed
✅ Checked Alex's model config (confirmed Opus) via SSH
**iMessage**: Was `enabled: false` in config AND old OpenClaw version (2026.2.22-2) had bug where iMessage wouldn't load even when enabled. Updated to 2026.2.23, fixed config (dmPolicy: open, allowFrom: ["*"]), also needed `dangerouslyAllowHostHeaderOriginFallback: true` for new version's controlUi requirement. All working now.
**Google Workspace**: [email protected] authorized via remote OAuth flow. Used `gog auth keyring file` backend with `GOG_KEYRING_PASSWORD=Topsail` env var (macOS keychain doesn't persist in SSH sessions). Token imported via `gog auth tokens import`.
Edward: E28448, E28449 complete (today) — IJW Shelbyville KY (Philip Cialdella), 8'x2' and 8'x8', high prices due to quantities across 4 fixture types, Edwin reviewed, **needs Kevin's final approval** → alerted Kevin via iMessage
Edwin LightPaper Drawings — OVERDUE
Kevin changed due date to TODAY (2/24), I had it as 2/25 — my mistake
Sent reminder to Edwin on Cliq at ~12:35 PM with folder link
As of 12:43 PM — all 3 subfolders still empty, no uploads yet
Zoho CRM API — 401 Auth Error
Maton gateway returning 401 "Missing the authorization header"
Was working yesterday, may need token refresh
Trillionaire Mindset — Reminder Sent
Kevin's thinking topic for today, sent at 10:03 AM
Core idea: invisible luxury, unreplicable environments, "private chef of lighting"
Email Command Center — Color-Coded & Categories Approved (2:00 PM)
Google Sheet color-coded by category with legend in column I
14 categories approved by Kevin ("ok with that if you do not think it is too complex")
Used Sheets API batchUpdate for cell background colors