Decisions Tab
The Decisions tab surfaces project-setup gaps that need a human call. These aren't tracked items in the usual sense — they're missing actions the system has detected by analyzing your projects, calls, and signals.
Decision Kinds
| Kind | Surface | Primary Action |
|---|---|---|
| Customer ask | A customer signal that doesn't link to any active project | Create project (with customer pre-filtered) |
| Scoping | A project that lacks a scoping description | Draft scoping (AI drafts from signals) |
| Product area | A project not mapped to your taxonomy | Set project area (AI suggests area path) |
| Call routing | A call that belongs with an existing project but isn't attached | Attach call |
| PR review | A stale PR waiting on a human reviewer | Open PR |
The List
The left pane groups decisions by project where applicable and ranks them by score. The score is computed from customer value, severity, volume, and recency. Higher score = more urgent.
The Detail Pane
Click any decision to open it. Each detail shows:
- Why it's here — the factors that produced the score (customer value, severity, volume, recency)
- Action card(s) — primary button (kind-specific), sometimes a secondary "Dismiss"
- AI-suggested resolution — for area and scoping decisions, a preview of what the AI would set
- Project context — type, status, signal count
- Linked signals — full source list with contact, company, source, and date
Preview → Apply for AI Suggestions
For project-area and scoping decisions, the agent offers a draft you can accept.
1. Open the decision
The detail pane loads context and asks the AI for a suggestion.
2. Review the preview
For project-area: a proposed taxonomy path (e.g., Features > Search > Filters).
For scoping: a drafted scoping description in markdown.
3. Apply or refine
Click Apply to write the suggestion to the project, or dismiss it if it doesn't fit.
How Decisions Disappear
A decision is removed when the underlying gap is filled:
- Customer ask → resolved when a project is created with this customer linked, or the signal is attached to an existing project
- Scoping → resolved when the project has a scoping description
- Product area → resolved when the project has an
areaPath - Call routing → resolved when the call is attached to a project
- PR review → resolved when the PR has a human reviewer (not just Codex)
Tip: Decisions and Signals can coexist for the same project — a project can be missing a scoping description AND have inbound customer signals at the same time. Work them in priority order.