Hermes BibleUnofficial Docs
← All docs Docs / Core Features

Kanban worker lanes

Kanban worker lanes A worker lane is a class of process that the kanban dispatcher can route tasks to. Each lane has an identity (the assignee string), a spawn

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/kanban-worker-lanes

Kanban worker lanes A worker lane is a class of process that the kanban dispatcher can route tasks to. Each lane has an identity (the assignee string), a spawn

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. The hierarchy
  2. What a lane provides
  3. 1. An assignee string
  4. 2. A spawn mechanism
  5. 3. A lifecycle terminator
  6. Outputs and the review-required convention
  7. Logs and audit trail
  8. Existing lane shapes
  9. Hermes profile lane (default)
  10. Orchestrator profile lane
  11. Adding an external CLI worker lane
  12. Failure modes the dispatcher handles
  13. Related

Section map

The hierarchy

Maps the hierarchy to the Core Features documentation path, with the source page reserved for exact commands and updates.

What a lane provides

Maps what a lane provides to the Core Features documentation path, with the source page reserved for exact commands and updates.

1. An assignee string

Maps 1. an assignee string to the Core Features documentation path, with the source page reserved for exact commands and updates.

2. A spawn mechanism

Maps 2. a spawn mechanism to the Core Features documentation path, with the source page reserved for exact commands and updates.

3. A lifecycle terminator

Maps 3. a lifecycle terminator to the Core Features documentation path, with the source page reserved for exact commands and updates.

Outputs and the review-required convention

Maps outputs and the review-required convention to the Core Features documentation path, with the source page reserved for exact commands and updates.

Logs and audit trail

Maps logs and audit trail to the Core Features documentation path, with the source page reserved for exact commands and updates.

Existing lane shapes

Maps existing lane shapes to the Core Features documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Core Features doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: The hierarchy, What a lane provides, 1. An assignee string, 2. A spawn mechanism, 3. A lifecycle terminator. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: kanban, worker, lanes, class, process. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitCore Features documentation

Use when you need orientation for kanban worker lanes before applying exact upstream commands.

Verify firstThe hierarchy

Open the source anchor for The hierarchy and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
  2. Start with the source section for The hierarchy; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for What a lane provides if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page