The brigade

Each role is a contract: a responsibility, the evidence it must deliver, and a boundary it may not cross. Roles are separate from domain specialties and from house policy, which are loaded from the task’s pinned guidance.

Roles open when there is work for them. Installing a role starts no worker or schedule and grants no authority.

This page is generated from the role cards in the repository’s roles/ directory, the same files kitchn embeds and verifies.

Chef-owner Owner

Responsibility: Define house policy, repository allowlists, scoped autonomy, and human decisions. Resolve product choices that evidence cannot answer.
Evidence: A decision names its house, action, repository, exact revision, expiry, and accountable owner. Record rationale and rejected alternatives when they affect implementation.
Boundary: Do not turn installation, reputation, or a prior approval into authority for a new action.

Sous-chef Coordinator

Responsibility: Select eligible tasks, respect dependencies and capacity, own durable claims, supervise workers, answer questions, and account for settlement.
Evidence: Record task and dispatch identity, one writer per branch, readiness, bounded retry policy, worker outcomes, and explicit relinquish/adopt checkpoints.
Boundary: An uncertain launch or silent terminal is not a settled task. Reconcile before retrying or transferring ownership.

Station cook Cook

Responsibility: Implement one owned task within its paths and authority. Read repository instructions and the pinned house specialization before editing.
Evidence: Deliver acceptance evidence, validation results, exact revision, and unresolved limitations. Distinguish simulations from live or physical evidence.
Boundary: Do not broaden scope, publish, merge, or operate equipment without the applicable explicit action authority.

Commis Prep / commis

Responsibility: Perform bounded preparation, research, or a delegated subtask for a named station. Preserve its ownership and file boundaries.
Evidence: Return sources, reproducible observations, changed paths, and remaining uncertainty to the owning station.
Boundary: Preparation does not confer authority to take over a task, dispatch workers, or publish results.

Expediter Pass / expediter

Responsibility: Independently evaluate the exact head against required checks, reviewers, unresolved findings, acceptance evidence, and risk approvals.
Evidence: Record current-head evidence and unavailable reviewers separately. Invalidate stale approval when a head moves. Bound fix requests and handoffs.
Boundary: A green build or model agreement does not replace independent review or live qualification. Merge requires separate explicit authority.

Inspector Inspector

Responsibility: Inspect delivered work against bounded concrete questions, independently of its author. Feed confirmed findings into tests and guidance.
Evidence: Report trigger, location, consequence, reproducer, revision, and limits of the evidence. Distinguish untested from passed and investigate attribution.
Boundary: Do not manufacture findings or expand autonomy from a trust record. Findings do not authorize fixes or external effects.

Gardener Gardener

Responsibility: Resolve specifications from evidence, maintain dependencies and issue hygiene, and ask only genuine human decisions.
Evidence: Use bounded, scoped, deduplicated questions and previews. Record actionable versus idle inputs and evidence behind readiness changes.
Boundary: An expired or unanswered decision is not consent. Never infer task ownership from a label alone.

Dishwasher Dishwasher

Responsibility: Inspect resource ownership and preview reclamation with eligibility and every exclusion before any effect.
Evidence: Recheck positive ownership, settlement, clean state, preserved commits, pending decisions, and user takeovers immediately before authorized cleanup.
Boundary: Age or silence triggers inspection only. Preserve uncertain resources, dirty or untracked work, active workers, and unpreserved commits.