Enroll a service
Enrollment is an explicit decision. A repository that a source can see stays a candidate until someone enrolls it, and the resulting service starts with a minimal policy that you confirm next.
Enroll
Section titled “Enroll”- Find the repository under Repository candidates. Use the search, source, and state filters if the list is long.
- Choose Enroll service. The enrollment page shows the repository name as its title.
- Enter a Service name and a Slug. The slug is a stable lowercase identifier and cannot be changed later.
- Review the Starting policy: type Application, risk Medium, repository root
.(the whole repository), and AI authority Repository read. - Choose Enroll and activate, or Save as draft to enroll without activating.
An activated service opens on its Policy tab. A draft returns you to the candidate list, where its card now shows lifecycle actions.
What happens next
Section titled “What happens next”- One service exists per repository candidate. The service inherits the source’s detected capabilities as a ceiling; its own AI capabilities are switched on separately in the policy.
- Enrollment writes revision 1 of the service’s execution policy. Every later change appends a new revision; revisions are never edited.
- The service’s Policy tab shows a post-enrollment checklist: description, commands, expected checks, protected paths, and repository access. Confirm it before anyone requests a change. See Manage a service’s execution policy.
Lifecycle
Section titled “Lifecycle”Lifecycle actions live on the candidate card in Settings → Repositories, not on the service page:
- Pause stops new work; Activate resumes it.
- Archive stops new work permanently while keeping the enrollment, change records, and audit history. Archived services show no further actions.
- A service whose repository is no longer visible to its source becomes Disconnected automatically.
Confirm the execution policy, then invite people and assign roles so the service has at least one Developer.