This stage turns the rules of the discovery document into settings. Work through the areas below in order. For each area, decide with the customer, then set it.
Write down each decision and its reason as you go. The handover note is built from these notes.
Projects
Decide with the customer:
- Which repositories become projects. Use one project for each repository.
- The branch that CoRoid opens its pull requests against.
- Whether CoRoid may push to the repository (Synced) or only reads it (Local only).
- The commands that install, build and test the code, and the services that the tests need.
- What agents must know that the code does not show.
Create each project from Projects. Then open the project's settings:
Repository for the branches and the mode, Environment variables, and
Knowledge → Context for what agents read. Check the build and test
commands that CoRoid detected. Write what agents must know in AGENTS.md, in
the repository.
See Create your first project, Repository and branch settings, Build and test configuration and Write an AGENTS.md.
Quality Control
Decide with the customer:
- What every change must pass, and which failures block or only advise.
- How thorough QA is, and where the checks run.
- What happens to the pull requests that people open: CoRoid Quality Control, and CoRoid Review as advisory or blocking.
- Which sources may file requests, such as Slack, Telegram or Jira.
- What happens when something breaks, such as a failed task or deployment.
Set it in Quality Control. Set the Organisation default to the checks that most projects need. Give a project its own setup only where it differs. See Quality policies and gates and Anti-slop checks.
A pull request from CoRoid merges only when a person merges it. For code that needs a named approver, such as payment code, use branch protection on the git host.
Mandates
A mandate lets CoRoid start work that arrives without a person, for example from an error tracker. It never lets CoRoid merge or deploy.
Decide with the customer:
- Which work CoRoid may start on its own, and on which projects.
- How much it may spend per week or per month.
- When the customer will look at the mandate again.
Set mandates in Quality Control: choose Organisation default, then Mandates in the Delivery group. When the customer wants no work without a person, set no mandate. See Mandates.
AI profiles
Decide with the customer:
- Which profile the organisation uses by default.
- Whether model calls must stay in the EU. Then use EU Only.
- Whether to pay for models with CoRoid's model credits or with the customer's own provider keys.
- Which providers and models agents may never use.
Set profiles in Settings → AI profile, and keys in Settings → Provider keys. Limit providers and models in Settings → Identity and access → Org policy. See AI profiles, Provider keys and Model credits.
Automations
Decide with the customer:
- Which work starts on a schedule, and which starts when something happens.
- What each automation does, and in which projects.
- Whether an automation only reads and reports, or also opens tasks.
Create automations in New Work, and find them all in Factory → Automations. The switches under When something breaks in Quality Control each run one automation. See Automations, Schedules and Hooks.
Workflows
A workflow covers a business process, such as a support inbox. Agents do its steps, and people decide where the workflow says so. Workflows is not on for every organisation yet. Ask CoRoid to switch it on.
Decide with the customer:
- Which process to cover first. Choose one with many similar cases and clear rules.
- How a case starts: an email, a form on the customer's website, a person, or another workflow.
- The steps, and what each step waits for: nothing, only money, or every change and message.
- The paths for each step: ask the customer, go to another step, follow a rules table, hand the case to a person, or close it.
- The rules tables, as rows of "when this, then that".
- The address that replies come from, the signature and the AI disclosure line.
Build it in Workflows. Each workflow has Cases, Steps and Settings, and the rules tables are shared under Rules tables. Run Try it on the steps before you publish: Try it sends and changes nothing. Then Publish and Turn on. See Workflows over MCP.
Review rules
Decide with the customer what CoRoid's Reviewer must look for in this customer's code, beyond CoRoid's own rules.
Write the rules in each repository: a REVIEW.md file at the root, and rule
files in a review-rules folder. CoRoid reads them from the base branch, so a
pull request cannot change the rules it is reviewed by. Set what CoRoid Review
posts in Quality Control, under Pull requests. See
Pull requests.
Skills
A skill is a procedure that agents load only when the work needs it, such as "how we write a database migration". Decide with the customer which of its own procedures agents must follow.
Write each skill in the repository, as skills/<name>/SKILL.md. The file
starts with front matter that holds a name and a description. Agents read
skills from the merged repository only. See
Progressive skills and
Write an AGENTS.md.
What you can change without code
Customers and implementers do not get CoRoid's source code. Everything that a customer can change is in this table: a setting in the portal, or a file in the customer's own repository. Some pages appear only where CoRoid has switched the feature on, such as Workflows.
| What | Where |
|---|---|
| Organisation name | Settings → General |
| Members and their roles | Settings → Members |
| AI profiles | Settings → AI profile |
| Provider keys | Settings → Provider keys |
| Service accounts for the work intake API | Settings → Service accounts |
| The git host connection | Settings → Connections → Source control |
| Slack and Telegram bots | Settings → Connections → Channels |
| External MCP servers, and the tools agents may call | Settings → Connections → External MCP |
| Access tokens, approvals and automation policies of CoRoid's MCP server | Settings → Connections → CoRoid MCP server |
| SSO, verified domains and directory sync | Settings → Identity and access → Enterprise identity |
| Allowed models, providers, commands and tools | Settings → Identity and access → Org policy |
| Signed-in sessions | Settings → Identity and access → Active sessions |
| The audit log and its export | Settings → Identity and access → Audit log |
| Plan, agent slots and model credits | Settings → Billing & usage |
| Storage, data retention and the settings export | Settings → Data & legal |
| A project's name, repository, branches and mode | The project's Settings → General and Repository |
| A project's environment variables | The project's Settings → Environment variables |
| What agents read about a project | The project's Settings → Knowledge → Context |
| Review evidence from the customer's tools | The project's Settings → Integrations |
| Checks, QA, request sources, pull requests and "When something breaks" | Quality Control |
| Anti-slop rules and the weekly debt cleanup | Quality Control |
| Mandates | Quality Control → Organisation default → Delivery |
| Security protections, threat models and attack surface | Security → Projects |
| Languages, translation checks and contributors | Globalisation |
| Release environments, approval rules, deploy pipeline and versioning | Releases → Release settings |
| Event automations and schedules | Factory → Automations, created in New Work |
| Scheduled reports | Factory → Reports |
| Workflows and rules tables | Workflows |
| Agent instructions | AGENTS.md and the other memory files in the repository |
| Review rules | REVIEW.md and the review-rules folder in the repository |
| Skills | skills/<name>/SKILL.md in the repository |
The CoRoid MCP server changes many of these settings from an assistant, within the tools that are switched on.
A need that nothing covers
When no row of the table covers a rule, do not build around the product. Send the need to CoRoid as a request through the contact page. Write:
- The customer's situation, without customer data.
- What you tried with the settings above.
- What the customer needs, and why.
A change that CoRoid makes reaches every customer in a release.
Done when
- Each rule in the discovery document has a setting, or a request to CoRoid.
- Each decision has a reason in your notes.
- One task in each project reaches a pull request through the checks.
Related
- Settings overview
- Pilot, the next stage