Skip to content

Strategy

Strategy is a tab of the Autonomy region (/autonomy/strategy?repo=<owner>/<name>). It is where you judge the Strategist’s proposals. Approving, declining, editing and reverting need the Autonomy grant. Without it the controls show but stay inert, and they name who holds the grant.

For the model behind goals, pools and evidence, see Strategy.

With “All repositories” selected, the tab lists each repository that has a proposal waiting: the repository, the version, how long it has waited, and a Review link. The repository chooser comes below the list. With nothing waiting, only the chooser shows.

The number of repositories waiting also appears on Autonomy in the rail and on this tab. It covers the whole organization and shows only to people who hold the Autonomy grant.

When a proposal is waiting, the tab leads with it. A deep link is /autonomy/strategy?repo=<owner>/<name>&review=<version>.

The Strategist’s proposal. The block names the version, the repository, when the Strategist made it and how long it has waited, under a “waiting for review” chip. It counts the tracks created, changed and retired, and says that the proposal can be wrong: each change cites what it read. Show the transcript opens the run’s transcript in a drawer.

Below it:

  1. Goals · how the charter is doing. One row per goal in charter order: its state now (met, partly, unmet or unknown), the evidence with citations, a trend of the last five runs that assessed it, and the strategy tracks that serve it. Runs that propose nothing still update this table. Edit the charter links to the charter page.
  2. What changes in the strategy pool. Each strategy track compared with the tracks running now, not with the previous snapshot: share, cadence and menu mix as before → after, what is created or retired, the goals it serves, and its rationale with citations. A changed prompt has a collapsed line diff of its instructions.
  3. Capacity. How many open slots go to strategy tracks and how many to operator tracks, and how many slots each strategy track gets.
  4. What the Strategist read. The run’s inputs, one per collector. A collector that failed reads <name>: unavailable: <reason>. Each citation above links here.
  5. Operator tracks. Read-only rows with Open in Tracks. A strategy never changes them.
ActionWhat it does
Approve and applyOpens a confirmation listing each create, change and retire with its share, cadence and goals served, then the capacity split. Confirming applies the proposal at once, recorded as approved by you. There is no separate approved step.
DeclineNeeds a reason of up to 500 characters. The version becomes declined and the reason is kept in history.
Edit, then approveA drawer where you change each track’s share, cadence and menu mix, or add a live strategy track. Goals served and the prompt are read-only. Colony checks your edits with the same rules. A refused submit writes nothing and leaves the proposal waiting; each violation shows beside its field, and Approve with your edits stays off until you change that field.

There is no per-track accept. Approving with edits records a new version authored by you that replaces the proposal.

The top of the tab shows the last run and the next one: Last run: <time>, a proposal (v13). Next run: <time>. The last outcome is a proposal, no change, or a failure with its reason; a failed run offers Run it now.

Each version shows a status chip, what triggered it (scheduled run, charter change, on request, an edit of another version, or a revert), when it was created, and who decided it with their reason. Deciders read as “you”, a member’s name, or “by auto approval”.

StatusChip
Waiting for reviewYours
ActiveDone
Superseded, declined, invalid, no changeColony

Superseded, declined, invalid and no-change entries are collapsed. An invalid entry opens to its violations, and a superseded one says why, for example “Set aside: the charter changed (v5 replaced v4).” Runs with no change group into one entry.

Revert to v<N> appears on the active version when its parent has an applied set of tracks. It applies that version’s tracks again as a new version authored by you. Work already started keeps going.

Generate asks the Strategist for a proposal now. The request is durable, and one made while a run is pending is absorbed by it. The page shows the pending run, not a guess.

The charter page is /autonomy/strategy/charter?repo=<owner>/<name>. It holds an ordered list of goals and the guidance.

  • Each goal has a one-sentence statement and an optional “Done when”. You can add, edit, reorder and remove goals. Removing one asks first, because its history ends. An edited goal keeps its id; a new goal gets a fresh one.
  • Guidance is what the Strategist should keep in mind. It is never assessed.
  • A charter with guidance but no goals shows a notice and Add the first goal.
  • Saving a changed charter sets aside a waiting proposal and asks the Strategist for a new one.

Saving the charter needs the Autonomy grant (charter-update).

Autonomy › Settings has a Strategy settings section for each repository, gated by the Autonomy grant:

SettingMeaning
StrategyScheduled and charter-change runs, on by default. It shows the next run. Off stops those runs; Generate still works.
Approval”A person approves” (default) or “Apply automatically”. Automatic asks for confirmation; Colony then applies each valid proposal and records it as approved by auto.
Capacity share0 to 1 (default 0.5), with the resulting split.
Selection”A person picks” or “Colony picks”, the default for strategy tracks that apply creates. Each track can override it in Tracks.
Cooldown floorMinutes (default 60) for strategy tracks that apply creates.

The same section holds the autonomy grant.

The grant sets how large a change the Strategist may apply. Data source: GET /api/autonomy/:owner/:repo; save via PUT /api/autonomy/:owner/:repo.

FieldDescription
Max auto sizeThe largest track size a proposal may contain: small, medium, large or epic. Defaults to small. Approval checks every proposed slate against the grant as it stands at that moment, so narrowing the grant refuses earlier proposals. See Autonomy grant (max_auto_size).
Max auto select sizeThe largest candidate size that may be selected automatically. none keeps every selection with a person. Defaults to none.