Skip to content

Dashboards

The left navigation groups Colony Cloud’s surfaces by job. The Ledger sits in the Work region and Reporting sits in the Reporting region. This page documents both, along with the work-item sheet you act from. Floor and Wall sit under Operations; see Floor and Wall for live fleet activity and ambient displays. Review happens from the Ledger and the work item; see Reviews.

Route: /work (/dashboard/ledger redirects here)

The Ledger is where /work lands after sign-in (/dashboard redirects there), and it is the primary daily-use surface. It follows the repository filter in the page chrome, which is carried in the URL as ?repo=owner/name; clear the filter to see every repository.

Work has three sections:

  • Your queue holds what is owed to you: questions, improvement picks, dependency decisions, and items Colony has flagged for a person, whatever their state.
  • Unstewarded holds owed items nobody has picked up.
  • Moving holds everything else that isn’t finished.

The header reads “N owed to you · … · N moving”. Filtered to one repository, it reads “Filtered to <repository> · N owed to you here · … · N moving”. A Mine first toggle puts your own rows at the top of Your queue and Moving.

Each row shows the title, the repository and age, a status chip that says whose move it is, and an ask when there is one. When Your queue is empty it says so, and when the list is filtered, Show all repositories clears the filter.

Above the list, the Proposals band holds proposals that are not yet work. Tick one or more and use Authorize to file them together (“X of Y authorized”); each row says whether it meets its standards. New proposal and Import a plan start another, and a title or Open opens the proposal at /work?proposal=:id, where Decline also lives. See Drafts.

Click a row’s title to open the work-item sheet, addressed as /work?item=:owner/:repo/:number (the old /dashboard/work/:owner/:repo/:number redirects there). The URL is shareable and survives a reload. On a medium-width window the sheet docks beside the Ledger, so you can keep the list in view.

You can answer what Colony is waiting on without leaving the list:

  • A question. Answer opens a form in the row. Write your answer and send it. Turn on Also keep this as a standing constraint to record it as a constraint on this item in the same step. The row then moves to Moving with a line confirming the send. If Colony didn’t get the answer, your text stays in the row and you can send it again.
  • An improvement pick. See the candidates lists what Colony found, each with its size, files and rationale. Choose one, or use Roll again for more. If the track’s mode is “you pick”, the row links to /autonomy/tracks.
  • A dependency decision. The row shows a summary of the update and the choices it offers: Approve, Adopt, Decline this release, Decline major releases and Recheck.

If the question was already answered or the decision already made on the work item, the row says so, offers Open the item and Dismiss, and sends nothing. Answering and picking need the same grants as on the work item; without one, the control is inert and says why.

When Colony has flagged an item for a person, its status chip reads “escalated · <state>” and the row shows the reason Colony recorded. The row offers Open. An item that is blocked shows the failed chip instead of the flag.

On a compact window Work becomes a single column: the scope line, the menu button and the page title, then “N owed to you · N moving”, Your queue and Moving. A bottom navigation switches between Work (with its count of the Your queue items assigned to you), Operations and Reporting.

Answer in place: Answer opens the form in the row, and once you send, the next ask in Your queue opens. An improvement pick lists its candidates as tappable rows. A dependency decision that needs a desk says so, and offers only Recheck on a phone; approve, adopt or decline it at a desk, where the review shows what changed.

Route: /reporting/reports

Reporting is the home for the org’s sealed, dated record of what happened. It has four tabs: Reports, Retrospectives (/reporting/retrospectives), Events and Settings (/reporting/settings).

Pick a period (day, week, or month). The tab shows your subscription for that period, This week so far (the open window, summarized in two sentences, with when it seals), and the list of sealed reports. Each row gives the period, when it sealed, the work items completed and the spend, and a Read link. Until a report has sealed, the tab says so in words rather than showing a zero or a placeholder number.

Each sealed report opens at /reporting/reports/:id. The page has:

  • a cover with the period as its title, and a meta line with the organization and tenant, the dates, when it sealed and the start of its SHA-256;
  • Colony’s reading of the period, written once at seal time. It is labeled as Colony’s, sits outside the sealed record and can be wrong. Reports sealed before readings existed show a note instead; the statements are complete without it;
  • the nine statements in two bands, Delivery and Cost, each with its figure in bold;
  • a note for any restatement. A later report states the change; an earlier report stays as it was sealed.

Some statements carry a doorway: Open them in Work on what was delivered and what didn’t land, See the tracks on autonomy, and Open Operations on availability. A doorway is hidden when its population is zero. To narrow a report to one repository, add ?repo=owner/name; the page then shows that repository’s own breakdown from the sealed report, not a recount, and leaves out the statements that are tenant-wide.

Share or export opens a dialog with three parts:

  • Copy the link. Anyone in the organization can open it.
  • Invite a report reader. Enter an email address. This needs the Reporting bundle. See Team & Roles.
  • Export the sealed file. The file is exactly as sealed. Check a file computes the SHA-256 of a file you choose, in your browser, and tells you whether it matches the sealed report’s.

A doorway opens /work filtered to the report’s items as they stood at period close. A banner names the report and says that the items’ states now may differ, with Back to the report and Clear. If late data changed the count since the seal, the banner states both counts.

A report reader sees only the Reports tab and the sealed reports. They get no doorways, no link to copy and no invitation section, and they keep Export and Check a file.

Set spend limits on Operations → Settings (/operations/settings), not on Reporting. It shows the Daily cost cap and the Colony Mayor monthly cap when your plan has one. Administrators change the daily cost cap there, with a reason; everyone else sees it read-only. Below that, set the Monthly ceiling (USD) and a Repository monthly cap (USD) for each repository. A repository’s effective ceiling is the lower of its repository monthly cap and the monthly ceiling. A changed monthly ceiling applies after the pipeline next restarts. See Cost & Budget.

The work-item sheet shows an item’s intent, discussion, constraints, and history, with its actions in the footer. The footer offers Answer (when the item is waiting on a question), Constrain, Add knowledge, Stop or Resume, Release #N for a canceled subtask, and Cancel. A More actions menu holds the rest. What you see depends on the item’s workflow and your role, and an action your workflow does not offer from Cloud appears disabled with a reason.

From the sheet, you can act on each item:

SituationAction
Worker stalled or timed outChoose Retry in More actions to re-queue the item through colony_act (or use /colony:retry [size] on the issue).
Item is waiting on a questionClick Answer and reply in the form.
A rule should apply to this item from now onClick Constrain to add a standing constraint.
Colony needs context it does not haveClick Add knowledge to record it.
Nobody owns the itemUse Claim (or Take over when someone else holds it) in the sheet.
Issue is blocked on a dependency that has since resolvedOpen More actions and click Unblock to remove the current block and re-enqueue.
Review loop caused by a bad issue or bad conventionsFix .colony/conventions.md, then retry the issue with /colony:retry.
Issue should be abandonedClick Cancel to transition to Done and close the GitHub issue.
Issue has related dead-letter contextDiagnose the issue, then use Recover a Dead-Lettered Issue when the record itself must be retried or resolved.
Processing should halt temporarily without losing stateClick Stop to halt the run in progress and hold the item until you resume.
Issue was previously paused and should resumeClick Resume to unpause and restore to the pre-pause state.
Analysis is complete and planning should be skippedOpen More actions and click Skip planning to go straight to development.
Issue scope is too large and should be broken into subtasksOpen More actions and click Decompose to force epic decomposition into subtasks.
Current implementation is wrong and should be restarted from scratchOpen More actions and click Reimplement to close the PR, delete the branch and worktree, and reset to analyzing.
PR is ready for a re-review cycleOpen More actions and click Trigger review to start a new review cycle.
PR needs targeted changes the automated reviewer cannot captureOpen More actions and click Return with feedback to send change-request text back to the developer agent.
Pipeline state is incorrect and must be corrected manuallyOpen Operations → Override, choose the repository and item, pick one of the states its workflow allows from where it is now, and give a reason. Colony makes the move and records your reason.
Issue priority needs to changeOpen More actions and click Set priority to set priority to high, normal, or low.
Analysis is out of date or wrong and should be redone from scratchOpen More actions and click Reanalyze to discard the previous analysis and re-run the analyzer.
A completed item needs more workOpen More actions and click Reopen to send it back to intake. Only offered when the item’s workflow declares reopen.

Reanalyze is offered only in states where the workflow declares it, and it is hidden while the item is paused. Workflow-declared custom operator actions also appear in More actions, under their declared label or the humanized slug if none is declared, and only in states listed in their from. Actions with executable side effects (close-pr, merge-pr, add-label, remove-label) ask for confirmation first.

A parent that cannot finalize because one of its subtasks was canceled is released from the work item itself: open the parent and click Release #N in the footer for the canceled subtask. This stops the parent waiting on that subtask. The subtask stays canceled, and the parent finalizes on its next sweep if nothing else is outstanding.

For the full list of slash commands available on individual issues and PRs, see slash commands. The Operator role page covers when to intervene.