Feature overview

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

Phase execution

Use Graph to see dependency connections or List for a compact view. Select a phase to inspect its current milestone, attempt, verification evidence, and concrete waiting reason. Arrow keys move between phases; Tab reaches the other controls. The graph scrolls horizontally on a small screen.

The Feature table shows one spinner whenever any phase is actively building, simplifying, 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 is a read-only view of execution started by Codex through the Integrity Build skill and plugin. It does not start a host, launch a shell, choose a repository path, or submit run commands. Open the page to inspect the authoritative run, host identity, model catalogue, progress, and waiting reasons.

The run details show the selected Feature or Phase scope, worker and reviewer models, reasoning levels, concurrency, retry and duration limits. These values are chosen in the approved Build request and remain display-only here. A single-phase Build waits for verified prerequisites and does not start those prerequisites itself. Workers and reviewers share the concurrency limit. Hard token caps are currently unavailable.

The page reports active milestones, verified integration, waiting reasons, and safe interruption states from the canonical run. A run's progress is evidence; a request or host status alone does not prove that work has finished. Use the Codex/Integrity Build workflow for Build, Pause, Resume, or Cancel operations.

Changing dependencies requires the repository plan to be reconciled again. Active affected phases must stop first. Users with approved graph-edit access may edit dependencies in the overview; execution controls and settings editors remain outside the web surface.