Kits
Kits
A kit is a template for a whole project, applied in one go (module kits). A kit makes the project, its board columns and first tasks, a brain outline, a monitor on its address and a team of agents on one model, all inside Max and without a card each. Anything that changes something outside Max (adding a domain, DNS records, an app or a mailbox) is offered as its own approval card. A step that is already true raises no card.
In the sidebar under Projects → Kits. Kits are applied from Projects.
What you see
The Project kits page lists the kits you may use, with Search kits…. Each kit shows its name, purpose, project kind, whether it uses a web address, and what it makes: first tasks, the team, the brain outline, readiness checks, whether it watches the address, and its outside steps.
- Platform kits are offered to every organisation.
- Ours kits are your organisation's own, offered to everyone in it.
On each kit:
- Use this kit opens New project from kit on the Projects page with this kit chosen.
- Copy as ours (for people who write kits) makes your organisation's own copy.
- Edit and Publish on your organisation's kits.
With no kits yet, it says "No kits yet". A platform administrator sees Add starter kits, which adds the kits the platform ships.
What you can do
Start a project from a kit
- Open Projects and press New project from kit.
- Pick a kit; what it makes is listed under it.
- Write the project's name and, when the kit uses one, its address, such as
example.com. - Pick the model the kit's team should run on.
- Read the preview: everything the kit will make inside Max, and every outside step that will be asked as a card.
- Press Create. The result lists what was made, what was already there, what was skipped and why, and the cards now waiting for an answer.
- Open the project's Readiness to see what is still missing.
A shop kit also starts the launch checklist: after the team is made, the project is set to the building stage and readiness auto-fix is switched on.
Fill an existing project from a kit
- Open Projects and, in the project's ⋯, press Apply a kit.
- Pick the kit. The project's name is fixed, and its live address is filled in when it has one.
- Read the preview. Only what the project lacks is listed: missing columns, first tasks no kit made before, a monitor if none watches the address, the team if the one a kit made is gone.
- Outside steps that are already true, or whose card is still waiting, are not asked again.
- Press Apply. If nothing was missing, the result says so and nothing is made.
A task the kit made that somebody completed or deleted is never made again.
Copy a kit as your own
- On a platform kit, press Copy as ours. The copy is your organisation's own and unpublished; the platform's stays as it is.
- Press Edit to change its name, first tasks, team, outside steps or anything else. Each field's (i) says what it does.
- Press Publish. Only people in your organisation see it, listed as ours beside the platform's.
When the platform publishes a newer version, your copy's card says so and what changed. Your copy never changes by itself.
Who can do what
| Permission | Label | Lets you |
|---|---|---|
kits:read | See project kits | Open Kits and read what each kit makes |
kits:apply | Start or fill a project from a kit | Use New project from kit and Apply a kit |
kits:manage | Write this organisation's kits | Copy, edit and publish your organisation's kits |
Making the project also needs Projects rights, and each outside step is still approved by a person.
What runs on its own
Nothing in this module runs on a schedule.
Needs
Kits declares no other module it needs, but what a kit makes depends on what is installed: Projects, Tasks, Brain, Monitoring, Agents and Readiness. When Readiness is not installed, the result says so.
For agents
Agents can find a kit and apply it for you.
Read (read-only): kits.list, kits.get (one kit in full), kits.preview (what applying would make, changing nothing), kits.projectTeam (the team a kit made for a project).
Change: kits.apply (start or fill a project; outside steps are raised as approval cards, never done directly).
Over MCP the same tools are named kits__list, kits__apply and so on.