---
title: "AI Operations"
area: platform
order: 2
lastUpdated: 2026-05-14
updatedBy: Codex
---

## Use This Doc For

- `/platform/ai`
- `/platform/ai/capacity-continuity`
- `/platform/ai/operations`
- `/platform/ai/operations-map`
- `/platform/ai/capability-needs`
- `/platform/ai/history`
- `/platform/ai/assignments`

## Workflow

1. Start with the current operating picture: health, recent activity, operations-map posture, and assignment posture.
2. Review Capacity Continuity when paid AI capacity is idle, blocked, or expected to keep working during holidays, vacations, business events, after-hours windows, or owner inactivity.
3. Review Capability Needs when coworkers surface missing tools, prompts, permissions, or product gaps that need governed follow-up.
4. Review history when a result looks wrong, slow, or inconsistent.
5. Adjust assignments only after you understand whether the problem is role design, model selection, tool access, standing orders, or calendar state.

## What To Watch

- work being routed to the wrong specialist
- paid AI capacity going unused without a clear blocker
- repeated retries or stalled history patterns
- assignment changes that solve one route but weaken another
- capacity work that produces token spend without durable evidence, backlog movement, or reviewable output
- capability needs without submitter context, route context, or a clear backlog follow-up
