Kanban worker lanes
Kanban worker lanes
Start with meaning, then move to detail.
This lesson explains Kanban worker lanes as part of using Hermes and understanding its behavior. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect The hierarchy, What a lane provides, 1. An assignee string, then verify failure modes and version compatibility.
Start with installation if you have not run Hermes yet.
A clear outcome before you read.
- Understand Kanban worker lanes without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
What does the source say, and in what order?
- 01The hierarchy
Start here to understand the core idea or structure.
- 02What a lane provides
Read this after the foundation, then connect it to the previous step.
- 031. An assignee string
Read this after the foundation, then connect it to the previous step.
- 042. A spawn mechanism
Read this after the foundation, then connect it to the previous step.
- 053. A lifecycle terminator
Read this after the foundation, then connect it to the previous step.
- 06Outputs and the review-required convention
Read this after the foundation, then connect it to the previous step.
- 07Logs and audit trail
Read this after the foundation, then connect it to the previous step.
- 08Existing lane shapes
Read this after the foundation, then connect it to the previous step.
- 09Hermes profile lane (default)
Read this after the foundation, then connect it to the previous step.
- 10Orchestrator profile lane
Finish here to verify the result and special cases.
Copy only after you understand the effect.
Hermes Kanban = canonical task lifecycle + audit trail
Worker lane = implementation executor for one assigned card
Reviewer = human or human-proxy that gates "done"
GitHub PR = upstreamable artifact (optional, for code lanes)Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.