Initialize CEO workspace with SOPs and Mission Log
This commit is contained in:
@@ -0,0 +1,67 @@
|
||||
# APEX OS — Standard Operating Procedures (SOPs)
|
||||
|
||||
## 1. COMMAND REFERENCE (Telegram)
|
||||
|
||||
| Command | Purpose | Example |
|
||||
|---------|---------|---------|
|
||||
| `/status` | Get full system health and metrics | `/status` |
|
||||
| `/roster` | List all active employees | `/roster` |
|
||||
| `/task [description]` | Assign a task to CEO Agent for decomposition | `/task Research competitor pricing for AI tools` |
|
||||
| `/hire [Role] \| [Task]` | Create a new AI employee | `/hire Content Writer \| Write blog posts about AI` |
|
||||
| `/help` | Show command menu | `/help` |
|
||||
| *Natural language* | Any text routes to CEO Agent | `What's our ad spend this month?` |
|
||||
|
||||
## 2. TASK LIFECYCLE
|
||||
|
||||
```
|
||||
CEO (Telegram) → /task "Build X"
|
||||
↓
|
||||
CEO Agent decomposes into sub-tasks
|
||||
↓
|
||||
Tasks assigned to employees via apex.tasks
|
||||
↓
|
||||
Employee completes → status = 'completed'
|
||||
↓
|
||||
Status Watcher detects change → triggers next step
|
||||
↓
|
||||
When all sub-tasks done → CEO Agent bundles results
|
||||
↓
|
||||
CEO receives Telegram notification with [Approve] [Reject] [Revise]
|
||||
↓
|
||||
On Approve → Engineer deploys or task archived
|
||||
```
|
||||
|
||||
## 3. EMPLOYEE MANAGEMENT
|
||||
|
||||
### Hiring
|
||||
```
|
||||
/hire [Role Name] | [Specialized Task Description]
|
||||
```
|
||||
|
||||
### Monitoring
|
||||
- Grafana Dashboard: http://grafana.apex.unstuck-path.com
|
||||
- Employee Leaderboard shows success rates
|
||||
- P&L panel tracks AI costs per employee
|
||||
|
||||
## 4. EMERGENCY PROCEDURES
|
||||
|
||||
### System Health Check
|
||||
```
|
||||
/status
|
||||
```
|
||||
|
||||
### Manual Recovery
|
||||
```bash
|
||||
ssh root@62.72.3.145 -i <ssh-key>
|
||||
docker ps -a
|
||||
/opt/apex/scripts/auto-recovery.sh
|
||||
```
|
||||
|
||||
## 5. ESCALATION MATRIX
|
||||
|
||||
| Severity | Response | Channel |
|
||||
|----------|----------|---------|
|
||||
| Low | Employee handles autonomously | Logged to reflections |
|
||||
| Medium | CEO Agent coordinates response | Telegram notification |
|
||||
| High | Human CEO notified immediately | Telegram with [Approve] required |
|
||||
| Critical | Auto-recovery + human alert | Telegram + Grafana alert |
|
||||
@@ -0,0 +1,14 @@
|
||||
# APEX OS — Mission Log
|
||||
|
||||
## Mission #1: AD_AUTONOMY_BLUEPRINT
|
||||
- **Date:** Phase 6
|
||||
- **Objective:** Research Meta Ads API and create autonomous advertising blueprint
|
||||
- **Team:** Research Analyst + Marketing Strategist + Engineer
|
||||
- **Status:** Complete
|
||||
- **Output:** AD_AUTONOMY_BLUEPRINT.md (in apex-os-docs)
|
||||
|
||||
## Mission #2: OPERATION AD-READY (Phase 7)
|
||||
- **Date:** Phase 7
|
||||
- **Objective:** Create Meta Ads campaign blueprint for APEX OS itself
|
||||
- **Team:** CEO Agent orchestrating Research + Marketing + Engineer
|
||||
- **Status:** Complete
|
||||
Reference in New Issue
Block a user