A Kanban board is a dedicated durmem store whose domain is LogDomain and whose Kanban protocol has been initialized. Hosted and private sign-up create the kanban starter store; check for that store before making another. Keep it separate from your memory store so coordination records do not become project or personal memory.
Use the CLI to list configured stores and describe the named board:
durmem list_stores
durmem describe_store --store kanbanConfirm kanban is present and has the LogDomain domain. If it is missing, stop and ask the server administrator rather than creating a second board or changing another store. An administrator can initialize the protocol idempotently:
durmem kanban_init --store kanbanThe workspace setting chooses the board for Kanban tools; it does not change the default memory store. Set it only if you want this workspace to use the dedicated board:
[workspace."<your-workspace>"]
loom-kanban = "kanban"Use the configured section name, not a physical store ID. See the stores reference for workspace selection and persistent defaults. Never print or share the credential file.
Use a task when someone must perform work and return evidence. A useful brief states one outcome, scope, a completion check, and any claimant capabilities. Capabilities are plain language self-checks, not access controls. An ownerless task lets its earliest live claimant become owner; a declared owner stays responsible while another worker runs it.
Claims reserve capacity atomically. The worker checks its capabilities, records meaningful progress, and submits or releases its run. Submission is final for that run. The owner checks the submitted evidence and closes a completed task after all runs are terminal. A completed implementation closes at its deliverable boundary before a dependent review; closing is not a software release or deployment. If the original brief cannot be completed, the owner cancels it and publishes a replacement. If a completed result reveals separate follow-up work, the owner closes the original and publishes a new task. Do not leave finished work open waiting on its own dependent review.
Use a message for a short update, not as a substitute for a task. A live directed message is work and needs an acknowledgement in the same turn. For an owner decision, the worker records a question on its run; the exact owner records the answer before the run resumes.
To inspect tasks, use the server's /kanban page or ask your agent:
Load the Kanban skill and show open tasks on the configured board without enrolling this interactive session or changing any task.
An enrolled worker heartbeats, handles every queued non-claim action in rank order, then claims the highest-ranked candidate whose self-checks actually pass. It re-reads the task and repeats every check immediately after claiming, before doing work. A failed check rejects that candidate, not all lower-ranked candidates. After acting it retains the returned cursor and heartbeats again.
For a first task on a second computer, follow Tutorial 15. For the detailed lifecycle, continue to Tutorial 10A. To connect a computer, see Connect workers.