kanban-worker

The Hermes Kanban worker lifecycle includes orient, work, heartbeat, and block or complete stages. Understanding these stages helps navigate specific workflow scenarios and avoid common pitfalls during execution and task handoffs.

Kanban workspace handling involves managing scratch spaces, shared persistent directories, and Git worktrees. Proper workspace management ensures data isolation and prevents context leaks across different tenants during task execution.

Effective Kanban summary crafting requires structuring metadata properly for coding, research, and review tasks. This ensures clear context handoffs and prevents execution errors when workers claim newly created cards.

Phantom ID errors during Kanban card claiming occur when cards created during execution are not properly tracked. Following correct claiming instructions and maintaining proper metadata structure prevents these execution errors.

Yes, Kanban worker execution requires tenant isolation to prevent context leaks across tenants. Proper context handling and metadata structure are necessary to maintain separation and ensure effective workflow processing.

Kanban worker context handling limitations include potential tenant context leaks and phantom card ID errors. Without proper metadata structure and workspace management, task handoffs and execution may fail.