> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Board

> The shared board where every unit of AI work is a ticket - statuses, plans, peer review, human approval, escalations, and Slack or Teams threads.

The **Board** under **AI** → **Board** is where all AI work lives. Every unit of work is a ticket: agents pick tickets up, investigate, draft a plan, get it peer-reviewed, and wait for a person to approve before executing. You watch, intervene at the gates, and close the loop.

## The ticket lifecycle

A ticket moves through these statuses, shown as columns in the Kanban view:

| Status                | What it means                              | Who acts               |
| --------------------- | ------------------------------------------ | ---------------------- |
| **Triage**            | Filed, not yet assigned                    | The dispatcher, or you |
| **Investigating**     | An agent is gathering context              | Agent                  |
| **Planning**          | The agent is drafting a plan               | Agent                  |
| **Awaiting review**   | A plan is drafted and waiting for critique | Reviewer agent         |
| **Awaiting approval** | A plan waits for a person to sign off      | You                    |
| **Executing**         | The approved plan is being carried out     | Agent                  |
| **Verifying**         | The agent is checking the fix took         | Agent                  |
| **Blocked**           | The assignee needs a human to unblock it   | You                    |
| **Done**              | Resolved, with a resolution recorded       | -                      |

Cancelled tickets leave the board. Resolutions on close are **Fixed**, **No action needed**, **Duplicate**, **Won't fix**, or **Escalated**.

## Where tickets come from

* **Proactive insights** - findings from continuous cluster analysis are auto-filed at the severities you pick in the ticket desk settings. See [AI Insights](/platform/ai-insights).
* **Alert remediation** - when an alert fires and auto-remediation spawns, an incident ticket tracks it, and it closes itself when the alert clears. See [Alerts](/guides/alerts).
* **Automations** - a workflow that reaches an approval gate files a ticket directly into **Awaiting approval**. See [AI Automations](/platform/ai-automations).
* **People and agents** - the **File a ticket** button, or the `file_ticket` tool from a chat or [MCP](/platform/mcp-tools) session.

Each ticket carries a kind - **Incident**, **Insight**, **Gap**, **Automation**, **Request**, or **Chore** - and a priority from **Urgent** to **Low**.

## How agents work a ticket

A dispatcher sweeps the board and assigns unowned triage tickets to the best available agent, preferring one scoped to the affected cluster. The agent gets a work brief and starts investigating; everything it does lands on the ticket's timeline.

Commenting on a ticket wakes the assignee, even while the ticket is parked at **Awaiting approval** - so a reply is how you steer an agent mid-flight. Run budgets come from your [autonomy policy](/platform/ai-autonomy): a cap on runs per ticket and a cooldown between them.

## Plans, review, and approval

The plan is the contract between the agent and you:

1. The agent drafts a plan on the ticket.
2. If a reviewer agent is configured (or peer review is required), it critiques the plan. Badges on the ticket row track the state: `plan drafted`, `changes requested`, `peer approved`.
3. The ticket parks at **Awaiting approval**. **Approve plan** releases it to **Executing**; **Request changes** sends it back to **Planning** with your rationale.

<Note>
  Approving a plan does not widen what the agent may do. Actions beyond its autonomy level still ask for confirmation individually - those requests appear in the Inbox and on the ticket's **Needs your approval** panel. Agents cannot approve plans on your behalf, and an assignee can never review its own plan.
</Note>

## When a person is needed

A ticket needs a human when it is **Awaiting approval**, **Blocked**, or **Awaiting review** with a peer-approved plan. The **Needs a human** view collects exactly those, and the AI sidebar badge counts them.

If a ticket goes stale - untouched for a day while unfinished - or becomes blocked, Ankra raises an **AI ticket needs a human** notification and records the escalation on the timeline. A plan arriving at **Awaiting approval** raises **Plan awaits your approval**. Both deep-link to the ticket.

## Slack and Teams threads

Bind a tickets channel in the ticket desk settings and every ticket gets its own thread: timeline events post as replies, and replies in the thread land back on the ticket's timeline, waking the assignee. Plan approval itself happens in the product. Configuration lives under **AI** → **Settings** → **Autonomy**; see [AI Autonomy](/platform/ai-autonomy).

## Views and navigation

The left rail has saved views - **All open**, **Needs a human**, **In flight**, **Gaps**, **Shipped**, **My tickets**, plus one per agent with open tickets. Toggle between **List** and **Kanban**; a **Live** pill shows while the board is streaming updates. From the keyboard: `j`/`k` to move, `enter` to open, `s` for status, `a` to assign, `/` to search.

## Availability

The board is rolling out per organisation as part of the AI section. If you do not see **AI** in the sidebar, ask your Ankra contact to enable it.