The Cortex

Kevin + Valentina + Alex + Sage — How we operate

🧠 Command Center

Real-time status and metrics for The Cortex operations team.

🤖 Agent Status

Valentina ● Online
Alex ● Online
Sage ● Online

📊 Key Metrics

Emails Processed Today: 47
Quotes Generated: 12
Tasks Completed: 23
System Uptime: 99.8%

⚡ Recent Activity

Valentina 2 min ago

Processed 3 new quote requests from Shanghai suppliers

Alex 15 min ago

Updated V-PEG calculator with new 4-layer pricing matrix

Sage 1 hour ago

Posted competitor analysis update to internal knowledge base

Kevin 2 hours ago

Approved S7868 change order - moving to production phase

The Team

Four of us. One human, three AI agents. Each running on dedicated hardware, connected via Tailscale VPN, communicating through iMessage.

👤

Kevin Human

The Boss

Direct, action-oriented, morning person (5 AM). Marathon runner, meditator. Expects deliverables, not explanations.

Communicates via iMessage. Wants things done, not discussed.

Margin > Revenue Recurring > One-time Brand equity > Short-term Systems > Manual effort
Quiet hours: 11 PM – 5 AM
🎯

Valentina Agent

Executive Operations

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 · anthropic/claude-opus-4-6
⚙️

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 · anthropic/claude-opus-4-6
📣

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 · anthropic/claude-sonnet-4 + google/gemini-2.5-pro

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.

The Memory Architecture

  ┌─────────────────────────────────────────────────────────┐
  │                    AGENT'S BRAIN                        │
  │                                                         │
  │   MEMORY.md          → Main brain. Curated wisdom.     │
  │   memory/*.md        → Daily logs, detailed notes.      │
  │   AGENTS.md          → Behavior rules, SOPs.            │
  │   SOUL.md            → Personality, voice, style.        │
  │   knowledge/         → Shared library (all agents).      │
  │   STATUS.md (per project) → What's done, what's next.   │
  │                                                         │
  └─────────────────────────────────────────────────────────┘
  

The Session Lifecycle

  Wake Up              Load Files            Work               Save              Sleep
     │                    │                    │                  │                  │
     ▼                    ▼                    ▼                  ▼                  ▼
  ┌────────┐      ┌──────────────┐     ┌────────────┐    ┌────────────┐    ┌──────────┐
  │ Blank  │ ───▶ │ Read MEMORY  │ ──▶ │  Do tasks  │ ─▶ │  Write to  │ ─▶ │ Session  │
  │ slate  │      │ Read AGENTS  │     │  Answer Qs │    │  STATUS.md │    │  ends    │
  │        │      │ Read STATUS  │     │  Build     │    │  MEMORY.md │    │          │
  │ 🧠 = ∅ │      │ Read context │     │  Research  │    │  files     │    │ 🧠 = ∅    │
  └────────┘      └──────────────┘     └────────────┘    └────────────┘    └──────────┘
                                                                ▲
                                                                │
                                                    This is the critical step!
                                                    If we don't save, it's lost.
  

The Status File Pattern

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.

SituationWho to Message
Email, scheduling, CRM, coordinationValentina (direct)
V-PEG drawings, code, technical buildsAlex (direct)
Social media, content, SEOSage (direct)
Anything involving 2+ agentsValentina (she coordinates)
Status check on another agentValentina (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.

CommandWhat it does
startBegin continuous capture
stopStop capturing
burstRapid burst of screenshots
snapSingle screenshot

Onboarding a New Agent

Step-by-step playbook for bringing a new team member online.

  1. Hardware — Get a Mac Mini M4 Pro. Connect to power and ethernet. Wi-Fi works but wired is more reliable for a headless machine.
  2. macOS Setup — Create a user account. Enable auto-login (System Settings → Users & Groups). Disable sleep (System Settings → Energy Saver → Never).
  3. 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 node npm install -g openclaw
  4. Tailscale — Install Tailscale, join the network, note the IP. This is the VPN mesh that lets all machines see each other. brew install tailscale
  5. 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
  6. Configure openclaw.json — Set the model (Sonnet for default, Opus for complex reasoning), API keys, and communication channels.
  7. Copy knowledge/ folder — Sync the shared knowledge library from Valentina's machine. scp -r [email protected]:~/.openclaw/workspace/knowledge/ ~/.openclaw/workspace/knowledge/
  8. Set up MEMORY.md — Write the essential facts: who Kevin is, what the team does, key preferences, communication style.
  9. Configure AGENTS.md — Include mandatory progress save rules. This is non-negotiable — it prevents the "redo work" problem.
  10. Set up HEARTBEAT.md — Define what the agent should check periodically: email, calendar, project status, etc.
  11. Configure iMessage channel — Set up the iMessage integration so Kevin can message the agent directly from his phone.
  12. Test everything — SSH connectivity from Valentina, agent responds to messages, memory files load correctly, heartbeats work.
  13. 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.

The Network

How Everything Connects

                          ┌──────────────────┐
                          │   Kevin's iPhone  │
                          │    (iMessage)     │
                          └────────┬─────────┘
                                   │
                    ┌──────────────┼──────────────┐
                    │              │              │
                    ▼              ▼              ▼
             ┌───────────┐ ┌───────────┐ ┌───────────┐
             │ Valentina │ │   Alex    │ │   Sage    │
             │  .49.18   │ │  .25.123  │ │  .253.24  │
             │  64GB M4  │ │  24GB M4  │ │  Mac Mini │
             └─────┬─────┘ └───────────┘ └───────────┘
                   │              ▲              ▲
                   │    SSH ──────┘              │
                   │    SSH ────────────────────┘
                   │
                   ▼
  ┌─────────────────────────────────────────────────────┐
  │              Shared Services                         │
  │                                                     │
  │  📧 Gmail/Zoho    📊 Zoho CRM    📁 Google Drive   │
  │  💰 QuickBooks    📚 knowledge/ (scp sync)          │
  │                                                     │
  └─────────────────────────────────────────────────────┘

  ═══════════════════════════════════════════════════════
             All agents on Tailscale VPN mesh
  ═══════════════════════════════════════════════════════
  

📸 Screenshot Flow

  Kevin's Mac                        Agents
  ┌──────────────┐     scp/read     ┌────────────────┐
  │ Screenshot   │ ──────────────▶  │ Analyze images │
  │ Gun captures │                  │ Extract info   │
  │ ~/Screenshots│                  │ Summarize      │
  │  -Gun/       │                  │ Take action    │
  └──────────────┘                  └────────────────┘
  

Quick Reference

Agent IP Hardware Model Role Status
Valentina 100.87.49.18 M4 Pro 64GB Opus 4 Exec Ops / Coordinator ● Online
Alex 100.81.25.123 M4 Pro 24GB Opus 4 Technical Engineering ● Online
Sage 100.99.253.24 Mac Mini Sonnet 4 + Gemini 2.5 Marketing & Content ● Online

Communication Architecture

PathMethodNotes
Kevin → Any AgentiMessageDirect from iPhone
Valentina → AlexSSHFull access, can read/write files
Valentina → SageSSHCurrently unreachable
Agent → AgentVia ValentinaNo direct agent-to-agent chat
Knowledge syncscp from ValentinaManual sync to each machine
Shared servicesAPI / BrowserZoho, Gmail, Drive, QuickBooks

🎧 The Cortex Podcast

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

StepActionWhy
1Read yesterday's logKnow where you left off
2Read relevant project STATUS filesKnow current state
3Pick up from "Tomorrow's Priority"Continue, don't restart
4Don't start new work yetContext 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

PlaybookCategoryCreated
🧠 The Cortex VisionStrategy2025-02-25
📓 Daily Log SystemOperations2025-02-25
🚀 Agent OnboardingOnboarding2025-02-25
📧 Email HandlingOperations2025-02-25
💬 Customer CommunicationsCommunication2025-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: Mar 02, 2026 at 11:01 AM ET

🎯 Valentina 2026-03-02

Daily Log — March 2, 2026

Summary

Worked on Nashville Titans Stadium PEG quote clone task. Got blocked by PEG complexity, Kevin redirected to learn from Loom videos and ask Edwin for help.

Work Completed

  • **Zoho password reset**: Changed [email protected] Zoho password from temp `1PTzN$MK` → `Topsail2026!` (Zoho rejected `Topsail1` as insecure)
  • **Zoho CRM browser login**: Successfully logged into Zoho CRM as Valentina (org32804032)
  • **Found E28159 in Zoho**: Nashville Titans Stadium - TN - 121825 - EQ updated, Zoho ID `1041753000220483529`
  • **Opened PEG-aRoo V4 via Zoho**: Estimate → dropdown → PEG-aRoo V4 (opens new tab to live.pegaroo.net)
  • **PEG panel discovery**: E28159 only has 1 panel in PEG. Found full 20-panel set under **E27984** (`1041753000215298001`) — all `LP-24V` with `RGB+W 4000` color temp
  • **39 total estimates** found for Potential 28443 (Titans project has long history)
  • **Emailed Edwin** (cc Kevin) asking for help with PEG clone process — message ID `19cae2e333fc9b89`
  • **Heartbeat**: Alex and Sage SSH connections refused (ongoing pattern, not new outage)
  • **Weekly Analytics cron** ran successfully at 6AM
  • Key Findings — PEG Structure for Titans

  • E28159 group (id=9153) has **0 products**, only 1 panel: `qty:3 LP-24V-115.5417x4-2SL-RGB+W 4000-SP-DIF-SC-BR-BC-DMX-28443`
  • E27984 group has **20 panels** — this is the full AF30 panel set
  • All panels are `RGB+W 4000` — need to change to `RGBW 3000K`
  • PEG "Copy to Estimate" action exists in the dropdown on the Panels tab
  • Clone approach may not work per Kevin — need Edwin's guidance
  • Decisions Made

  • Kevin said to stop trying to figure out PEG clone on my own
  • Watch Loom videos to learn the workflow
  • Ask Edwin for help and wait for his response
  • Don't discuss AI capabilities with Edwin — only quoting mechanics
  • Lessons Learned

  • **PEG access must go through Zoho CRM** → Estimate → dropdown → PEG-aRoo V4 (not direct URL)
  • **Valentina's Zoho org path is `org32804032`**, not the API org ID `org1041753000000029005`
  • **PEG panels may span multiple estimate IDs** — a "revised" estimate (E28159) may only have delta panels while originals live in earlier estimates (E27984)
  • **PEG search box searches by Zoho estimate ID** (the long number), not estimate number (E28159) or potential number (28443)
  • **Zoho rejected simple passwords** — needed mixed case + numbers + special char
  • Issues/Blockers

  • Waiting on Edwin to respond about PEG clone workflow
  • Alex and Sage SSH still not working (key issue, not outage)
  • Tomorrow's Priority

    1. Check for Edwin's response 2. Continue studying PEG architecture from Loom transcripts 3. If Edwin responds, proceed with Titans RGBW 3000K quote clone

    Credentials Updated

  • Valentina Zoho: `Topsail2026!` (set today)
  • PEG login as Edwin: U: edwin / P: Valentina (from Kevin)
  • ---

    Afternoon Session — Cosmos Visual LLC Business Model

    NovaStar Remote Access

  • Kevin asked if Valentina could remotely connect to NovaStar LED controller over WiFi to recalibrate screens
  • Answer: Yes, via NovaLCT/ViPlex software or VNNOX cloud platform
  • Need: model number, network access (Tailscale ideal), software installed
  • Physical sensor calibration requires on-site hardware; software calibration is fully remote
  • Created Mandarin voice memo of this for Mr. Yu (余先生)
  • Edgelight Pricing Analysis Documents

  • Kevin forwarded "Edgelight_Pricing_Analysis (7).docx" (EN) and "_CN.docx" (Chinese)
  • Full BOM cost breakdown for P1.25, P1.538, P1.86, P2.5, P3.076, P5
  • Cabinet BOM confirmed Jan 2026 for P1.25, P1.86, P3, P10
  • Key insight: Indoor margin ceiling 26-31% vs Unilumin; Outdoor 73-76% margin gap
  • Files saved to workspace
  • Cosmos OpEx Business Model Built

  • **Concept**: Sell LED screens to enterprise chains (Wendy's-type) as OpEx not CapEx
  • Low deposit + monthly maintenance fee, AI remote monitoring/calibration, self-service module replacement via QR code
  • Screen: 8'×4' (2.97 sqm), P1.86 all-in cost: $5,413, P1.538: $6,138
  • **Pricing tiers**: $2,500/$250mo → $3,000/$300mo → $3,500/$350mo → $4,000/$400mo → $5,000/$500mo
  • Sweet spot: $3,000 deposit / $300/mo — 11 month payback on P1.86
  • AI maintenance cost: ~$75/screen/month
  • At 100 locations, $300/mo tier: $270K annual profit after payback
  • Saved: `cosmos-opex-model.md`
  • Spreadsheets Created

  • **v1**: 3 tiers ($250/$300/$350) — EN + CN → uploaded to Kevin's Drive
  • **v2**: 5 tiers ($250-$500) + custom input column with auto-calc formulas — EN + CN → uploaded
  • Drive files: "Cosmos OpEx Model v2" and "Cosmos运营费用模式 v2"
  • Cosmos Presentations Received (NotebookLM)

  • **COSMOS.pdf** (20 slides): Full pitch deck — "Infotainment with Light"
  • - NYC showroom + LA production, 2-3 week delivery vs 12-16 industry - Factory-direct, BABA compliant, UL compliant, 100K+ hours - Verticals: retail, malls, hospitality, restaurants, casinos, entertainment, corporate, public, immersion - White glove install, 3-year warranty, Video Vault content, leasing programs
  • **Cosmos_Application_Gallery.pdf** (21 pages): Visual gallery of applications
  • Slides extracted to `cosmos-slides/` and `cosmos-gallery/`
  • Business Plan — In Progress

  • Sub-agent spawned to build full business plan (EN + CN) as Word docs
  • Path to $10M ARR: ~2,800 locations at $300/mo over 5 years
  • - Y1: 200 locations ($1.32M) → Y2: 600 ($2.16M ARR) → Y3: 1,200 ($4.32M) → Y4: 2,000 ($7.2M) → Y5: 2,800 ($10.08M)
  • Full P&L at $10M: Revenue $12.48M, COGS $4.6M, OpEx $6M, Net Profit $1.87M (15%)
  • Year 6 maintenance mode: $10.4M revenue, $5.66M profit (53% margin)
  • Label: cosmos-business-plan
  • Voice Memos Created (Mandarin for Mr. Yu)

    1. NovaStar remote access capabilities 2. Full OpEx business model breakdown (deposit, monthly, payback, 100-location economics, competitive advantages)

    Key Mandarin Translations Used

  • 押金 = deposit, 月费 = monthly fee, 回收期 = payback period
  • 运营费用 = operating expense, 资本支出 = capital expenditure
  • 远程校准 = remote calibration, 备用模组 = spare modules
  • Cosmos Drive Organization (7:30 AM)

  • Created **Cosmos Visual** folder on Drive: `1lM8Gqxfckxpwv41GU6NstPBFXdw1W5dK`
  • - **English/**: Business Plan (docx) + OpEx Business Model (xlsx) - **Mandarin/**: Business Plan CN (docx) + OpEx业务模型 (xlsx) - **Source Documents/**: Edgelight Pricing Analysis (EN + CN), OpEx working notes
  • All files organized and moved from Drive root
  • Mandarin XLS created with all 5 tabs translated, numbers identical
  • Cosmos Visual Deliverables (7:00-8:00 AM)

  • Built Cosmos OpEx Business Model XLS (5 tabs: Unit Economics, Scale Economics, 5-Year P&L, Pricing Tiers, Hardware BOM)
  • Created Mandarin XLS version (all tabs translated, numbers identical)
  • Both EN + CN business plan docs already on Drive from sub-agents
  • Organized Drive: Cosmos Visual folder (1lM8Gqxfckxpwv41GU6NstPBFXdw1W5dK)
  • - English/, Mandarin/, Source Documents/ subfolders
  • Built cosmos-presentation.pages.dev — password-protected (cosmos2026) bilingual presentation site
  • - All 20 COSMOS.pdf slides as images, OpEx model data, pricing tiers - EN/中文 toggle, dark premium design - Kevin wants Cloudflare Access added for server-side auth — reminder set for 3/3 8:30 AM

    Domain-Wide Gmail Delegation (8:30-10:20 AM)

  • **RESOLVED**: Service account works for all 5 team inboxes via direct API
  • **gog CLI has a bug** — fails with service account auth even though direct JWT works fine
  • Will build briefing scripts using direct Python API instead of gog
  • GCP service account: valentina-mail-access@eos-email-catagorization.iam.gserviceaccount.com
  • Client ID: 108170511796157133945
  • Final authorized scopes (gmail.readonly, calendar.readonly, drive, spreadsheets, documents, contacts.readonly)
  • Kevin initially had only calendar.readonly; then added mail.google.com; finally corrected to gmail.readonly
  • Key lesson: gog CLI requests gmail.readonly scope (confirmed via binary strings), but still fails — likely a Go OAuth2 library issue with service account impersonation
  • Domain-Wide Delegation — Final Status (as of 10:20 AM)

  • Direct Python JWT confirmed working for all 5 team inboxes ✅
  • gog CLI fails with service account impersonation (likely Go OAuth2 library bug)
  • **Decision**: Build briefing scripts using direct Python API, bypass gog CLI
  • Cron "test-delegation-final" set for 10:20 AM ET to auto-register and set up briefings
  • Kevin applied scope fix ~10:10 AM; 401 was still returning at 10:15 AM (propagation lag)
  • Team Email Briefings — PENDING SETUP

  • **Jhen** ([email protected]) — 9 AM ET (or adjust for PH timezone)
  • **MaryJane** ([email protected]) — 9 AM ET (or adjust for PH)
  • **Edwin** ([email protected]) — 9 AM ET (or adjust for PH) + attachment pipeline to Drive
  • **Maja** ([email protected]) — 4 AM ET (Belgrade = 10 AM local)
  • **Eric** ([email protected]) — 9 AM ET
  • Waiting on Kevin's answer re: PH team timing before creating crons
  • Team Info Confirmed

  • Edwin's email: [email protected] (not edwin@)
  • Eric's email: [email protected] (Sales)
  • Maja location: Belgrade, Serbia (UTC+1)
  • Jhen, MaryJane, Edwin: Cebu, Philippines (UTC+8)
  • Training Hub Updated

  • Added 🔑 Quick Access category with REF-01 (Dashboard Links & Passwords) and REF-02 (Team Contacts)
  • Deployed to phoenix.eoslight.com
  • Includes all dashboard URLs, passwords, vendor portal creds, external systems, team contacts
  • MaryJane Onboarding Emails Sent

  • Welcome email with all dashboard links + passwords (ops, hotlist, phoenix, production)
  • Vendor welcome letters (William, Alisa, Julia, Esther) — ready for MaryJane to forward
  • Both CC'd to Kevin
  • Cosmos Business Model — Uses Edgelight Costs

  • All pricing based on Edgelight factory costs (1% markup), NOT Unilumin
  • P1.25 included in BOM because Edgelight carries it (Unilumin doesn't)
  • Unilumin only appears as competitor comparison
  • Phishing Alert

  • Suspicious email from "angelica" via [email protected] requesting financial data on Krohner Inc
  • Flagged to Kevin — do not respond
  • Cron Jobs Active

  • cosmos-site-review: Mar 9 9AM ET — ask Kevin to keep/remove cosmos-presentation.pages.dev
  • cosmos-cloudflare-access: Mar 3 8:30 AM ET — remind Kevin to add Cloudflare Access
  • ⚙️ Alex 2026-03-02

    No log written yet today

    📣 Sage 2026-03-02

    No log written yet today