97 lines
3.5 KiB
Markdown
97 lines
3.5 KiB
Markdown
|
|
|
|
---
|
|
|
|
## 🗄️ Shared Supabase Database - CRITICAL: Table Naming Convention
|
|
|
|
**Rule:** `<project_name>_<table_name>` with underscores (NO hyphens)
|
|
|
|
**Why:** All Vercel apps share one Supabase project to prevent collisions
|
|
|
|
**Current Prefixes:**
|
|
- *(none)* — Gantt Board (legacy - `tasks`, `projects`, `sprints` - no prefix)
|
|
- `blog_` — Blog Backup (messages, tags)
|
|
- `mission_control_` — Mission Control (documents, folders)
|
|
- `heartbeat_` — Heartbeat Monitor (status, logs)
|
|
|
|
**Note:** Gantt Board is the legacy app (no prefixes). All NEW apps MUST use prefixes.
|
|
|
|
**Full doc:** `DB_TABLE_NAMING.md`
|
|
|
|
**Remember:** Always prefix, always underscores, never abbreviate!
|
|
|
|
---
|
|
|
|
## 🚀 Mission Control Future Vision — Voxyz Inspiration
|
|
|
|
**Date Added:** February 22, 2026
|
|
**Source:** X/Twitter Article by Vox ([@Voxyz_ai](https://x.com/Voxyz_ai))
|
|
**Article Title:** *"I Built an AI Company with OpenClaw + Vercel + Supabase — Two Weeks Later, They Run It Themselves"*
|
|
**Article Date:** February 6, 2026
|
|
|
|
### Why This Matters
|
|
|
|
Vox built a **6-agent autonomous company** using the same stack we're using (OpenClaw + Vercel + Supabase). Two weeks after launch, the system runs itself with minimal human intervention. This is the long-term vision for Mission Control.
|
|
|
|
### Vox's Architecture (Reference for Future)
|
|
|
|
**The 6 Agents:**
|
|
- **Minion** — Makes decisions
|
|
- **Sage** — Analyzes strategy
|
|
- **Scout** — Gathers intel
|
|
- **Quill** — Writes content
|
|
- **Xalt** — Manages social media
|
|
- **Observer** — Quality checks
|
|
|
|
**The Closed Loop:**
|
|
```
|
|
Agent proposes idea → Auto-approval check → Create mission + steps
|
|
↑ ↓
|
|
Trigger/Reaction ← Event emitted ← Worker executes
|
|
```
|
|
|
|
**Key Innovations:**
|
|
1. **Single Proposal Service** — One function handles ALL proposal creation (no bypassing)
|
|
2. **Cap Gates** — Reject at entry point (don't let queue build up)
|
|
3. **Reaction Matrix** — 30% probability reactions = "feels like a real team"
|
|
4. **Self-Healing** — 30-min stale task detection and recovery
|
|
|
|
### Application to Mission Control
|
|
|
|
**Short-Term (Now):** Complete Phases 6-9 as read-only dashboard
|
|
|
|
**Medium-Term:** Phase 10 — Daily Mission Generation
|
|
- Auto-propose 3 priorities each morning
|
|
- Smart triggers for deadlines/blockers
|
|
- Simple closed loop: Analyze → Propose → Approve
|
|
|
|
**Long-Term:** Phase 11-13 — Full Autonomous Operations
|
|
- Agents propose and execute tasks
|
|
- Self-healing system
|
|
- You monitor, agents run
|
|
|
|
### Key Lessons from Vox's Pitfalls
|
|
|
|
1. **Don't run workers on both VPS and Vercel** — Race conditions
|
|
2. **Always use Proposal Service** — Never direct inserts
|
|
3. **Implement Cap Gates early** — Prevent queue buildup
|
|
4. **Use policy-driven config** — Don't hardcode limits
|
|
5. **Add cooldowns to triggers** — Prevent spam
|
|
|
|
### Research Notes
|
|
|
|
**Open Questions:**
|
|
- Should Matt's agents have "personalities" or stay neutral?
|
|
- How much autonomy vs. human approval?
|
|
- What happens when agents disagree?
|
|
|
|
**Next Research:**
|
|
- Follow [@Voxyz_ai](https://x.com/Voxyz_ai) for updates
|
|
- Look for more implementation details beyond the article
|
|
- Study OpenClaw autonomous agent patterns
|
|
- Search for "OpenClaw closed loop" or "agent operations"
|
|
|
|
**Full Plan Location:**
|
|
`/Users/mattbruce/Documents/Projects/OpenClaw/Documents/Mission-Control-Plan.md`
|
|
|
|
**Remember:** This is the **North Star** — the ultimate vision for Mission Control. But short-term focus is completing the dashboard first (Phases 6-9). |