Documentation

Go-live

The checklist that the customer signs before CoRoid goes into full use, item by item, and the two measures to record on the day of go-live.

Go-live is the day the customer starts to use CoRoid in full. Before that day, go through the checklist below with the customer. The customer signs it. An item that is not true yet is fixed first, or written down as an exception with a date.

The go-live checklist

Agreement

  • The discovery document is current, and the customer agrees with it.
  • Each rule in the discovery document has a setting, or a request to CoRoid.
  • The pilot ended, and its results are written down.

People and access

  • Each person signs in with their own account. Nobody shares an account.
  • Each person uses two-factor authentication, or the customer's SSO.
  • Each person has the role that the discovery document gives them.
  • The customer's owner has the Owner role.
  • The customer has the list of consultants, and the date that their access ends.

Connections

  • The git host connection belongs to the customer: the customer installed the GitHub App, or the token or sign-in belongs to an account of the customer.
  • Branch protection and required reviews are on in the git host.
  • Each bot and each tool in the discovery document is connected, and nothing else.

Settings

  • Quality Control matches the rules, and no check says that it cannot run.
  • The people who review and merge pull requests are named.
  • Each mandate has an agreed purpose, projects, budget and review date. Or the customer wants no mandate.
  • The AI profile and the allowed models match the rules on data and models.
  • Model credits or provider keys are in place, and a person owns the budget.
  • Each automation in Factory → Automations has an owner who knows what it does.
  • Each workflow is published and on, and was tried with Try it. That includes a message that tries to make the agent break its rules.
  • Somebody answers Needs you every working day.

Capacity and support

  • The agent slots match what the pilot showed.
  • The customer knows who to call when something goes wrong.
  • The customer knows how to send a request or a defect to CoRoid.

Signature

  • Name, role and date of the person who signs for the customer.

Measures to record at go-live

Write these two numbers in the checklist. The review at day 90 compares against them.

  • Days from kickoff to the first pull request merged by an agent. The factory's Pull requests merged figure counts the pull requests that CoRoid's work opened. The git host shows the date of each merge.
  • Days from kickoff to go-live, compared with the date planned at kickoff.

Done when

The customer signs the checklist and keeps a copy.