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.
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: Mar 03, 2026 at 03:03 PM ET
🎯 Valentina 2026-03-03
NovaStar Factory Test — Shanghai (3/3/2026, 12:00-3:00 AM ET)
Status: IN PROGRESS
Kevin at Shanghai factory with engineers, testing remote LED screen management
**Hardware**: NovaStar TB60 (Taurus-00004669), IP 192.168.41.1, 6 LED modules (320×160mm)
**VNNOX Cloud Publishing**: Credentials gtzsc / 3nd8r7 (China server). Status: binding attempted, initially failed due to no internet, then ethernet connected
**VNNOX Care**: Already bound under username "Shleike" on care.novaicare.com
**VNNOX China servers NOT accessible from US** — api-cn.vnnox.com blocked from NYC Mac Mini
Remote Access Saga
ToDesk installed: Code 382 762 067 / Pass 7ueuvx06 — BUT ToDesk is China-only, can't connect from US
Switched to **AnyDesk**: Address **1 480 323 875** — installed on both sides, connection attempted, waiting for engineers to accept
Factory laptop: Huawei, Windows, has NovaLCT V3.0.0.4.2001
Engineer Feedback
Color calibration can't be done remotely (needs colorimeter on-site) — valid point
Dead LED detection CAN be done remotely via screenshots
Module swap with flash-stored calibration data should auto-correct color
Key Lesson
ToDesk = China-only remote desktop. Use AnyDesk or RustDesk for international connections
VNNOX China servers (api-cn.vnnox.com) not accessible from US
Factory internet was a challenge — TB60 needed ethernet, WiFi wasn't initially available
EOS Building Blocks — New Product
Kevin created new product: EOS Building Blocks (积木式背光板)
Universal pre-fab LED backlight panel for stone fabricators
1/2" cast acrylic substrate with laser-cut LED pockets, pre-wired, field-cuttable
/workspace/eos-building-blocks/EOS_Building_Blocks_Factory_Brief_CN.pdf — formatted PDF with Chinese chars (weasyprint)
Installed
weasyprint (pip3) — for generating PDFs with CJK characters
AnyDesk (brew cask) — for international remote desktop connections
AnyDesk Connection Progress (3:15 AM ET)
AnyDesk installed on Mac Mini via brew: `/Applications/AnyDesk.app`
Factory laptop AnyDesk address: **1 480 323 875**
Mac Mini AnyDesk address: shows as 1 480 323 875 in their recent sessions (green dot = online)
Connection established but needs acceptance — trying reverse connection (factory → Mac Mini)
AnyDesk on Mac Mini may need Accessibility permissions to fully function
**Key lesson**: ToDesk is China-only, doesn't work internationally. AnyDesk works cross-border.
**Key lesson**: Engineers connected to themselves creating infinite mirror — had to tell them to stop touching things
⚙️ Alex 2026-03-03
No log written yet today
📣 Sage 2026-03-03
No log written yet today
🎯 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
运营费用 = 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
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)
Embeds Alex's two Google Sheets (Comparison Template + KPI Dashboard)
Kevin approved deploying under `training.pegaroo.net` — need DNS access later
Built by sub-agent in 2 min, deployed to Cloudflare Pages
Kevin's Requests Organized
1. ✅ Titans quote — group 9354 ready, drawings working, holding on Zoho send
2. ✅ Training dashboard — deployed to eos-vpeg-training.pages.dev
3. ⏳ Gmail OAuth fix — gave Kevin step-by-step instructions (gog auth login)
4. ❓ Checklists review — Kevin started to mention but cut himself off, needs follow-up
Agent Health
Alex (100.81.25.123): SSH connection refused
Sage (100.99.253.24): SSH connection refused
Both unreachable since ~1:31 PM — Kevin not yet alerted (not urgent)
End of Day Status
**Nashville Titans PEG rebuild**: ✅ Group 9354 created, drawings working, ready for Zoho
**Nashville Titans color changes**: ✅ COMPLETE (groups 8922 + 9351 + 9354 all RGB+W 3000)
**Customer layout PDF edits**: ❌ NOT STARTED (can proceed now that drawings work)
**V-PEG monitoring**: ✅ Active via heartbeat (3/3 penny perfect — added 50 Hudson Yards)
**V-PEG training dashboard**: ✅ DEPLOYED (eos-vpeg-training.pages.dev)
**Gmail API**: ❌ Still down (unauthorized_client since ~10 AM, 8+ hours)
**Cosmos deliverables**: ✅ All complete and on Drive
**Alex/Sage agents**: ❌ SSH unreachable since 1:31 PM
⚙️ Alex 2026-03-02
Daily Log — March 2, 2026
Summary
First day of live V-PEG comparison pipeline. Kevin directed real-time quote testing against live PEG. Set up monitoring with Valentina, ran 3 quotes penny-perfect, built tracking infrastructure.
Work Completed
1. **Live Comparison Pipeline** — Valentina monitors Zoho for new estimates, forwards specs, I run through V-PEG pricing engine
2. **3/3 Penny Perfect Pricing**:
- E28482 Lucien Way: Framed LP J2 36×36, $640.99 ✅
- E28480 Dean's Restaurant: AURA Stone 87.125×25, $1,584.83 ✅
- E28483 50 Hudson Yards: AURA Frame 4×46 qty 123 (QD2), $386.32 ✅
3. **PEG Operator Access** — Kevin created user "Alex Quoter / Topsail" for quoting and drawing downloads
4. **Cloudflare Whitelist** — Kevin set up Skip rule for IP 72.229.59.214 on pegaroo.net (order=First, skip all rules)
5. **PEG Drawing Downloads** — Successfully pulling customer/factory drawings from live PEG via operator login
6. **V-PEG Comparison Checklist** — Built comprehensive checklist per Kevin's directive (drawings, codes, names, wattage, drivers, Zoho sync)
7. **Google Sheets**:
- Comparison Template: https://docs.google.com/spreadsheets/d/18ZE7w8k2xH0ufGG_BvjJzLhQ8mHX5Wku8iBgkCBt1f8
- KPI Dashboard: https://docs.google.com/spreadsheets/d/1EYFCOlGYdYfzW4Ypde1iBpHPsGOGEhZA8X6DSNNjVZI
8. **V-PEG Drawings Generated** — Created customer drawings for Lucien Way and Dean's Restaurant
Decisions Made
Kevin: V-PEG comparison is not just pricing — compare EVERY detail (drawings, product codes, names, wattage, drivers)
Kevin: Build V-PEG drawings to "equal or better" live PEG for ALL fixtures
Kevin: Dashboard with KPI tracking, A-F grading system
Kevin: Cloudflare page under pegaroo.net for internal dashboards (password protected)
Kevin: Team won't manually email quote details — must be automated via Zoho monitoring
29504 SHOWROOM: Missing LED module grid, missing SHOWROOM-specific fields (COLOR FRAME, PERFORATED METAL COLOR, ORIENTATION, TRIM COLOR, FINISH), thickness should be 3.6" not 0.375"
29513 Factory Drawing: LightPaper text at bottom ("TS cuts / EL cuts") — wrong for LightPanels. Factory drawings should be borderless, no bottom table, no logo. TYPE should be AF29 not EDGELUX.
Sharp corners rule: ALL panels sharp. No rounded corners unless explicit radius dimension.
Tomorrow's Priority
1. Deep drawing comparisons — pull PEG drawings, compare every element per checklist
2. Process E28484 (USTA Arthur Ashe, 8 line items)
3. Start filling in comparison template sheets for each quote
4. Begin grading drawings per A-F system
5. Continue monitoring for new quotes from Cebu team