# Tracker

> Source: https://whisperer.one/llms/tracker.md · Whisperer machine-readable layer.
> Product overview: https://whisperer.one/llms/product.md · Full corpus: https://whisperer.one/llms-full.txt

The tracker is the kanban task board inside Whisperer.

## Model

Projects contain columns; columns contain task cards. A card has a title, description, due
date, priority and labels. Columns are the workflow — they are the user's own, not a fixed
set.

## Where tasks come from

- Created directly by the person.
- Created by Leo on request.
- Promoted from a meeting: an action item or a commitment extracted from the transcript
  becomes a card, carrying the meeting it came from as its source.

A task created from a meeting suggestion is filed on the board of that meeting's hub. If the
meeting has no hub, or the hub has no board chosen, the suggestion declines rather than
picking an arbitrary project — a task in the wrong project is discovered late and costs more
than a task that was never created.

## Boundary

The tracker holds work someone owns. An obligation stated on a call is a **commitment** until
a person decides it should be tracked; commitments live in the context graph with their
source, and Leo reminds about them there. Promoting a commitment to a task is a human
decision, which is also why external MCP clients cannot resolve commitments.

## Access from outside

`whisperer:tracker.read` and `whisperer:tracker.write` expose listing boards, creating
projects, columns and tasks, updating and moving them. Deleting projects, columns and tasks is
not exposed to external clients at all.