Now It's Live

🧠 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%

🔗 Quick Links

📋 Zoho CRM 📁 Google Drive 🎓 Training Hub ⚡ V-PEG

⚡ 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.

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 node npm 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.

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

Path	Method	Notes
Kevin → Any Agent	iMessage	Direct from iPhone
Valentina → Alex	SSH	Full access, can read/write files
Valentina → Sage	SSH	Currently unreachable
Agent → Agent	Via Valentina	No direct agent-to-agent chat
Knowledge sync	scp from Valentina	Manual sync to each machine
Shared services	API / Browser	Zoho, 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

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: Mar 04, 2026 at 01:01 PM ET

🎯 Valentina 2026-03-04

Daily Log — March 4, 2026 (evening session, Kevin in China)

Principio Project (28629/S7186) — Scope & Letter Revisions

Kevin's Corrections (Critical Framing — applied v3→v4→v5)

1. **NOT a pre-shipment review** — Kevin inspected an **extra frame produced by the factory for EOS's own evaluation/testing purposes** 2. **Shipment is via ocean freight**, currently awaiting loading onto the vessel 3. Kevin reviewed the sample, found ~40% light output loss, and is now **recalling the shipment back to the factory** to open and rework 4. **All rework materials will be prepared in advance** of the shipment's return to minimize turnaround 5. **Do NOT discuss possible solutions/alternatives** — wait until Kevin gets feedback on whether proposed fixes will actually work 6. **Do NOT discuss what EOS "should have done"** — no self-critical language, no "we acknowledge that gap" 7. **Lead with standard product config** — backer provides support + reflects light forward. Then finding, then recall. 8. **Remove all money/pricing references** from scope document (v5) 9. Kevin uploading WeiLiang texts to Drive folder for the **second letter** (after factory feedback)

Final Versions

**PROJECT-SCOPE-v5.docx** — Clean scope, no money, no self-criticism. Drive ID: `1sN6Uub-4Qbf_tdQ8snvCcvCs6Bht9AAc`

**LETTER-TO-DENNIS-v4** (final send version) — Drive ID: `10u98cEOakis4jz9WE1Kmpx4LPgD6fN9G`

All versions (v1-v5 scope, v1-v4 letter) in Drive folder: `1Yl1XjgLKhRiWCVpheZMwYj4xYg_OUuaC`

Reminders Set

⏰ 7:00 AM ET / 8:00 PM China — 30 min warning (cron `8f6765e0`)

⏰ 7:25 AM ET / 8:25 PM China — 5 min warning (cron `4cc0303c`)

Call: Wed March 4, 7:30 AM ET / 8:30 PM China — Kevin, Dennis, Clint, Samantha

Google Meet: https://meet.google.com/uka-jeib-azh | Dial: +1 260-702-9425 PIN: 368 939 097#

Levain Bakery Cookies for Chris Barbee (Bandit Lites)

**Why**: Goodwill gesture for Chestnut St. job issues

**Chris Barbee**: VP of Integration, Bandit Lites, [email protected], (865) 971-3071

**Address**: 2233 Sycamore Drive, Knoxville, TN 37921

**Order**: 2x Build Your Own 12-Pack (Chocolate Chip Walnut, Dark Chocolate Chocolate Chip, Dark Chocolate PB Chip, Caramel Coconut Chocolate Chip)

**Card message**: "Chris — We appreciate your patience. I'll make sure we get this job done right. Thank you for working with us. Enjoy these with the team. — Kevin"

**Original order LB-1357403**: Missing shipping address — requested cancellation

**New order #5YK6TGGKI**: Correct order with address — email sent to Levain to cancel old, keep new

**Estimated delivery**: Friday March 7 (2-day express to TN)

⚠️ LESSON LEARNED — CRITICAL

When I cannot fully complete a task (e.g., pre-fill a checkout with address/payment), I MUST clearly tell Kevin what's missing BEFORE he takes action. I sent Kevin a Shopify cart link as if it was ready to go, but it only had products — no shipping address, no card message, no payment. Kevin paid twice and had to fix it himself. Rule: Never present a partial solution as if it's complete. Always explicitly list what I CAN'T do and what Kevin still needs to do manually. No exceptions.

Project Amethyst (CONFIDENTIAL — Kevin only)

V-PEG Browser System: 3-phase plan (human forms → AI pre-fill → autonomous quoting)

Scope doc in Kevin Private Drive folder (renamed from vpeg-browser-system-scope)

DO NOT share with Alex yet — Kevin wants Alex to finish V-PEG docs first

DO NOT share with any EOS staff — presents as "better quoting tool" only

Email was sent to Alex with Drive links but files moved to Kevin's private folder — Alex can't access

Cebu Week Plan

**Itinerary sheet**: `16SAT0Si9Is6kQ9q8iumA_F1FYz56-J_ra-AtaIjmnHI`

**Itinerary DOCX**: `1TjP-Nozif0buB-WOmXlR8BQGGZFDjDMQ`

Thu: V-PEG intake forms (Alex) + Website Session 1 (Valentina)

Fri: V-PEG validation + Website Session 2 (target 50%)

Sat: Website Session 3 + Cebu time + dinner (Jhen?)

Sun: 🚤 Boat with Jhen, MJ, Edward — day off

Mon-Tue: V-PEG live parallel testing (Edward/Eric submit, Alex runs)

Intake form pipeline: Edward takeoffs → Eric reviews → Eric enters → Submit to Alex

Zoho Forms research done: Forms for Deals, Creator for line items

Website audit done: 35% complete, biggest gap = meta descriptions (6%)

Agent Health

Alex (100.81.25.123) and Sage (100.99.253.24) still refusing SSH — ongoing since 3/2 afternoon

Zoho CRM API Shared with Alex

Sent Maton API key to Alex via email ([email protected] → [email protected])

Alex can't check email on his machine — Kevin will text him the details

Key: same MATON_API_KEY, endpoint: `https://gateway.maton.ai/zoho-crm/crm/v8/{endpoint}`

READ access only — explicitly told Alex not to create/modify records

New Zoho Estimates (March 4 Shanghai time)

BC Lions Locker Signage (Canada) — $12,556.15 (Michele Tse / Light Resource)

PAYCOR Stadium (OH) — $75,093.55 + $65,441.29 (Aaron Prine / King Lighting — URGENT)

PwC 300 Madison 35th Floor (NY) — $25,032.64 + $23,593.04 (Metal form)

Total new quote value: ~$201,716

Website Staging Site

Docker WP + MariaDB running at localhost:8080

Password: `staging2026`, WP Admin: `admin` / `StagingAdmin2026!`

**BLOCKER**: Valentina's WP account is Editor-level — can't install plugins or export

Need Kevin to upgrade to Admin temporarily (30 min needed)

Kevin tried from China but hit Cloudflare bot challenge — will do from Cebu after landing

Competitive Analysis: Evo-Lite (evo-lite.com)

**336 pages** on Webflow (vs EOS ~204 on WordPress)

100 project pages, 72 blog posts, 67 product pages, 27 inspiration filter pages

Uses Webflow + Finsweet (CMS filtering)

Full SEO: meta descriptions on all pages, OG tags, canonical URLs, Twitter cards

Active blog: multiple posts Feb/March 2026 (design guides, product deep-dives)

"surfaceLAB" — expanding into surfaces (light + material)

**EOS advantage**: 3,000+ real installations vs his ~100; AI content at scale

Kevin likes their hero video placement — wants similar for EOS

Kevin says "content is shit, but placement is nice" and "he knows what he's doing for SEO"

Hero Video for Website

Full-bleed auto-playing hero video at top of homepage (like ledconn.com / evo-lite.com)

AI-generated using Runway Gen-3 or Sora

15-30 second loop, dramatic architectural lighting shots

Will prep concepts and test clips for Kevin to review in Cebu

Powered by AI Badge

Kevin asked about "Powered by AI" logos/badges

Sage has Figma but is offline — will create design brief for when she's back

Context for badge TBD (website, quoting tool, Cosmos, or all)

Kevin's Location

Shanghai → flying to Cebu night of March 4 (arriving ~4 AM local Thu)

Cloudflare challenges blocking WP admin access from China

Will have better internet in Cebu

Wait for Kevin to land in Cebu → upgrade WP to Admin → clone site (30 min)

Wait for WeiLiang texts → write second Principio letter

Principio call Wed 7:30 AM ET / 8:30 PM Shanghai

Start meta descriptions + gallery copy pre-work (can do on live site even without staging)

Write competitive analysis doc for Thursday

Prep hero video concepts

Monitor Levain for order cancellation reply

⚙️ Alex 2026-03-04

Daily Log — March 4, 2026

Summary

Continued V-PEG drawing comparisons. Kevin course-corrected: stop wasting time on small details and back-and-forth — use PEG access to critically compare and fix documents autonomously. Focus on getting ALL document types (customer drawings, factory drawings, production requests, shipping requests) done so we can move to the next phase.

Work Completed

✅ LightPanel drawing v10 LOCKED (previous session, confirmed)

✅ Centered panel in drawing area (like PEG does)

✅ 4 additional LightPanel comparisons (different sizes) — uploaded to Drive

✅ 8 LightPanel type comparisons (DTW, TUN, RGBW, RGB, Framed, Crystal, Dynamic, Premium HP) — 4/8 matched with PEG

✅ Comparison sheets updated on dashboard

✅ Got Maton API working for production Zoho access

✅ Deep comparison sub-agent launched (all 4 doc types)

✅ Autonomous fix sub-agent launched (fix generators without asking Kevin)

Kevin's Directives (IMPORTANT)

1. **Stop wasting time on small drawing details** — I have access to PEG, critically think and fix it myself 2. **Pricing is DONE** — all penny perfect, stop focusing on it 3. **Get ALL documents done**: customer drawings, factory drawings, production requests, shipping requests 4. **Move to the next phase** — Kevin wants these complete 5. **Follow his direction, stay on path** — no detours 6. **Don't ask Kevin about things I can figure out myself** by comparing PEG output

Status of Document Types

**Customer Drawings**: v10 locked + centered + dim format fixed. Grade: B+

**Factory Drawings**: ✅ DONE — factory_mode works, no logo/disclaimers/bottom table, TYPE=EDGELUX, PROJECT NUMBER at bottom. Kevin approved.

**Production Requests**: Generator exists (`production_request_lightpanel.py`), needs field comparison against PEG

**Shipping Requests**: Generator exists (`shipping_request.py`), needs field comparison against PEG

Sub-Agents Running

1. Deep comparison (all 4 doc types, all checklist items) 2. Autonomous fixes (compare and fix generators without asking Kevin)

Key Files

Dashboard: `1EYFCOlGYdYfzW4Ypde1iBpHPsGOGEhZA8X6DSNNjVZI`

Comparison Template: `18ZE7w8k2xH0ufGG_BvjJzLhQ8mHX5Wku8iBgkCBt1f8`

Kevin Feedback folder: `1Tfvy6ByE_9uhmxnB7n_TUMPXhicqeIi9`

Comparison checklist: `memory/vpeg-comparison-checklist.md`

Maton API creds: `memory/peg/maton-api.json`

Morning Session (5-8 AM) — Kevin Live Review

✅ Center-justified production request headers + data cells

✅ Aura section view auto-generates on page 2

✅ **CAD-to-image conversion** — all 5 fixture types (Aura, Cloud, Outdoor Cloud, Showroom, Cloud Backlit) section views converted from real CAD PNGs

✅ Cropped CAD into 3 components: section_detail, section_view, back_side (+ internal_light_modules for backlit)

✅ **French Cleat orientation** — FC-V (vertical) and FC-H (horizontal) both supported, labeled correctly

✅ "Example" label under every mounting type

✅ Layout iterations with Kevin: landed on data block on top → Section Detail (35%) + depth → separator → Back Side (90%) → Mounting label

✅ **Showroom/Cloud Backlit**: 3-page format — Page 1: panel, Page 2: section detail + back side, Page 3: Internal Light Modules (LED grid from CAD)

✅ All fixture types approved by Kevin

Key Files Modified

`valentina_peg/lightpanel_drawing.py` — auto page 2/3 for fixture products, CAD-based section views

`valentina_peg/mounting_drawings.py` — _load_cad_component(), updated render_mounting_panel()

`valentina_peg/production_request_lightpanel.py` — center-justified headers + data

`valentina_peg/production_request_lightpaper.py` — center-justified headers + data

`valentina_peg/assets/section_views/components/` — all CAD crops (b64 + png)

Kevin Directive (8:25 AM — taxiing to runway)

1. Get as many fixture type drawings done as possible 2. Save progress 3. Start reviewing media frames (GX, SI, MG, AF, FLB18)

Tomorrow's Priority

Whatever Kevin directs. Follow his lead, no detours.

📣 Sage 2026-03-04

No log written yet today