AI Agent Team — Roster

The management view of the dept-based AI agent team: which depts are chartered, which have an operating agent persona, and at what autonomy level. One row per dept — this is the org chart for KB-OS’s agent layer.

How an agent runs (the charter chain): CONSTITUTION.md → dept JOB_DESCRIPTION.md (policy: scope, decision authority, hand-offs) → Staff/<Role>.md (operating instructions + autonomy) → the task’s SSOT doc. As of 2026-07-09, /task-start and /task-continue auto-load this chain from the task file’s dept path — no manual loading needed.

Core (cross-business)

Dept	Charter	Agent (Staff)	Autonomy	Inbox	Status
AI	JD	AI-Director	A1	Inbox	✅ Active
AI/Tools	JD	Skill-Developer (IC → AI-Director)	A1	Inbox	✅ Active
Processes	JD	Processes-Director	A1	Inbox	✅ Active
IT	JD	IT-Director	A1	Inbox	✅ Active
Cancer50	JD	—	—	Inbox	🔶 Dormant mission anchor

MBR (current business focus)

Dept	Charter	Agent (Staff)	Autonomy	Inbox	Status
Strategy	JD	CEO (Talbot)	—	Inbox	✅ Chartered
Offerings	JD	—	—	Inbox	Chartered, no agent yet
Mktg (+ Content, Viral-Growth, WealthCare50)	JD	—	—	Inbox	Chartered, no agent yet
IT (+ Apps, Data, Processes, Sites, UX)	JD	—	—	Inbox	Chartered, no agent yet
Risks	JD	—	—	Inbox	Chartered, no agent yet

SDC / FSS

Per-task activation — no depts chartered yet. Activate on first real need (/dept-init); do not fabricate scope for a stub dept.

---

Expanding the team (add an agent)

1. Charter the dept — /dept-init scaffolds Tasks/, Inbox.md, etc.; write JOB_DESCRIPTION.md (scope owned, inputs/outputs, decision authority, hand-offs) from an existing one as template
2. Draft the Staff file — <Dept>/Staff/<Role>-Director.md, following the Core/AI/Tools/Skill-Developer.md / *-Director.md pattern: mission, “reads before acting” list, autonomy level, how it works a task
3. Set autonomy — A0 (ask everything) → A1 (draft, CEO approves) → A2 (autonomous within budget) → A3 (within scope) → A4 (within mission). New agents start A1
4. Register — add the row here; Core depts also go in ~/ai-config/AGENTS.md’s dept→charter map and the Core/DASHBOARD.md Active Depts table
5. Dogfood immediately — run a real task through /task-start in the new dept’s Tasks/ folder; gaps show up in use, not review (KB-OS lesson, 2026-06-25)

Autonomy escalation rules

• Globally-deploying commits and changes to the AGENTS.md rules system always escalate to the CEO (Talbot), regardless of dept autonomy
• A dept’s level lives in its JOB_DESCRIPTION.md frontmatter (autonomy:); the Staff file restates it operationally
• A2+ activates only when budget tracking exists — see UPGRADES (Autonomy Levels section)