DOMAIN-CONTEXT.md - Shared Context for All Domains
Last Updated: 2026-02-16 22:45 UTC
Purpose: Provide current priorities and active projects to all domain sessions
Current Week Priorities (Feb 16-22)
Critical This Week
- Paula's maternity leave policies - Philippine law + team transition plan created
- Carmee design onboarding - 30-day plan ready, needs Jedi Council review
- Telegram domain architecture - 8 groups initialized (Strategy, Ops, Finance, Team, Infrastructure, Support, Daily, Quantitative)
- Steve FL shipment tracking - 9 packages in transit, target delivery Wed Feb 19
Blocked/Waiting
- Gmail OAuth - Day 3 offline, blocking email visibility
- Weather API - wttr.in timeout day 3
- RMA outsourcing - Valencia contact needed, Jerry window closing
Active Projects
Phase 1: Foundation (Feb 16 - Mar 15)
- Carmee pathway automation - Target 20-30% reduction by Mar 15
- Charlie admin automation - Minnie takes over 8-10 hrs/week
- Valencia fulfillment prep - RMA/shipping handoff
Phase 2: Soft Launch (Mar 16 - Apr 10)
- Paula maternity leave - Starts ~April 7
- Design handoff to Carmee - 2-4 weeks knowledge transfer
- Social media coverage - Team training
Phase 3: Paula's Leave (Apr 11 - Jun 30)
- 12-week maternity leave - Team maintains baseline
- Carmee design ramp-up - 3-5 projects by April 15
Escape Velocity Metrics
Current ROI: 15x (6 hrs/week saved, $240-350/month cost)
Target for Tier 2: 20-30x (25 hrs/week saved)
Loss Function Priority:
- Vitality (skiing, movement)
- Relational (Charlie time, environment)
- Sovereignty (deep-work, conflict debt)
- Business (only after above protected)
Key Constraints
Charlie's release: Finance/ops → Vania (NON-NEGOTIABLE)
Carmee capacity: AT CAPACITY, pathway automation must deliver before design work
Jerry window: In US THIS MONTH, RMA documentation urgent
Rebuild discipline: Sunday 9:45 PM PT only
Passport appointment: Tomorrow (Tue Feb 17) 7:30 AM LA
Cross-Domain Escalation Protocol
When to escalate to Main:
- Critical decisions affecting loss function priority order
- Cross-domain dependencies (e.g., Finance blocking Ops)
- Strategic tradeoffs (sovereignty vs capital)
- Urgent issues requiring Quan's attention
How to escalate:
Use sessions_send to agent:main:main with:
- Domain name
- Issue summary
- Why it needs Main coordination
- Proposed options (if any)
Domain Coordination Patterns
Strategy → Operations: Strategic constraints affecting execution
Finance → Operations: Payment holds blocking shipments
Team → Operations: Capacity constraints affecting delivery
Infrastructure → All: System outages affecting workflows
Support → Product: Field feedback requiring design changes
Quantitative → Strategy: Metrics informing strategic decisions
Recent Decisions
Feb 16:
- Telegram group architecture confirmed (8 domains + Main hub)
ackReactionScope: "all" for domain seeding phase (pending restart)- Filipino team maternity leave policy based on Philippine law (RA 11210)
- Team transition plan for Paula's leave finalized
Feb 15:
- Escape velocity tracker created (weekly assessment framework)
- Tailscale + Markdown server operational (100.72.11.53:9876)
- Chinese PDF generation with Noto Sans SC font support
Quick Reference
Main Session: agent:main:main (strategic coordinator)
Telegram Main Chat: Direct messages with Quan
8 Domain Groups:
- Strategy & Vision: -1003723796592
- Operations & Process: -1003745938506
- Finance & Sales: -1003720984736
- Team & Culture: -1003837408316
- Infrastructure & Tech: -1003891773186
- Support & Product: -1003899079628
- Daily Execution: -1003178408980
- Quantitative Analysis: -1003863945301
VPS: 144.202.121.97 (Vultr)
Tailscale: 100.72.11.53 (minnie-core)
Markdown Server: http://100.72.11.53:9876
This file is automatically updated by Main session. Domain sessions: read this on startup for current context.