Glossary

Several words in the product look related and mean different things. This page pins them so the Floor, chat, and Settings do not fight over the same label.

Floor Team

A Floor Team is a recipe: a deterministic sequence of roles over one plan item (or a phase of items). It is what Adjust calls Team when you queue work from the plan — Solo, Build and verify, Phase team, Plan, Research, Custom. It is not a person you address in chat, and it is not a group of chat personas.

See the teams for who runs on each recipe and what each ends at.

Teammate

A Teammate is a named chat persona on the desktop daemon — display identity, default model, and tool grants — that you address in chat and bind a session to. Settings and chat surfaces use this noun. A Teammate is never labeled Team. Teammates is the page.

Crew

A Crew is the collective of Teammates (the surface that lists them together). It is not a Floor Team: collecting personas is not the same as choosing a dispatch recipe.

Agent (web app)

Settings → Agents in the web app lists the app's own chat assistants — the built-in Manager, COO and CTO, plus any you add — each with its own instructions, model and allowlist of chat tools. They are not Teammates: they live in the app, not on a daemon, and carry no Slack grants. The word agent also names any process an orchestration run launches; context makes that one clear.

Playbook

A playbook is a saved way to start a recipe: name, recipe (solo or build-verify), brief, parameters, and optionally a graph of recipe, prompt and Teammate nodes. The desktop calls the daemon's list the Workflow catalog; the web app's builder page is Workflows, which keeps a separate catalog on your Kairoku account. Workflows.

Automation

An automation is a trigger on the desktop daemon — a cron schedule, a signed webhook, or a forge event class — bound to a target: a prompt, or a recipe with a brief. It carries a routing policy saying which daemon should take the wake. The web app's Automations page keeps a separate catalog that nothing fires in this release. Automations.

Integration, catalog entry, vault

A catalog entry is a connector the daemon advertises as data (slack, github, gitlab, and the fixture.* rows used in tests). Installing one may attach a credential — a token the daemon encrypts into its vault, a file-backed store on the machine whose contents are never rendered back. Integration catalog.

Wake relay

The Slack wake relay is a small cloud service that accepts Slack events while your daemon is offline, holds them for 72 hours, and hands them to the daemon when it reconnects. It is optional; daemon-first intake works without it. Slack.

Two daemons

kairoku daemon is the orchestration runner the CLI installs on an agent machine: it claims Floor runs from the web app and launches agents in worktrees. kairokud is the desktop daemon the desktop app carries: vault, Teammates, integrations, automations, playbooks. They are two programs with two configuration directories, and neither calls the other today. When a page says "the daemon", the section it is in tells you which.

At a glance

Floor Team stays the recipe noun. Chat personas use Teammate. Collectives use Crew. Do not label a chat persona Team.