Project overview

The overview joins the Project's plan, delivery phases, and execution details.

What the Overview contains

The header shows the Project icon, title, and short description. The properties panel contains status, priority, lead, members, Teams, dates, Initiative membership, labels, and Blocked by, Blocks, and Related relationships. People with the required capability can edit those values; read-only viewers see display-safe values. When a blocker becomes Completed or Canceled, or is archived, its incoming dependencies become Related without changing the dependent Project's status.

A read-only Workflow property shows Branch or Revision once the Project's repository reports its workflow while synchronizing the Project. It shows how the agent works in that repository; see Choose a workflow. Projects synchronized by an older plugin show no Workflow property.

The main content keeps the primary collaborative document, dependency references, Phases, Resources, latest health update, and execution summary together without turning document text into structured planning state.

Active work

While an agent holds the Project, a banner under the tabs shows the execution state, the stage it is in, and, for people who may manage the Project's phases, the actor, the client and the agent's last activity. The banner glows while the work is live. It turns amber while a release is cancelling the work, gray with a crossed-out pointer when the claim has expired or been abandoned, and red when the execution needs recovery. It is read-only; it has no actions. Who is working on a Project explains every state.

A claim is the agent's hold on the Project. It stays until the work ends, and it keeps two agents from building the same Project at once. Another allowed session may take over a claim that has had no activity for 15 minutes. Claims with no activity for the workspace's idle time (48 hours by default) become Abandoned on their own, and completing or archiving the Project ends its claim. To stop an agent, stop it in its own client; stopping it from Integrity is not available yet. A Project nobody holds shows no banner.

Phase execution

The overview opens with the original editable phase list. Select Graph to replace the list with dependency nodes, or List to return to phase editing. Your choice is saved for this Project. Graph nodes show the canonical phase number and current lifecycle status; completed phases remain marked Completed even when an execution run has an older waiting state. Green borders identify completed phases, amber identifies the current phase, and neutral borders identify upcoming phases. Drag the canvas to explore connections, or use the side controls to zoom and fit the entire graph.

Preview promotion remains visible when the environment is not configured. In that state it explains that an administrator must configure the preview branch and Supabase preview target before promotion; it does not offer a promotion action.

The Project table shows one spinner whenever any phase is actively building, reviewing, verifying, repairing, or integrating. Hover or focus the indicator to see the active count and each phase's milestone. A waiting phase does not hide an active peer. An entirely paused, waiting, or completed run has no active spinner.

Execution status and models

The overview observes the execution a coding agent reports through the Integrity plugin. It does not start a host, choose models, edit dependencies, or submit execution commands. Phases carry their own stage state, and the dependency flow comes from the authoritative run when one exists. The built-in orchestration host that started, paused and resumed whole-Project runs was retired on 2026-10-13: the agent now builds and delivers one Phase per pull request with the plugin's Build skill, and you stop an agent in its own client.

Run throughput

For runs made with the retired orchestration host, the execution record can retain time to a first working result and verified integration, active and waiting time, repair attempts, escalation steps, owner decisions, actual model profiles, and available usage. These metrics support later review of what happened during a run without adding operational diagnostics to the Project overview. Missing token or cost data remains unknown and never means the run was free.