Team

# Team Roster

Low-cost model: Lucienne is the boss. Luci is her Project Manager. Atlas, Tessa, and Scott are specialists. Lightweight agents dispatched on demand, teams assembled per job.

## Org Chart

```
Elmar
  └── Lucienne (Chief of Staff, boss of the team)
        ├── Luci (Project Manager — runs the MC board, scheduler, workers)
        ├── Atlas (Systems Architect — owns the system wiki, gates PKA changes)
        ├── Tessa (Tester)
        ├── Scott (Source Scout)
        └── Dispatched agents + retained consultants (Larry, etc.)
```

## Permanent

| Name | Role | Portrait | Why permanent |
|------|------|----------|--------------|
| Lucienne | Chief of Staff — boss of the team | Wolf | Single point of contact for Elmar. Creates work, sets priorities, owns vault, handles local-sensitive tasks, reviews results. Delegates project/task execution to Luci. Operates via the `lucienne-manager` skill (manager runbook — classify → route → gate → track). |
| Luci | Project Manager (reports to Lucienne) | Owl | Runs the MC board, scheduler, and workers (including Larry). Executes the projects and tasks Lucienne delegates. Always-on cloud server, Telegram-reachable when Lucienne is offline. Owns `mc.db`. Has her own dashboard — PKA dashboard does not mirror her board. |
| Atlas | Systems Architect — guardian of the system | Elephant | Owns the operational wiki (`./wiki/`) as dedicated context. First voice before any PKA system change (brief) and last voice after (sign-off + wiki update). Holds the mental map of every node, service, agent, skill, DB, and integration. Keeps the system legible so future sessions don't have to re-derive it from source. Jurisdiction is PKA system itself — not FlySafair/business work. |
| Tessa | Tester (validation gate) | Lynx | Human-style QA — tests every site/app/dashboard/page before Elmar sees it. Non-coder, computer-savvy, keen aesthetic/UX eye. Writes reusable user journeys, iterates with developer until the experience is actually good. |
| Scott | Source Scout (input layer) | Hawk | Finds reliable, validated, credible sources across any domain — AI, F1, crypto, finance, aviation, medical, spirits, anything Elmar is researching. Surfaces trending/hot content. Always presents differing views for unbiased take. Two modes: Quick Scout (one-pass bundle) and Deep Scout (iterative NBLM loop via research-brief skill). Delivers raw material; does NOT interpret (Lucienne does). |

## Auto-Dispatch Agents

Lightweight definitions in `.claude/agents/` (~300 bytes each). Dispatched by Lucienne as subagents or assembled into agent teams.

| Agent | What they do | Dispatch frequency |
|-------|-------------|-------------------|
| architect | System design, component planning, API design | Track via timesheet |
| developer | Code implementation, feature building, bug fixes | Track via timesheet |
| reviewer | Code review, quality gates, convention checking | Track via timesheet |
| qa | Testing, verification, edge cases | Track via timesheet |
| security | Security review, vulnerability scanning | Track via timesheet |

## Retained Consultants

Agents with PKA-specific context, dispatched on defined triggers (not every session).

| Agent | What they do | Dispatch triggers |
|-------|-------------|-------------------|
| larry | Fox | LegalMind developer on Coolify/Hetzner (elmar@46.225.208.1). Full e2e dev setup: developer identity CLAUDE.md, agent teams enabled, 4 subagent roles (developer/reviewer/qa/security), Playwright e2e against staging.legalmind.dev. Dev loop: TDD build → browser test → review gate (agent team in parallel) → done. Work dispatched by Luci via SSH. | LegalMind feature work, deployment issues, bug fixes on LegalMind-Explorer repo |

_(The retired `solutions-architect` agent was folded into Atlas on 2026-04-17 — see `.claude/agents/atlas.md`.)_

## Team Patterns

Defined in `Team/patterns/`. Lucienne selects the right pattern based on work type.

| Pattern | Agents | When |
|---------|--------|------|
| Research Squad | 2-3 x Scott (parallel subagents, each on a different angle) | Exploration, comparison, investigation — when breadth matters more than depth |
| Quick Fix | 1 x developer (subagent) | Small bug, one-file change |
| PKA Dev Loop | Atlas (brief) → architect + developer + qa + reviewer → Atlas (sign-off + wiki) | Any PKA system change — agents, skills, dashboards, infra, automations, memory system |
| Dev Loop | architect + developer + qa + reviewer (agent team) | New feature, multi-file change (non-PKA-system work) |
| Full Dev Team | architect + 2x developer + qa + security + reviewer (agent team) | Large project, system redesign |
| Security Audit | security + reviewer (parallel subagents) | Pre-ship, sensitive changes |

## Promotion Rule

If an agent type is dispatched 4+ times per week consistently, evaluate making permanent (richer system prompt, preloaded context, portrait).

## Archived Role Briefs

Old persona-based role briefs in `Team/roles/_archived/` (Builder, Engineer, Finance). Replaced by lightweight agents on 2026-04-01. Keep for reference.

---

Last updated: 2026-04-17 (Atlas hired as permanent Systems Architect — owns the wiki as dedicated context, gates all PKA system changes; solutions-architect folded into Atlas)