The initiative page
One page per initiative: the description, the plan, and its history in order, from who defined it through each run and the pull request it opened.
One column holds the description, the implementation plan and the activity; a rail beside it holds status, ranking, the pull request, dependencies and source documents. The status control in the rail is the one place an initiative moves between Queue, Todo, Backlog, Done and Canceled, and Queue is still the only way to get it planned.
The activity is the initiative's history in order. Who defined it, who changed the title or description and what changed, who moved it between columns, when an agent planned or built it, and which pull request each run opened and when it merged. Every run is listed with the way into its log. Edits read one per field, and consecutive moves fold into one line.
A finished, canceled or archived initiative is read-only; its description, dependencies and documents stay as the record of what was built, and reopening is the only action left. While a plan waits for Approve or Reject the description is locked, so the verdict is about the plan you read. Deleting mid-build stops the run first.