Hermes Adapter Preview
The hermes-kanban adapter connects SDTK-AGENT workflows to a Hermes Kanban board — as a dry-run plan compiler. It shows exactly what cards and links a workflow would create, without creating any.
What ships today
sdtk-agent adapter hermes-kanban plan --workflow ./workflow.jsonThe adapter:
- compiles a workflow DAG into a Kanban card create/link plan
- validates configured profiles (
herwiki/herresearch/herorches/herdev) - never creates a live card — there is no live gateway in the published release
Fail-closed by design
If a runtime map asks for mode:"live", the currently published npm adapter refuses — fail-closed, not silently downgraded. This is deliberate: dispatching real work to external boards, bots, or messaging surfaces crosses a trust boundary that SDTK will only cross behind explicit, published, gated functionality.
What not to expect
No live Kanban cards, no bots, no Telegram/messaging dispatch, no remote workers. If you see the adapter in a workflow, it is planning — not dispatching.
Why a dry-run adapter is still useful
- Design review — see the full card/link topology a workflow implies before committing to it.
- Profile validation — catch misconfigured Hermes profiles at plan time, not dispatch time.
- Forward compatibility — workflows written against the adapter contract today will be ready if/when live dispatch ships.
Live dispatch is gated Gated
Live-mode source now ships in the published sdtk-agent-hermes-adapter@0.2.0, but Hermes live dispatch is still gated and validation-only — it is not public-ready. Live only engages behind a fail-closed preflight (config + live_ack + credential + gateway/board checks) and is being exercised for controlled real-box validation; public readiness waits for that real-box evidence plus independent review. Until then, these docs treat Hermes as dry-run/mock only — do not rely on live cards/bots/messaging.