Autonomy
The Autonomy page (/autonomy/portfolio) is the org-wide view of what work Colony chooses and how much it decides alone. Its subtitle reads “What work is chosen, and how much Colony decides alone.”
The Autonomy item in the left rail and the Strategy tab each show a count: the number of repositories with a strategy proposal waiting for review. The count covers the whole organization, so a repository filter never hides it. It shows only to people who hold the Autonomy grant, and it is hidden at 0.
The page has two parts: a status line for the Strategist at the top, and Strategy by repository below it.
The Strategist status line
Section titled “The Strategist status line”The status line reports whether the Strategist is running on schedule. It only counts repos with an active charter. A repo without one is left out. To set up a charter and the autonomy grant for a repo, see Strategy. For the concept, see Strategy.
When proposals are waiting, the line also names them and how long each has waited, for example “1 strategy proposal waiting: colony-cloud, for 2 days”. Open Strategy to review.
The line shows one of these messages:
| Message | Meaning |
|---|---|
| No repository has an active charter. | None of your repos has a charter, so there is nothing to schedule. |
| Not reporting. No strategist run recorded for the chartered repository. | One repo has a charter, but Colony has never recorded a Strategist run for it. With several chartered repos the message ends “for any chartered repository” instead. |
| On schedule across N chartered repositories. | Every chartered repo has a recent successful run. With one repository, the message reads “1 chartered repository”. |
| X of N chartered repositories are not on schedule. Worst: … | At least one chartered repo is off schedule. The text after “Worst:” names the repo that needs attention first. |
| Not reporting. Charter status unknown: run state could not be loaded for … | None of the repos whose run state loaded has a charter, but run state could not be loaded for at least one other repo, so Colony cannot tell whether that repo has one. |
If run state could not be loaded for some repos while others loaded, the line adds a sentence for the ones that failed: “Run state could not be loaded for …”, with “and N more” when several failed. When every chartered repo is on schedule, the sentence is joined to the first part: “On schedule across N chartered repositories, but run state could not be loaded for …”. A repo that no longer exists is ignored rather than reported as unknown.
Picking the worst repo
Section titled “Picking the worst repo”The “Worst” repo is chosen in this order:
- A repo that is not reporting, meaning it has no recorded run.
- A repo whose latest run failed. The message gives the date, the failure reason when there is one, and a count such as “(3 in a row)” when the run has failed more than once consecutively.
- A repo that is overdue.
Within the same group, the repo with the oldest latest run comes first.
A run counts as overdue in three cases:
- It succeeded, but it is more than one hour past the pipeline’s own
nextDueAt. The hour absorbs a cycle that is still running when its due time passes. The deadline always comes from the pipeline, never from a value Cloud picks. - It succeeded, but the pipeline recorded no usable next due time for it.
- The latest run neither succeeded nor failed and is not still pending. The message reads “is overdue, last run … was …” and names the outcome.
When every chartered repository is on schedule, the line opens with the time of the newest run, for example “The Strategist last ran 3 October, 03:12 UTC, on schedule across 3 chartered repositories”.
Strategy by repository
Section titled “Strategy by repository”One row per chartered repository, with proposals waiting for review first. Each row shows the repository, a waiting for review or active chip, the strategy version and a goals summary such as “4 goals: 1 met, 1 partly, 1 unmet, 1 unknown”. A waiting row offers Review, and any other row offers Open. Both go to the Strategy tab.
Below the list, a line counts the repositories with no charter, which only operator tracks feed, with a Write a charter link.
Where each track is configured and whether its work conforms to the portfolio are on the Tracks tab, with a repository selected.
Related
Section titled “Related”- Strategy: the charter and the autonomy grant.
- Self-Improvement Tracks: configure and monitor tracks.
- Strategy concepts: how the Strategist chooses work.