← back to Ai Workforce

BRIEF.md

32 lines

# ai-workforce — brief

**Seed:** @ScottyBeamIO tweet (2026-07-12) — "a massive Mac Mini farm, each one
running its own Hermes AI agent like a full-time employee… an entire workforce."

- **Client / owner:** Steve (internal; potential productized/sellable concept).
- **Outcome / "high value":** One screen that presents Steve's real fleet as an
  **AI workforce** — machines as offices, agents/services/scheduled jobs as
  full-time employees, each with a role, status, last output, and cost. Turns an
  invisible sprawl of pm2 processes + 150+ launchd jobs + the officer cabinet
  into a legible "org you can look at."
- **Why net-new:** Distinct lens from the existing command centers (AbramsEgo
  :9773 ops P&L, CNCP :3333 flow, cabinet mindmap :9766 static org chart). This
  is the *workforce roster* view — reuses their data (CNCP wins, cost ledger,
  cabinet.yaml) rather than their code.
- **Constraints:** Local prototype only. Basic-auth viewer. **No deploy / DNS /
  public exposure without Steve's explicit go** (accelerator Phase 6 is gated).
- **Reference / inspiration:** the seed tweet; house command-center conventions.

## Data sources (all live, local, read-only)
- `pm2 jlist` — running services → "live employees" (status, cpu/mem, uptime).
- `launchctl list | grep com.steve` — scheduled agents → "shift workers".
- `~/Projects/agent-cabinet/cabinet.yaml` — officer/VP roster → "management".
- CNCP `http://127.0.0.1:3333/api/wins` — today's shipped work → "output".
- `~/.claude/cost-ledger.jsonl` — paid-API spend → "payroll / cost today".
- Mac2 `sysctl` — cores, memory, load → office capacity.

## House-rule compliance
- Admin surface → every employee card shows **created/"hired" date + time**.
- Roster is a grid → **sort control + density slider**, persisted to localStorage.
- All work is local ($0). Deploy is the only gated step and it is NOT taken here.