Hermes BibleUnofficial Docs
← All docs Docs / Core Features

Kanban tutorial

Kanban tutorial A walkthrough of the four use cases the Hermes Kanban system was designed for, with the dashboard open in a browser. If you haven't read the Kan

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

Kanban tutorial A walkthrough of the four use cases the Hermes Kanban system was designed for, with the dashboard open in a browser. If you haven't read the Kan

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. Setup
  2. The board at a glance
  3. Flat view
  4. Story 1 — Solo dev shipping a feature
  5. Story 2 — Fleet farming
  6. Story 3 — Role pipeline with retry
  7. Story 4 — Circuit breaker and crash recovery
  8. Circuit breaker — permanent-looking failure
  9. Crash recovery — worker dies mid-flight
  10. Structured handoff — why summary and metadata matter
  11. Inspecting a task currently running
  12. Next steps

Section map

Setup

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

The board at a glance

Maps the board at a glance to the Core Features documentation path, with the source page reserved for exact commands and updates.

Flat view

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

Story 1 — Solo dev shipping a feature

Maps story 1 — solo dev shipping a feature to the Core Features documentation path, with the source page reserved for exact commands and updates.

Story 2 — Fleet farming

Maps story 2 — fleet farming to the Core Features documentation path, with the source page reserved for exact commands and updates.

Story 3 — Role pipeline with retry

Maps story 3 — role pipeline with retry to the Core Features documentation path, with the source page reserved for exact commands and updates.

Story 4 — Circuit breaker and crash recovery

Maps story 4 — circuit breaker and crash recovery to the Core Features documentation path, with the source page reserved for exact commands and updates.

Circuit breaker — permanent-looking failure

Maps circuit breaker — permanent-looking failure 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: Setup, The board at a glance, Flat view, Story 1 — Solo dev shipping a feature, Story 2 — Fleet farming. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: kanban, tutorial, walkthrough, cases, system. 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 tutorial before applying exact upstream commands.

Verify firstSetup

Open the source anchor for Setup 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 Setup; 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 The board at a glance 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