Documentation

Review at day 90

Ninety days after go-live, read five measures of the setup with the customer, find what causes each weak result, and agree on what to change.

Ninety days after go-live, review the setup with the customer. Read the measures below, compare them with the goals of the discovery document, and agree on what to change.

The measures

CoRoid does not show these measures together on one page yet. Read each one where the table says, and write it down for the review.

MeasureWhere to read it
Days from kickoff to the first pull request merged by an agentThe go-live checklist, where you recorded it
Share of agent slots in use, and tasks delivered per weekSlots: Active now and Queued in Settings → Billing & usage → Capacity & credits. They show the moment only, so read them at set times each week. Tasks: the factory's Work finished figure, with 4 weeks chosen
Quality Control passes on the first tryFactory → Run log, with the type Quality check chosen. Count the changes whose first run passed
Workflow cases closed without a handoverEach workflow's Statistics, for 3 months: Closed by the workflow
Support cases caused by a configuration mistakeThe customer's own support records. Count the cases whose fix was a change of a setting

See The overview for the factory's figures.

Find the cause

A weak measure points to a setting more often than to the product. Start with these places.

What you seeWhere to look
Few pull requests by agents, or a slow first oneThe requests: are they clear enough to build? See Specification-driven development. Also how long work waits in Needs you
Many slots stay emptyToo few requests reach CoRoid. Check the request sources, mandates and automations. Or the plan has more slots than the work needs
Slots are full and tasks wait longThe work needs more agent slots. See Agent slots and capacity
Few changes pass Quality Control on the first tryAGENTS.md, the project context, and the build and test commands. Also checks that are set wrong
Few workflow cases close without a personPaths and rules table rows that are missing. In Statistics, a step whose yeses were Approved as written can need fewer yeses
Support cases come from settingsThe setting, and the part of the handover note that explains it

Agree on what to change

  1. Go through the measures with the customer, against the goals of the discovery document.
  2. For each weak result, name the cause and the change.
  3. Give each change an owner and a date.
  4. Update the discovery document and the handover note with each change.

A need that no setting covers is a request to CoRoid. See A need that nothing covers.

Done when

The customer agrees with the list of changes, and each change has an owner and a date.