Skip to content

Retrospectives

The Retrospectives tab (/reporting/retrospectives?repo=<owner>/<name>) shows what Colony has learned from completed issues in this repository — where implementation scope drifted from plan, how issues resolved, which failure modes recurred, and what candidate observations are ready for promotion into the intelligence store.

Data is loaded from GET /pipeline/repos/<owner>/<name>/retrospectives. Every metric on this tab is scoped to issues whose retrospective records were created within the selected window.

A control at the top of the tab chooses the lookback window: 7 days, 30 days (default) or 90 days. Changing the window reloads every card.

Outcomes · N items shows how completed items resolved, with a bar and a count per outcome. Colony’s retrospector agent records the outcome when an item completes, and only items with an outcome appear. See Outcome Distribution.

Empty state: “No outcome data recorded in this window. Check the current status for in-flight issues.”

This card compares the files Colony planned to touch with the files it touched, for items with both records:

RowMeaning
Matched the planActual and planned file counts were equal.
Touched more filesActual file count exceeded planned file count.
Touched fewer filesActual file count was below planned file count.

Each row shows its percentage of the items with data. See Plan Drift Rate.

Empty state: “No file scope data available for this window. It accumulates as items complete with planned and actual file records. View the pipeline for active issues.”

Lessons, recurring failure patterns and general observations from items in the window, each with a count that opens the items behind it. Colony writes these from each item’s history, and they can be wrong. Lessons and failure patterns show the top 20 by frequency.

Empty state: “Nothing learned in this window yet. View the pipeline as items complete to see lessons appear here.”

Invariants and playbook items the retrospector flagged, up to 100 across the feed, with those it recommends first. Each shows its item, its kind and its text. With the standard-create grant, Make it a standard turns one into a statement.

Empty state: “No candidates in this window.”

The Retrospectives tab surfaces issue-level drift and outcome data. For rolling repo and org health signals — Block Rate, Failure-Blocked Rate, Mean Cost / Issue, Mean Turns / Issue, Reimplement Loop Rate, and Dead Letter Rate — see the Rolling Health KPIs section in the Metrics reference. Those metrics are computed over a rolling baseline window and are not shown on this tab.