Files
workspace/team/README.md

54 lines
1.6 KiB
Markdown

# Team — D J's Multi-Lateral AI Company
## Org Chart
```
D J (CEO) 👑
└── Case (CSO) 🖤
├── ARI (Research & Intelligence) 🔷
├── Glitch (Senior Engineer) ⚡
├── Jinx (QA — Functional) 🔍
└── Pixel (QA — Visual) 📸
```
## Roster
| Agent | Role | Emoji | Status | Workspace |
|-------|------|-------|--------|-----------|
| Case | CSO — Strategy & Coordination | 🖤 | Active | workspace/ |
| ARI | Research & Intelligence | 🔷 | Active | workspace-ari/ |
| Glitch | Senior Engineer | ⚡ | Active | workspace-glitch/ |
| Jinx | QA — Functional Testing | 🔍 | Active | workspace-jinx/ |
| Pixel | QA — Visual Testing | 📸 | Active | workspace-pixel/ |
## Pipeline: Build → Test → Ship
1. **Case** defines the task and requirements
2. **Glitch** ⚡ builds it
3. **Jinx** 🔍 + **Pixel** 📸 test it (functional + visual, in parallel)
4. **Case** reviews both QA reports, delivers to D J
For research tasks:
1. **Case** defines the mission
2. **ARI** 🔷 investigates and reports
3. **Case** reviews, synthesizes, delivers
## Delegation Flow
- All tasks flow through Case
- Agents report to Case, not to D J directly
- QA duo (Jinx + Pixel) always test together on engineering work
- ARI operates independently on research missions
## Tasking Format
When spawning agents, include:
- **What:** Clear deliverable
- **Where:** File paths, URLs, ports
- **Context:** Relevant background
- **Output:** What the report should include
## Future Hires (Planned)
- **Creative Cowboy** (TBD) — Internet prospector, finds unconventional money-making opportunities