Information Architecture

Global shell

┌────────────────────────────────────────────────────────────┐
│ Project switcher / search / global Needs You indicator     │
├───────────────┬────────────────────────────────────────────┤
│ Project nav   │ Main route                                │
│               │                                           │
│ Overview      │                                           │
│ Board         │                                           │
│ List          │                                           │
│ Tree          │                                           │
│ Decisions     │                                           │
│ Plans         │                                           │
│ Settings      │                                           │
└───────────────┴────────────────────────────────────────────┘

The exact visual design can change. The information relationships should stay clear.

Project Overview

Purpose: answer “what needs my attention and what is moving?”

Sections:

• Needs You / Reviews awaiting human action;
• active Tasks and Runs;
• recently completed work;
• project health/agent availability when degraded;
• shortcuts to create Task/Feature/Plan.

Board

Columns use Task status only:

• Backlog
• Ready
• Working
• Needs You
• Review
• Done

Do not create columns for Planning, Agent Review, Verification, or Worktree setup.

Cards can show subordinate badges such as:

• Plan awaiting review;
• Agent active;
• Decision count;
• verification failed;
• review round/revision;
• blocked by dependency.

List

Dense sortable/filterable view for scanning many Tasks. Useful filters include state, Feature, attention needed, agent strategy, and recent activity.

Tree

Shows hierarchy and relationships:

Project
├── Feature
│   ├── Plan
│   ├── Task
│   └── Task
└── Standalone Task

Dependencies are relationships rather than forcing the hierarchy itself into a DAG visualization.

Task Workspace

This becomes the most important route during early development.

Suggested layout:

Task header: status · goal · actions
────────────────────────────────────
Main area                       Side rail
Activity / current work         Acceptance criteria
Review (when applicable)        Decisions
Plan                             Verification
Diff                             Run/environment summary

A tabbed or pane layout can evolve after real usage; do not over-design before the vertical slice exists.

Review Workspace

Primary components:

• candidate revision/base identity;
• diff tree + diff viewer;
• inline/general comments;
• acceptance criteria;
• verification results with revision validity;
• assumptions/claims area;
• previous review round link;
• Request changes and Approve actions.

Plan Workspace

• Plan title/scope/status;
• current immutable revision;
• revision history;
• annotation/review pane;
• submit/reject/approve;
• Feature-plan decomposition preview and confirm flow.

Decision Inbox

Global and Project-scoped filtering. Each Decision links back to the Task/Run/Turn and shows its reason. Resolve from the Inbox when enough context is present; otherwise open the Task.

Agent Run diagnostics

Secondary route/panel with raw/provider-centric detail:

• selected Driver/Instance/Strategy;
• capability/policy snapshot;
• Turns;
• normalized events;
• raw log access;
• external session identity;
• stop reason and delivery errors.

This must not become the primary navigation model.