[
{
"id": "orch-scheduled-job-list-get",
"concept": "scheduled_job",
"verbs": "list/get",
"capability": "Scheduled job: list/get",
"semantics": "Enumerate the harness's install-scoped scheduled jobs and read one job's definition",
"hermes": "variant",
"openclaw": "yes",
"orchestrator": "yes",
"hermes_detail": "✓* `hermes cron list` over `~/.hermes/cron/jobs.json` (per profile); no per-job `get` at the pin — `cron status` reports the scheduler, not a job",
"openclaw_detail": "✓ `openclaw cron list` + `cron get <id>` (JSON) / `cron show <id>` over the shared state DB, via the Gateway",
"orchestrator_detail": "✓ `cron/jobs.json` per profile folder, in Hermes's own job schema (`docs/ORCHESTRATOR-IR.md` §6); the file IS the source of truth — there is no other store and no daemon copy of it",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "cron list"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "cron list"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "cron get"
}
],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "store",
"harness": "orchestrator",
"path": "cron/jobs.json"
},
{
"kind": "store",
"harness": "orchestrator",
"path": "profiles"
},
{
"kind": "code",
"path": "crates/harness/src/jobs.rs",
"symbol": "fn collect_hermes_shaped_jobs"
},
{
"kind": "code",
"path": "crates/harness/src/jobs.rs",
"symbol": "HarnessId::ORCHESTRATOR => crate::orchestrator_profile_dirs"
}
],
"orchestrator_note": "ORC-7: `jobs list|get --harness orchestrator` read every profile folder's `cron/jobs.json` through the SAME reader Hermes's rows go through (one implementation, a harness-id parameter), projecting schedule, payload, delivery, enabled/state and next/last run onto the uniform row and returning the native record verbatim from `get`. Executed against a seeded root (receipt orc7-orchestrator-registry-receipt-2026-09-04.json). Unlike the Hermes row there is no second door to miss: the orchestrator has no CLI, and its daemon writes this same file — the loop's tick claims and fires due jobs into it (ORC-5), so a listed job is a job something schedules.",
"provenance": "inventory concept 6 (Scheduled job), build list: observed + controlled, M",
"status": "partial",
"evidence": [
{
"kind": "store",
"harness": "hermes",
"path": "cron/jobs.json"
},
{
"kind": "store",
"harness": "hermes",
"path": "profiles/<name>/cron/jobs.json"
},
{
"kind": "code",
"path": "crates/harness/src/jobs.rs",
"symbol": "pub fn list_jobs"
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "\"harness.v1.jobs.list\""
},
{
"kind": "store",
"harness": "openclaw",
"path": "state/openclaw.sqlite"
},
{
"kind": "store",
"harness": "openclaw",
"path": "cron/jobs.json"
}
],
"note": "ORCH-7 landed the observed half: `harness.v1.jobs.list|get` and `supercode jobs list|get` read Hermes's `cron/jobs.json` (under HERMES_HOME and each `profiles/<name>/cron/`) and OpenClaw's `cron/jobs.json`, projecting both onto one row (schedule, payload, session target, delivery, enabled/state, next/last run, profile) with the native record returned verbatim by `get`. Still missing, and why this is not `implemented`: the read is over the harnesses' FILES only. Neither `hermes cron list` nor OpenClaw's Gateway `cron list` is called, so a job a running gateway holds but has not flushed is invisible; and OpenClaw upstream has moved its cron store into the shared SQLite state DB, which this loader does not open — such an install reports `absent_store` honestly rather than failing. Review 2026-09-03: at the pin OpenClaw stores jobs in `state/openclaw.sqlite` (`cron_jobs`); `cron/jobs.json` is only the table's store_key — the loader now reads the SQLite table first and the file as legacy (receipt orch7-openclaw-jobs-receipt-2026-09-03.json)."
},
{
"id": "orch-scheduled-job-create-update-pause-resume-run-delete",
"concept": "scheduled_job",
"verbs": "create/update/pause/resume/run/delete",
"capability": "Scheduled job: create/update/pause/resume/run/delete",
"semantics": "Create, edit, pause/resume, run-now and delete a scheduled job through the harness's own verb",
"hermes": "yes",
"openclaw": "variant",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes cron create|edit|pause|resume|run|remove` (all six verbs, install-scoped)",
"openclaw_detail": "✓* `openclaw cron add|edit|enable|disable|run|rm` — pause/resume are spelled `enable`/`disable`",
"orchestrator_detail": "✓ a job is a record in `cron/jobs.json`, written by the package's own `save(state, root)`; there is no CLI verb behind it — the write door is the daemon's operator socket, and the package's own CLI when the daemon is down",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "cron create"
},
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "cron edit"
},
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "cron pause"
},
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "cron resume"
},
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "cron run"
},
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "cron remove"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "cron add"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "cron edit"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "cron enable"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "cron disable"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "cron run"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "cron rm"
}
],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/harness/src/jobs_control.rs",
"symbol": "fn orchestrator_mutate"
},
{
"kind": "code",
"path": "crates/harness/src/jobs_control.rs",
"symbol": "fn orchestrator_args"
},
{
"kind": "code",
"path": "crates/harness/src/orchestrator_door.rs",
"symbol": "pub fn call"
},
{
"kind": "code",
"path": "sdk/orchestrator/operator.mjs",
"symbol": "export async function applyOperator"
},
{
"kind": "code",
"path": "sdk/orchestrator/mcp/bridge.mjs",
"symbol": "async function dispatchOperator"
},
{
"kind": "store",
"harness": "orchestrator",
"path": "cron/jobs.json"
}
],
"orchestrator_note": "ORC-13 landed the write half. `jobs create|update|pause|resume|run|delete --harness orchestrator` go through the orchestrator's OWN door the way hermes's rows go through `hermes cron …`: the uniform row is translated onto the IR's job vocabulary (§2.6 — typed schedule, prompt, hermes's `deliver` grammar) and handed to `applyOperator` inside the `supercode-orchestrator` package, which dispatches the matching `events.operator` and lets the reducer's `save` effect write the folder. supercode writes no file of that folder itself. Two doors, one code path: the daemon's local socket `<root>/orchestrator.sock` while the lease names a live pid (so the write is ordered on the loop's own queue and the running loop's state and the folder can never disagree), and `node bin/orchestrator.mjs <op> --root …` when it is down. After each verb the row is re-read through the SAME ORC-7 loader `jobs list` uses, `ran` narrates the exact door, and a verb the reducer refused surfaces the reducer's own line (`jobs_delete: no job …`) rather than a silent no-op. A field the model has no home for is refused, never dropped: there is no session-target (a fire opens its own binding on the job's origin surface, §4.3) and no `command`/`system_event`/`script` payload. Receipted end-to-end on a fresh temp root, both doors, with the folder hashed before and after (receipt orc13-orchestrator-write-door-receipt-2026-09-04.json).",
"provenance": "inventory concept 6 (Scheduled job), controlled tier",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "crates/harness/src/jobs_control.rs",
"symbol": "pub fn mutate"
},
{
"kind": "code",
"path": "crates/harness/src/jobs_control.rs",
"symbol": "fn hermes_command"
},
{
"kind": "code",
"path": "crates/harness/src/jobs_control.rs",
"symbol": "fn openclaw_command"
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "\"harness.v1.jobs.create\""
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "\"harness.v1.jobs.delete\""
},
{
"kind": "code",
"path": "crates/cli/src/main.rs",
"symbol": "fn job_mutation_cmd"
}
],
"note": "ORCH-18 landed the controlled tier: `harness.v1.jobs.create|update|pause|resume|run|delete` and `supercode jobs <verb> --harness X` translate the uniform row onto the HARNESS'S OWN verb and run it — `hermes cron create|edit|pause|resume|run|remove` with HERMES_HOME (a profile is its own HERMES_HOME), `openclaw cron add|edit|disable|enable|run|rm` through the Gateway whose URL and token supercode resolves from openclaw's own config via the registry connect descriptor. supercode runs no cron engine: after each verb the row is re-read through the ORCH-7 loader, every outcome narrates the exact command in `ran` with the credential redacted, and a failed verb surfaces the harness's own stderr. Receipted end-to-end on both pinned installs (orch18-hermes-jobs-receipt-2026-09-03.json on hermes 0.21.0 — 6 verbs, `hermes cron list --all` agreeing at every step; orch18-openclaw-jobs-receipt-2026-09-03.json on an isolated openclaw 2026.7.1-2 gateway — the same 6 verbs plus a step where the harness itself refuses and its sentence surfaces, `openclaw cron list --all --json` agreeing at every step). Honest edges, all refused rather than faked: Claude Code has jobs but no client-callable verb (they are created by the model inside a session), hermes has no session-target verb, and openclaw has no script payload. Measured against the pin: `openclaw cron edit` rejects `--json`."
},
{
"id": "orch-run-list-get",
"concept": "run",
"verbs": "list/get",
"capability": "Run: list/get",
"semantics": "List one job's past fires and read a fire's outcome",
"hermes": "variant",
"openclaw": "variant",
"orchestrator": "yes",
"hermes_detail": "✓* `hermes cron runs` (alias `history`) over `cron/executions.db`; the listing is per-scheduler, not a per-run `get`",
"openclaw_detail": "✓* `openclaw cron runs --id <jobId>` (with `--run-id` for one exact run) over the `cron_run_logs` table in the shared state DB",
"orchestrator_detail": "✓ `cron/executions.db` per profile folder, Hermes's `executions` columns verbatim (`docs/ORCHESTRATOR-IR.md` §6)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "cron runs"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "cron runs"
}
],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "store",
"harness": "orchestrator",
"path": "cron/executions.db"
},
{
"kind": "code",
"path": "crates/harness/src/runs.rs",
"symbol": "fn collect_hermes_shaped"
},
{
"kind": "code",
"path": "crates/harness/src/runs.rs",
"symbol": "fn orchestrator_ledgers"
}
],
"orchestrator_note": "ORC-7: `runs list|get --harness orchestrator` read every profile folder's fire ledger through the same reader as Hermes's, including ORCH-13's delivery join against that folder's own `delivery_obligations`. Executed against a seeded root with one fire and its obligation, which reported `delivered`. The ledger is only ever populated by the scheduler ORC-5 builds; reading it is complete now, and a home whose ledger does not exist reports `absent_store` per profile rather than an empty history.",
"provenance": "inventory concept 7 (Run / fire), build list: observed only, S; fact-finders F2/F4 closed",
"status": "partial",
"evidence": [
{
"kind": "store",
"harness": "hermes",
"path": "cron/executions.db"
},
{
"kind": "store",
"harness": "hermes",
"path": "profiles/<name>/cron/executions.db"
},
{
"kind": "store",
"harness": "openclaw",
"path": "state/openclaw.sqlite/cron_run_logs"
},
{
"kind": "code",
"path": "crates/harness/src/runs.rs",
"symbol": "pub fn list_runs"
},
{
"kind": "code",
"path": "crates/harness/src/runs.rs",
"symbol": "fn join_hermes_session"
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "\"harness.v1.runs.list\""
}
],
"note": "ORCH-8 landed the observed half: `harness.v1.runs.list|get` and `supercode runs list|get` read Hermes's `cron/executions.db` (under HERMES_HOME and each `profiles/<name>/cron/`, since a Hermes profile home is itself a full HERMES_HOME) and OpenClaw's `cron_run_logs` in the shared state DB (`state/openclaw.sqlite` at the pin — `cron_run_receipts` is upstream `main`'s spelling, not this version's), projecting both onto one row: run id, job, the harness's own status word, claimed/started/finished, error, and the session the fire opened. Hermes writes no link from a fire to its session, so that join is recovered from the `cron_<job_id>_<YYYYMMDD_HHMMSS>` id whose instant falls inside the fire's own [claimed_at, finished_at] window, then followed to a compression chain's tip; a fire with no session in its window answers null rather than borrowing a neighbour's. `get` returns the store's row verbatim beside the uniform one. Still missing, and why this is not `implemented`: the read is over the harnesses' STORES only — neither `hermes cron runs` nor OpenClaw's Gateway `cron runs` is called, so a fire a running scheduler holds but has not committed is invisible; the row's `delivery` field is filled by ORCH-13 from each harness's own delivery record (see `orch-delivery-target`), and stays null for a fire neither ledger matches."
},
{
"id": "orch-conversation-surface-key-and-scope",
"concept": "conversation",
"verbs": "surface key + scope",
"capability": "Conversation: surface key + scope",
"semantics": "A conversation is addressed by an explicit surface key and carries a declared scope/expiry policy",
"hermes": "variant",
"openclaw": "variant",
"orchestrator": "yes",
"hermes_detail": "✓* `session_key` = `agent:<profile>:<platform>:<chat_type>:<chat_id>[:<thread>][:<participant>]` in `state.db sessions`, listed by `hermes sessions list`; scope/expiry is an idle/daily config policy, not a per-conversation field",
"openclaw_detail": "✓* `agent:<id>:<channel>:<kind>:<id>[:thread]` (DMs collapse to `agent:<id>:main`), listed by `openclaw sessions list`; scope is `session.dmScope`/`groupScope` config",
"orchestrator_detail": "✓ `bindings` table per profile folder — the one record Hermes keeps inside its sessions table, ours as a first-class row (`docs/ORCHESTRATOR-IR.md` §2.5); the key renders as `agent:<profile>:<platform>:<chat_type>[:…]`, Hermes's own form",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "sessions list"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "sessions list"
}
],
"orchestrator_status": "partial",
"orchestrator_evidence": [
{
"kind": "store",
"harness": "orchestrator",
"path": "state.db/bindings"
},
{
"kind": "code",
"path": "crates/interchange/src/catalog.rs",
"symbol": "fn discover_orchestrator"
},
{
"kind": "code",
"path": "crates/interchange/src/catalog.rs",
"symbol": "fn orchestrator_descriptor"
}
],
"orchestrator_note": "ORC-7 landed the surface half: `sessions list --harness orchestrator` lists one row per binding with the surface badge, the trigger (`cron` when the row carries a `recurrence_job_id`, `webhook` on that platform, `channel` otherwise), the profile folder it belongs to, and the worker harness + session id the binding addresses. Missing: the SCOPE half. `expiry:` (idle minutes, daily reset hour, per-chat/per-user/per-thread scope) is a `config.yaml` block no reader surfaces, so a listed conversation does not say when it will expire; and the binding is not joinable to its worker transcript by any verb — reading the conversation still means addressing the worker harness's own session by hand.",
"provenance": "inventory concept 5 (Conversation), build list: observed + controlled, M; ORCH-3 derivation tables",
"status": "partial",
"evidence": [
{
"kind": "store",
"harness": "hermes",
"path": "state.db/sessions/session_key"
},
{
"kind": "store",
"harness": "openclaw",
"path": "agents/<agentId>/sessions"
},
{
"kind": "code",
"path": "crates/interchange/src/ontology/binding.rs",
"symbol": "pub fn parse_hermes_session_key("
},
{
"kind": "code",
"path": "crates/interchange/src/ontology/binding.rs",
"symbol": "pub fn parse_openclaw_session_key("
},
{
"kind": "code",
"path": "crates/interchange/src/ontology/surface.rs",
"symbol": "pub struct SurfaceKey {"
}
],
"note": "ORCH-3 landed the READ half of the key: both harnesses' session keys are parsed into the shared `SurfaceKey` noun (platform/channel, chat kind, chat id, thread, participant, agent/profile) — Hermes's from the `session_key` column plus the gateway columns that override it, OpenClaw's from the transcript header's `sessionKey` — and `inspect --json` exposes them. Two halves are missing: `sessions list` still prints title/cwd only, so a listed conversation cannot be picked by its surface (that is ORCH-6), and scope/expiry is not modelled at all — neither Hermes's idle/daily policy nor OpenClaw's `dmScope`/`groupScope` is read."
},
{
"id": "orch-conversation-new-reset-archive-delete",
"concept": "conversation",
"verbs": "new/reset/archive/delete",
"capability": "Conversation: new/reset/archive/delete",
"semantics": "Start a new, reset, archive or delete a conversation through the harness's own verb",
"hermes": "variant",
"openclaw": "variant",
"orchestrator": "variant",
"hermes_detail": "✓* `hermes sessions delete <id>` is per-session; `sessions archive` is a BULK filter verb (--older-than / --title / --cwd ...) with no per-session selector, so \"archive THIS conversation\" is not expressible. `/reset` IS carried by the ACP door (acp_adapter/server.py `_SLASH_COMMANDS`) and clears the conversation in place; `/new` is GATEWAY-only (gateway/slash_commands.py) and the ACP adapter sends any unrecognized `/word` to the model as prose",
"openclaw_detail": "✓* `openclaw sessions cleanup` (store maintenance) and `sessions compact` only — the pinned CLI has no `archive` or `delete` subcommand. BOTH `/new` and `/reset` are carried by its ACP door (openclaw@2026.7.1-2 `dist/commands-*.js` BASE_AVAILABLE_COMMANDS), so a live driven session can run them",
"orchestrator_detail": "✓* `/new` and `/reset` are chat commands the DAEMON applies to a binding (`docs/ORCHESTRATOR-IR.md` §4.5, §2.7), reachable from outside a chat through its operator door; there is no archive or delete — a binding ends, and its transcript belongs to the worker",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "sessions delete"
},
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "sessions prune"
},
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "sessions archive"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "sessions cleanup"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "sessions compact"
}
],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/harness/src/sessions_control.rs",
"symbol": "fn orchestrator_mutate"
},
{
"kind": "code",
"path": "crates/harness/src/sessions_control.rs",
"symbol": "SessionDoor::Daemon"
},
{
"kind": "code",
"path": "crates/harness/src/orchestrator_door.rs",
"symbol": "pub fn call"
},
{
"kind": "code",
"path": "sdk/orchestrator/operator.mjs",
"symbol": "export async function applyOperator"
},
{
"kind": "code",
"path": "crates/cli/src/main.rs",
"symbol": "async fn session_lifecycle_cmd"
},
{
"kind": "store",
"harness": "orchestrator",
"path": "state.db"
}
],
"orchestrator_note": "ORC-13: the two verbs the orchestrator's model HAS are now controlled. `sessions new|reset --harness orchestrator --surface <platform|chat_type|chat_id|thread_id|participant_id>` reach the very reducer a human's `/new` or `/reset` chat message reaches (§4.5) — through the daemon's operator socket while it is up, and through the package's own CLI when it is down. The conversation is named by its SURFACE, not by an id: an orchestrator conversation is a BINDING (§2.5) and a binding has no id of its own, so `--surface` is the selector and `--session` is refused for it. Afterwards the binding is re-read through the same ORCH-6 discovery loader `sessions list --harness orchestrator` uses, and its `end_reason` is what proves the verb landed. A surface with no LIVE binding refuses by name rather than reporting an empty success. Archive and delete stay refused, and not for want of a door: the model has neither — a binding ends, and the transcript belongs to the worker harness the binding addresses, which is where `sessions.archive|delete` is performed. Receipted on a fresh temp root with a seeded conversation (receipt orc13-orchestrator-write-door-receipt-2026-09-04.json).",
"provenance": "inventory concept 5 (Conversation), controlled tier; corrected against the pinned CLIs (the inventory lists `openclaw sessions archive|delete`, which v2026.7.1-2 does not register)",
"status": "partial",
"evidence": [
{
"kind": "code",
"path": "crates/harness/src/sessions_control.rs",
"symbol": "pub fn door"
},
{
"kind": "code",
"path": "crates/harness/src/sessions_control.rs",
"symbol": "pub async fn mutate"
},
{
"kind": "code",
"path": "crates/harness/src/sessions_control.rs",
"symbol": "async fn opencode_call"
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "\"harness.v1.sessions.reset\""
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "async fn mutate_session"
},
{
"kind": "code",
"path": "crates/cli/src/main.rs",
"symbol": "async fn live_session_command_cmd"
},
{
"kind": "code",
"path": "crates/cli/src/main.rs",
"symbol": "async fn session_control_cmd"
}
],
"note": "ORCH-19 landed the controlled tier as far as the harnesses' own doors reach: `harness.v1.sessions.new|reset|archive|delete` and `supercode sessions archive|delete --harness X` / `sessions new|reset --harness X --session <live runtime>` go through the HARNESS'S OWN door and re-read the row afterwards. Hermes: `/reset` typed into a live driven session over the same `send_input` a human's message takes, plus `hermes sessions delete <id> --yes`. OpenClaw: `/new` and `/reset` in a live driven session, joined through the registry's connect descriptor. Codex: `codex archive <id>` / `codex delete <id> --force` under an isolated CODEX_HOME. OpenCode: its own running server's session API (never a direct DB write). supercode's own store keeps the Domain 5 verb unchanged. Still `partial`, and each gap is a REFUSAL that names its reason, never a silent no-op: hermes has no per-session archive verb (its `sessions archive` is bulk-by-filter) and its ACP door does not carry `/new` (gateway-only, and an unrecognized `/word` there would go to the model as prose); openclaw registers neither `archive` nor `delete` at the pin; Claude Code publishes no conversation lifecycle verb at all (retention window only). Receipted on this box: orch19-codex-sessions-receipt-2026-09-03.json (real codex 0.152.0, isolated CODEX_HOME, archive moves the rollout into `archived_sessions/` and delete removes it, supercode's own listing agreeing both ways), orch19-hermes-reset-receipt-2026-09-03.json (real hermes-acp on an isolated HERMES_HOME + mock provider; `state.db` read read-only through a copy), orch19-openclaw-new-receipt-2026-09-03.json (isolated pinned 2026.7.1-2 gateway; the gateway itself answers \"New session started.\" / \"Session reset.\" where the mock model would have answered otherwise). Zero model spend in all three.",
"cost": "architectural"
},
{
"id": "orch-pending-request-list",
"concept": "pending_request",
"verbs": "list",
"capability": "Pending request: list",
"semantics": "Enumerate the permission/approval requests currently awaiting an answer",
"hermes": "variant",
"openclaw": "variant",
"orchestrator": "variant",
"hermes_detail": "✓* live only: a request exists while a turn is blocked on it, surfaced over the `hermes acp` bridge (ACP `session/request_permission`) or the chat prompt; `state.db` keeps no pending queue",
"openclaw_detail": "✓* live only over `openclaw acp` / the Gateway; `openclaw approvals get` fetches the exec-approvals POLICY snapshot, not a queue of outstanding requests",
"orchestrator_detail": "✓* a worker's permission/question request is relayed to the surface and held in `runtime.pending_requests`, which is NEVER persisted (`docs/ORCHESTRATOR-IR.md` §2.8, §4.2)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "acp"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "acp"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "approvals get"
}
],
"orchestrator_status": "absent",
"orchestrator_evidence": [],
"orchestrator_note": "Absent, and for the same reason it is only `partial` for the other two: a request exists solely inside the process holding the worker connection. Here that process is the daemon, which keeps them in `runtime.pending_requests` — never persisted (`docs/ORCHESTRATOR-IR.md` §2.8) — and publishes no query door. `approvals list --harness orchestrator` refuses: the orchestrator's runtime descriptor declares `respond_to_requests: false`, which is what makes the concept absent rather than empty.",
"orchestrator_cost": "architectural",
"provenance": "inventory concept 12 (Approval), build list: observed + controlled, M; corrected against the pinned CLIs (neither `hermes approvals` nor `openclaw approvals pending|resolve|grants` exists at the pin)",
"status": "partial",
"evidence": [
{
"kind": "code",
"path": "crates/harness/src/approvals.rs",
"symbol": "pub fn classify_live_request("
},
{
"kind": "code",
"path": "crates/harness/src/approvals.rs",
"symbol": "\"session/request_permission\" => acp_request(payload)"
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "harness.v1.approvals.list"
},
{
"kind": "code",
"path": "crates/harness/src/support.rs",
"symbol": "descriptor.runtime.capabilities.respond_to_requests"
}
],
"note": "ORCH-9 (observed tier): `harness.v1.approvals.list` / `supercode approvals list` enumerate the requests waiting for an answer in one uniform row (id, harness, kind, status, subject, session_id, runtime_id, requested_at_ms, age_ms, options). Both harnesses mount as `AcpRuntimeBackend`, so a request raised on a session supercode drives arrives as ACP `session/request_permission`, becomes listable while the turn is blocked on it, and stops being listable when `runtimes.respond` answers it. PARTIAL, and the pin is why: at hermes 0.21.0 there is no `hermes approvals` at all and at openclaw 2026.7.1-2 there is no `approvals pending | resolve | grants` (both upstream-main-only), so no STORED operator approval or mined allowlist proposal exists for supercode to read — the `live` kind is the whole listing, and `stored`/`proposal` are defined in the type for a later pin without being produced. Still missing at any pin: a request raised on a Hermes/OpenClaw surface supercode is not attached to, which needs a Gateway client, not a supercode-side registry."
},
{
"id": "orch-pending-request-resolve",
"concept": "pending_request",
"verbs": "resolve",
"capability": "Pending request: resolve",
"semantics": "Answer one outstanding request (allow once / allow always / deny) from any surface",
"hermes": "variant",
"openclaw": "variant",
"orchestrator": "variant",
"hermes_detail": "✓* live only: the answer travels back in-band on the ACP session that raised it",
"openclaw_detail": "✓* live only, in-band on the ACP/Gateway session that raised it",
"orchestrator_detail": "✓* an admin's reply on the surface answers the request (§4.2), and `worker.permission.default` decides when nobody answers in time",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "acp"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "acp"
}
],
"orchestrator_status": "absent",
"orchestrator_evidence": [],
"orchestrator_note": "Absent: the daemon's reducer already relays a worker's request to the surface and answers it from an admin's reply or the `worker.permission` timeout (ORC-4, §4.2), but that is the DAEMON resolving it. supercode has no channel into that process, and the registry says so mechanically — the orchestrator's runtime capabilities are all false, so `approvals resolve` never selects it.",
"orchestrator_cost": "architectural",
"provenance": "inventory concept 12 (Approval), controlled tier; ORCH-4 registry tiers",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "crates/harness/src/support.rs",
"symbol": "descriptor.runtime.capabilities.respond_to_requests"
},
{
"kind": "code",
"path": "crates/harness/src/support.rs",
"symbol": "harness.v1.approvals.resolve"
},
{
"kind": "code",
"path": "crates/harness/src/approvals.rs",
"symbol": "pub fn plan_reply"
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "async fn approvals_resolve"
},
{
"kind": "code",
"path": "crates/harness/src/runtime/adapters.rs",
"symbol": "impl RuntimeBackend for AcpRuntimeBackend"
}
],
"note": "Implemented for the LIVE kind, which is the whole of this concept at the pin: `harness.v1.approvals.resolve` takes a row id from `approvals.list` and one uniform decision (allow_once | allow_always | deny), translates it onto the option token the request itself enumerated — ACP `optionId` by `kind`, opencode's `once | always | reject`, supercode's own frontend decisions — and sends it through `harness.v1.runtimes.respond`, so both harnesses answer on their own ACP door with no adapter change. Codex's `*Approval` reverse request enumerates no options and no vocabulary is invented for it: those rows refuse by name and stay `runtimes.respond`'s to answer. The `stored` and `proposal` kinds stay typed and unproduced — neither hermes nor openclaw has an approvals store at the pin — so there is nothing left to resolve here until a re-pin lands one."
},
{
"id": "orch-profile-list-get",
"concept": "profile",
"verbs": "list/get",
"capability": "Profile: list/get",
"semantics": "Enumerate the harness's routed config homes and read one profile's definition",
"hermes": "yes",
"openclaw": "variant",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes profile list` + `profile show` over `~/.hermes/profiles/<name>`",
"openclaw_detail": "✓* `openclaw agents list` over `~/.openclaw/agents/<id>`; no per-agent `get`/`show` verb at the pin",
"orchestrator_detail": "✓ a profile IS a folder: the root of `SUPERCODE_ORCHESTRATOR_HOME` for `default`, `profiles/<name>/` otherwise (`docs/ORCHESTRATOR-IR.md` §6)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "profile list"
},
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "profile show"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "agents list"
}
],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "store",
"harness": "orchestrator",
"path": "config.yaml"
},
{
"kind": "store",
"harness": "orchestrator",
"path": "profiles"
},
{
"kind": "code",
"path": "crates/harness/src/profiles.rs",
"symbol": "fn orchestrator_rows"
},
{
"kind": "code",
"path": "crates/harness/src/profiles.rs",
"symbol": "OrchestratorProfile"
}
],
"orchestrator_note": "ORC-7: `profiles list|get --harness orchestrator` answer from the folders themselves — `kind: orchestrator_profile`, the folder as `home`, `default` flagged, the routes that target the profile counted across every folder's table, the conversations counted from the profile's own `bindings` table, and the `worker:` block's harness and model in the row (`worker` is a new optional column, `-` for every other harness). Executed against a seeded root with two profiles.",
"provenance": "inventory concept 2 (Profile / Agent), build list: observed + controlled, M",
"status": "implemented",
"evidence": [
{
"kind": "store",
"harness": "hermes",
"path": "profiles/<name>/config.yaml"
},
{
"kind": "store",
"harness": "hermes",
"path": "config.yaml/gateway/profile_routes"
},
{
"kind": "store",
"harness": "hermes",
"path": "state.db/sessions/profile_name"
},
{
"kind": "store",
"harness": "openclaw",
"path": "openclaw.json/agents/list"
},
{
"kind": "store",
"harness": "openclaw",
"path": "openclaw.json/bindings"
},
{
"kind": "store",
"harness": "openclaw",
"path": "agents/<agentId>/sessions"
},
{
"kind": "code",
"path": "crates/harness/src/profiles.rs",
"symbol": "pub fn list_profiles("
},
{
"kind": "code",
"path": "crates/harness/src/profiles.rs",
"symbol": "pub fn get_profile("
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "\"harness.v1.profiles.list\" | \"harness.v1.profiles.get\""
}
],
"note": "ORCH-10 landed the read tier through both harnesses' own files. Hermes: `HERMES_HOME/profiles/<name>/` plus the implicit `default` (HERMES_HOME itself), its route count from `gateway.profile_routes` in `config.yaml` and its session count from the `state.db` `profile_name` partition (NULL for the default). OpenClaw: `agents/<id>/` plus the `agents.list` array in `openclaw.json` (read as JSON5), its route count from `bindings[].agentId` and its session count from the same `agents/<id>/sessions` filter discovery uses. One row shape either way — name, harness, kind, home, default, routes, sessions, model — over `harness.v1.profiles.list|get` and `supercode profiles list|show`. What this row does NOT cover, by design: the CONTENTS of a profile home (SOUL.md, MEMORY.md, skills, tools) belong to the memory and skills rows, and creating or deleting one is the `profile: create/delete` row. Receipted on the build box against the installed harnesses: for hermes-agent 0.21.0, `supercode profiles show --harness hermes default` reports the same profile and the same model pin (`anthropic/claude-opus-4.6`) as `hermes profile list`; for the real `~/.openclaw`, the rows are the two agents `openclaw.json` declares with the one slack binding on `account-manager` and per-agent session counts of 5 and 4, matching the directories."
},
{
"id": "orch-profile-create-delete",
"concept": "profile",
"verbs": "create/delete",
"capability": "Profile: create/delete",
"semantics": "Create and delete a routed config home through the harness's own verb",
"hermes": "yes",
"openclaw": "yes",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes profile create` / `profile delete` (the inventory's \"create: setup flow, not enumerated\" is wrong at the pin — both are registered subcommands)",
"openclaw_detail": "✓ `openclaw agents add [name]` / `agents delete <id>` (deletes the workspace + state)",
"orchestrator_detail": "✓ creating a profile is creating the folder and its `config.yaml` through the package's `save()`; deleting it removes the record and RENAMES the folder into `profiles/.trash/<name>-<stamp>/`",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "profile create"
},
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "profile delete"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "agents add"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "agents delete"
}
],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/harness/src/profiles_control.rs",
"symbol": "fn orchestrator_mutate"
},
{
"kind": "code",
"path": "crates/harness/src/orchestrator_door.rs",
"symbol": "pub fn call"
},
{
"kind": "code",
"path": "sdk/orchestrator/reducer.mjs",
"symbol": "case 'profiles_create'"
},
{
"kind": "code",
"path": "sdk/orchestrator/operator.mjs",
"symbol": "export function performRemoveProfileDir"
},
{
"kind": "store",
"harness": "orchestrator",
"path": "profiles"
}
],
"orchestrator_note": "ORC-13: `profiles create|delete --harness orchestrator` go through the package's operator door. `create` adds an empty folder record to `state.profiles` and lets the reducer's `save` effect write the home — so `config.yaml` is emitted by the one writer that owns its canonical order, and the `save(load(root)) == root` invariant holds by construction rather than by care. `delete` removes the record and emits a `remove_profile_dir` effect the loop (and the cold path, through the same shared function) performs by RENAMING the folder to `profiles/.trash/<name>-<stamp>/`; nothing is ever unlinked, and both the package's loader and `orchestrator_profile_dirs` skip a dot-prefixed folder so a trashed home is not a profile. The root folder IS the `default` profile (§6) and refuses deletion by name. Two fields are refused rather than dropped: there is no clone source, and a workspace is the `worker.cwd` key inside the folder, not a creation argument. The row is re-read through the ORCH-10 loader afterwards. Receipted on a fresh temp root, both doors (receipt orc13-orchestrator-write-door-receipt-2026-09-04.json).",
"provenance": "inventory concept 2 (Profile / Agent), controlled tier",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "crates/harness/src/profiles_control.rs",
"symbol": "pub fn mutate"
},
{
"kind": "code",
"path": "crates/harness/src/profiles_control.rs",
"symbol": "fn hermes_command"
},
{
"kind": "code",
"path": "crates/harness/src/profiles_control.rs",
"symbol": "fn openclaw_command"
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "\"harness.v1.profiles.create\""
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "\"harness.v1.profiles.delete\""
},
{
"kind": "code",
"path": "crates/cli/src/main.rs",
"symbol": "fn profile_mutation_cmd"
}
],
"note": "ORCH-21 landed the controlled tier: `harness.v1.profiles.create|delete` and `supercode profiles create|delete --harness X` translate the uniform row onto the HARNESS'S OWN verb and run it — `hermes profile create [--clone-from <from>] --no-alias <name>` / `hermes profile delete --yes <name>` with HERMES_HOME pointing at the ROOT home the caller addressed, and `openclaw agents add <id> --workspace <dir> --non-interactive --json` / `openclaw agents delete <id> --force --json` over openclaw's own `OPENCLAW_STATE_DIR` / `OPENCLAW_CONFIG_PATH` contract (neither agents verb takes a `--url`/`--token`; `agents delete` offers the change to a running Gateway itself). supercode owns no config plane: after each verb the row is re-read through the ORCH-10 loader, every outcome narrates the exact command in `ran`, and a failed verb surfaces the harness's own stderr. Receipted end-to-end on both pinned installs (orch21-hermes-profiles-receipt-2026-09-03.json on hermes 0.21.0 — create → `hermes profile list` shows it → delete → gone, on an isolated HERMES_HOME with `~/.local/bin` untouched; orch21-openclaw-profiles-receipt-2026-09-03.json on an isolated openclaw 2026.7.1-2 gateway — the same round trip with `openclaw agents list --json` agreeing at every step). Honest edges, all refused rather than faked: Codex profiles are `[profiles.<name>]` tables a human authors in `config.toml` and supercode presets are compiled-in code, so both refuse with `unsupported_action`; hermes has no workspace flag and openclaw has no clone source, so either field is refused rather than dropped; openclaw's own non-interactive `agents add` requires `--workspace`, so `profiles.create --harness openclaw` requires it too. Two behaviors measured against the pin and handled here: `hermes profile create` also writes a wrapper script to `~/.local/bin/<name>` (a path HERMES_HOME does not govern), so the programmatic form passes `--no-alias`; and `openclaw agents delete` leaves an EMPTY `agents/<id>` shell behind after pruning the config entry, `agent/` and `sessions/`, so the ORCH-10 loader now drops an undeclared empty directory — `openclaw agents list` does not report it either."
},
{
"id": "orch-skills-list",
"concept": "skills",
"verbs": "list",
"capability": "Skills: list",
"semantics": "Enumerate the capability packages installed for a profile/agent",
"hermes": "yes",
"openclaw": "yes",
"orchestrator": "variant",
"hermes_detail": "✓ `hermes skills list` (installed) + `skills browse`/`search` (registries)",
"openclaw_detail": "✓ `openclaw skills list` + `skills info <name>` / `skills check`",
"orchestrator_detail": "✓* jobs and webhook subscriptions NAME skills (`skills: […]`), but the orchestrator keeps no skills store of its own — the skill is installed in the WORKER harness's home and read through that harness's own door",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "skills list"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "skills list"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "skills info"
}
],
"orchestrator_status": "absent",
"orchestrator_evidence": [],
"orchestrator_note": "Absent by design of the folder, not by omission: `docs/ORCHESTRATOR-IR.md` §6 lists no skills path, so `crate::skills` has no root to open and `skills list --harness orchestrator` refuses rather than answering an empty list. The honest answer for a profile's skills is its worker's answer — `skills list --harness <worker>` against the worker's home — which is a small delegation on top of the `worker:` block this change already reads.",
"orchestrator_cost": "trivial",
"provenance": "inventory concept 15 (Skills), build list: observed + controlled, S",
"status": "implemented",
"evidence": [
{
"kind": "store",
"harness": "hermes",
"path": "skills/SKILL.md"
},
{
"kind": "store",
"harness": "hermes",
"path": "profiles/<name>/skills"
},
{
"kind": "store",
"harness": "openclaw",
"path": "skills/SKILL.md"
},
{
"kind": "store",
"harness": "openclaw",
"path": "plugin-skills"
},
{
"kind": "store",
"harness": "openclaw",
"path": "workspace/skills"
},
{
"kind": "code",
"path": "crates/harness/src/skills.rs",
"symbol": "pub fn list_skills("
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "harness.v1.skills.list"
}
],
"note": "`crate::skills` opens each harness's own skill roots read-only and `harness.v1.skills.list` / `supercode skills list [--harness] [--scope]` return the uniform row (name, harness, scope, location, description, version, enabled): Hermes `HERMES_HOME/skills` plus `profiles/<name>/skills`, walked rather than listed because Hermes groups skills by category; OpenClaw's managed `<config>/skills`, `plugin-skills`, `workspace/skills` and `workspace/.agents/skills`. Registry-side browse/search (`hermes skills browse`, `openclaw skills search`) queries the hub, not the installed set this row enumerates; installing and removing is the controlled tier (`orch-skills-install-remove`)."
},
{
"id": "orch-skills-install-remove",
"concept": "skills",
"verbs": "install/remove",
"capability": "Skills: install/remove",
"semantics": "Install and remove a capability package through the harness's own verb",
"hermes": "yes",
"openclaw": "variant",
"orchestrator": "variant",
"hermes_detail": "✓ `hermes skills install` / `skills uninstall` (plus `tap` for sources)",
"openclaw_detail": "✓* `openclaw skills install` / `skills update` — no remove verb at the pin; removal goes through `openclaw plugins` or the managed directory",
"orchestrator_detail": "✓* installing a skill for a profile means installing it in that profile's WORKER harness home; the orchestrator has no installer of its own",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "skills install"
},
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "skills uninstall"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "skills install"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "skills update"
}
],
"orchestrator_status": "absent",
"orchestrator_evidence": [],
"orchestrator_note": "Absent: nothing in supercode installs a skill on the orchestrator's behalf. The worker's own skills door (ORCH-22) is what would do it, and choosing WHICH home a profile's skill lands in is part of the worker-home layout (`<harness>/` subfolder, §6) that no code writes yet.",
"orchestrator_cost": "architectural",
"provenance": "inventory concept 15 (Skills), controlled tier",
"status": "partial",
"evidence": [
{
"kind": "code",
"path": "crates/harness/src/skills_control.rs",
"symbol": "pub fn mutate_skill"
},
{
"kind": "code",
"path": "crates/harness/src/skills_control.rs",
"symbol": "fn hermes_command"
},
{
"kind": "code",
"path": "crates/harness/src/skills_control.rs",
"symbol": "fn openclaw_command"
},
{
"kind": "code",
"path": "crates/harness/src/skills_control.rs",
"symbol": "pub const OPENCLAW_REMOVE_REFUSAL"
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "\"harness.v1.skills.install\""
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "\"harness.v1.skills.remove\""
},
{
"kind": "code",
"path": "crates/cli/src/main.rs",
"symbol": "fn skills_install_cmd"
}
],
"note": "ORCH-22 landed the controlled tier for Hermes in full and OpenClaw by half, which is exactly what the pin publishes. `harness.v1.skills.install|remove` and `supercode skills install|remove --harness X` run the HARNESS'S OWN verb and return the row re-read through the ORCH-11 loader, with `ran` narrating what was executed. Hermes: `hermes skills install <identifier> --yes` / `hermes skills uninstall <name> --yes` with HERMES_HOME, receipted end to end on the installed 0.21.0 against an isolated home (docs/interop/research/orch22-hermes-skills-receipt.json: install -> `hermes skills list` names it -> remove -> gone). Its positional is a registry identifier or an HTTP(S) URL to a SKILL.md and its fetch is SSRF-guarded, so there is no local-directory form at all; supercode refuses a local path for hermes rather than handing it to a verb that cannot take it. OpenClaw: `openclaw skills install <skill-ref> [--global] [--as]` works, receipted against an isolated pinned install with a LOCAL directory ref (docs/interop/research/orch22-openclaw-skills-receipt.json), but the pin has NO `skills remove`, so the uniform verb refuses with UnsupportedAction rather than deleting files out of the harness's managed directory behind its back. That missing half is why this row is partial and not implemented; re-pinning OpenClaw to a build with a remove verb closes it."
},
{
"id": "orch-memory-show-search",
"concept": "memory",
"verbs": "show/search",
"capability": "Memory: show/search",
"semantics": "Read and search the persistent cross-session memory of a profile/agent",
"hermes": "variant",
"openclaw": "extension",
"orchestrator": "no",
"hermes_detail": "✓* built-in memory is `MEMORY.md`/`USER.md` per profile (always on); `hermes memory status|off|reset` configures the external provider — there is no CLI show/search verb, the files are the door",
"openclaw_detail": "ext `openclaw memory search|status|index|promote`, contributed by the bundled `memory-core` extension rather than the core CLI",
"orchestrator_detail": "",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "memory status"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "memory search"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "memory status"
}
],
"orchestrator_status": "not_applicable",
"orchestrator_evidence": [],
"orchestrator_note": "The orchestrator's model has no memory concept: §6 lists no memory document, and its `AGENTS.md` is the profile's PERSONA, read natively by the worker from its cwd (§2.2) — not a memory store supercode may show or search. A profile's memory is its worker harness's memory, read through that harness's own door. Not a gap; a deliberate absence.",
"provenance": "inventory concept 14 (Memory), build list: observed (show/search), S",
"status": "implemented",
"evidence": [
{
"kind": "store",
"harness": "hermes",
"path": "memories/MEMORY.md"
},
{
"kind": "store",
"harness": "hermes",
"path": "USER.md"
},
{
"kind": "store",
"harness": "hermes",
"path": "profiles/<name>/memories"
},
{
"kind": "store",
"harness": "openclaw",
"path": "workspace/MEMORY.md"
},
{
"kind": "store",
"harness": "openclaw",
"path": "workspace/memory"
},
{
"kind": "store",
"harness": "openclaw",
"path": "workspace/DREAMS.md"
},
{
"kind": "code",
"path": "crates/harness/src/memory.rs",
"symbol": "pub fn show_memory("
},
{
"kind": "code",
"path": "crates/harness/src/memory.rs",
"symbol": "pub fn search_memory("
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "harness.v1.memory.show"
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "harness.v1.memory.search"
}
],
"note": "ORCH-12 landed the read tier by opening each harness's own memory files, with no engine on supercode's side: `harness.v1.memory.show|search` and `supercode memory show|search --harness X` return one uniform document row (name, harness, scope, profile, path, size, updated_at, preview, truncated, and `content` only under `full`) and one match row (path, line, excerpt) from a case-insensitive substring scan (`--regex` for a pattern). Hermes 0.21.0: `get_memory_dir()` is `get_hermes_home()/\"memories\"` holding `MEMORY.md` (the agent's notes) and `USER.md` (what it knows about the user) (`tools/memory_tool.py:55-57` at tag `v2026.7.20`), read for HERMES_HOME itself (scope `user`) and for every `profiles/<name>` home (scope `profile`), plus the root-level `MEMORY.md`/`USER.md` names Hermes's own export manifest lists (`hermes_cli/profiles.py:238`). OpenClaw 2026.7.1-2: memory-core classifies a workspace-relative path as memory when it is `MEMORY.md`, `DREAMS.md`/`dreams.md`, or under `memory/` (`extensions/memory-core/src/memory/qmd-manager.ts:156-165` at tag `v2026.7.1-2`), relative to the agent workspace `resolveAgentWorkspaceDir` names — the agent's own `workspace` key in `openclaw.json`, else `$OPENCLAW_WORKSPACE_DIR` / `<home>/workspace` (+`$OPENCLAW_PROFILE`) for the default agent and `<home>/workspace-<id>` for any other (`src/agents/agent-scope-config.ts:181`, `src/agents/workspace-default.ts:12`) — so the files are read directly and no gateway or search index is required. That precedence, and the `main`-then-first default for a config-less install, were corrected against `openclaw memory status` on the pinned CLI (`docs/interop/research/orch12-memory-receipt-2026-09-03.json`), which also shows why the read tier opens the files rather than shelling out: `openclaw memory search` needs a paid embeddings provider and a built index. `hermes memory status|off` and `openclaw memory search|index|forget|promote|reset` stay the harnesses' own verbs; the write side (forget/reset) is out of scope by demand, so this row is the show/search pair only."
},
{
"id": "orch-delivery-target",
"concept": "delivery_target",
"verbs": "on jobs/runs",
"capability": "Delivery target on jobs/runs",
"semantics": "Where a job's or turn's output is delivered, as a first-class field on the job/run",
"hermes": "variant",
"openclaw": "variant",
"orchestrator": "yes",
"hermes_detail": "✓* job `deliver` = origin|local|home|explicit plus the `delivery_obligations` table in `state.db` (state/attempts/last_error); `hermes send --to <platform>[:chat[:thread]]` is the standalone door",
"openclaw_detail": "✓* job `--channel`/`--to` fields with announce|webhook|none; `openclaw message send` / `message broadcast` are the standalone doors",
"orchestrator_detail": "✓ `deliver` / `failure_deliver` on a job (`origin | home | local | <platform>:<chat>[:<thread>]`) and one `delivery_obligations` row per outbound message, Hermes's columns (`docs/ORCHESTRATOR-IR.md` §2.6)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "send"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "message send"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "message broadcast"
}
],
"orchestrator_status": "partial",
"orchestrator_evidence": [
{
"kind": "store",
"harness": "orchestrator",
"path": "state.db/delivery_obligations"
},
{
"kind": "code",
"path": "crates/harness/src/runs.rs",
"symbol": "fn hermes_delivery"
},
{
"kind": "code",
"path": "crates/harness/src/jobs.rs",
"symbol": "fn hermes_row"
}
],
"orchestrator_note": "ORC-7: the `deliver` field is read on every orchestrator job row, and a fire's actual delivery (target, state, attempts, last error, delivered instant) is joined from the profile folder's own `delivery_obligations` by the same ORCH-13 code path Hermes's rows use — executed and observed `delivered` on the seeded fire. Missing, exactly as for Hermes: the obligation ledger has no listing verb of its own, so an obligation not tied to a fire (a turn's reply, a webhook's answer) is invisible; and `local`/`home` targets name no platform surface, so those fires answer `None` rather than a guessed destination.",
"provenance": "inventory concept 9 (Delivery target), build list: observed; sending later by demand, S",
"status": "partial",
"evidence": [
{
"kind": "store",
"harness": "hermes",
"path": "state.db/delivery_obligations"
},
{
"kind": "store",
"harness": "hermes",
"path": "cron/jobs.json"
},
{
"kind": "store",
"harness": "openclaw",
"path": "state/openclaw.sqlite/cron_run_logs"
},
{
"kind": "store",
"harness": "openclaw",
"path": "state/openclaw.sqlite/cron_jobs"
},
{
"kind": "code",
"path": "crates/harness/src/jobs.rs",
"symbol": "pub struct JobDeliver"
},
{
"kind": "code",
"path": "crates/harness/src/runs.rs",
"symbol": "fn hermes_delivery"
},
{
"kind": "code",
"path": "crates/harness/src/runs.rs",
"symbol": "fn openclaw_delivery"
}
],
"note": "ORCH-13 landed the READ this row is: a job row's `deliver` carries `{target, chat_id, thread_id, account, mode}` and a run row's `delivery` carries `{target, state, attempts, last_error, delivered_at}`, both through `harness.v1.jobs.list|get` / `runs.list|get` and a `DELIVERY` column on both CLI tables. Hermes: the job's `deliver` word plus its `origin{platform, chat_id, thread_id}`, and the `delivery_obligations` ledger inside `state.db` (`gateway/delivery_ledger.py`) for the outcome. OpenClaw: `delivery_mode` and the `delivery_channel`/`to`/`thread_id`/`account_id` columns of `cron_jobs` (folded in beside `job_json.delivery`), plus `cron_run_logs.delivery_status`/`delivery_error`/`delivered` for the outcome — with the address joined from the job, because the run log records only whether a delivery happened. Still missing, and why this is not `implemented`: (a) Hermes's ledger is the GATEWAY's, keyed by conversation `session_key` and platform surface and naming no job and no fire, so a fire is matched to it by the fire's own [claimed_at, finished_at] window (session key first, the job's delivery surface second), and an execution timestamp carrying no UTC offset cannot be placed on the ledger's epoch line at all — it answers null rather than assuming a timezone; (b) the read is over the harnesses' STORES only: neither harness's CLI is called, so a delivery a running gateway holds but has not committed is invisible. Sending stays deliberately out of scope — supercode never runs a channel.",
"cost": "architectural"
},
{
"id": "orch-channel-list-status",
"concept": "channel",
"verbs": "list/status",
"capability": "Channel: list/status",
"semantics": "Enumerate the transports/accounts the install is connected to and report each one's health",
"hermes": "variant",
"openclaw": "yes",
"orchestrator": "yes",
"hermes_detail": "✓* platform blocks in `config.yaml`; `hermes gateway list` reports profiles + gateway status and `hermes send --list` enumerates deliverable targets — there is no channels noun",
"openclaw_detail": "✓ `openclaw channels list|status|capabilities|logs` (plus add/remove/login/logout)",
"orchestrator_detail": "✓ `platforms:` blocks per profile folder, Hermes-shaped, with credentials as `${NAME}` references, Hermes's own form — never values (`docs/ORCHESTRATOR-IR.md` §2.4, §6)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "gateway list"
},
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "send"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "channels list"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "channels status"
}
],
"orchestrator_status": "partial",
"orchestrator_evidence": [
{
"kind": "store",
"harness": "orchestrator",
"path": "config.yaml"
},
{
"kind": "code",
"path": "crates/harness/src/channels.rs",
"symbol": "fn hermes_rows"
},
{
"kind": "code",
"path": "crates/harness/src/channels.rs",
"symbol": "HarnessId::ORCHESTRATOR => {"
}
],
"orchestrator_note": "ORC-7: `channels list|status --harness orchestrator` read each profile folder's `platforms:` block through the Hermes reader, with the env-variable fallback deliberately OFF for the orchestrator — a credential is a ref in the folder, so a variable Hermes happens to read can never conjure a channel this home never declared. `configured` is still decided by the key NAME (`is_credential_key`), so a `{dotenv: …}` map counts as configured and its value is never read or printed. Missing (the same half Hermes's row is missing): `status` is always `unknown`. The daemon does connect the adapters it has — `loopback` is the only one built (ORC-4; real platforms are ORC-9) — but no adapter reports liveness back to any store a reader could join, so the row cannot say more than `configured`.",
"provenance": "inventory concept 3 (Channel), build list: observed, S",
"status": "partial",
"evidence": [
{
"kind": "store",
"harness": "hermes",
"path": "config.yaml/platforms"
},
{
"kind": "store",
"harness": "openclaw",
"path": "openclaw.json/channels"
},
{
"kind": "code",
"path": "crates/harness/src/channels.rs",
"symbol": "pub fn list_channels("
},
{
"kind": "code",
"path": "crates/harness/src/channels.rs",
"symbol": "pub fn channel_status("
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "\"harness.v1.channels.list\" | \"harness.v1.channels.status\""
}
],
"note": "ORCH-14 landed the LIST half through both harnesses' own config files. Hermes: the `platforms:` block of `HERMES_HOME/config.yaml` (`enabled`, the platform's own credential keys, and the bridged `extra` map), plus the platforms `gateway/config.py::_apply_env_overrides` would enable from the environment alone — reported by the var's PRESENCE, never its value. OpenClaw: `channels.<name>` in `openclaw.json` (read as JSON5), split one row per `accounts.<accountId>` and named `<channel>/<accountId>`. One row shape either way — name, harness, kind, account, enabled, configured, status, sessions — over `harness.v1.channels.list|status` and `supercode channels list|status`, with the session count taken from the same discovery rows `sessions list` shows, bucketed by surface platform. No credential is read or emitted: `account` values come only from a fixed allowlist of public identifier key names and `configured` is decided by key NAME and by `env_var_os(..).is_some()`, proven by a scan of every emitted row — and of every CLI line — against the fixtures' fake secrets. Why this is not `implemented`: STATUS is live. Both harnesses answer a channel's connection state from a RUNNING gateway (`hermes gateway status`, `openclaw channels status` over the Gateway socket), so every row honestly reports `unknown` rather than inferring `up` from a config file; that half needs the Gateway client this repo does not have. Out of scope by design: OpenClaw's `channel_pairing_*`, `channel_ingress_events` and `delivery_queue_entries` tables in the state DB are the pairing, inbound-trigger and delivery-target concepts, not channel config."
},
{
"id": "orch-routing-list",
"concept": "routing",
"verbs": "list",
"capability": "Routing: list",
"semantics": "Show which surface tuples bind to which profile/agent",
"hermes": "variant",
"openclaw": "yes",
"orchestrator": "yes",
"hermes_detail": "✓* `gateway.profile_routes` in `config.yaml`, read/written with `hermes config get|set` — no dedicated routing verb",
"openclaw_detail": "✓ `openclaw agents bindings` (and `agents bind|unbind` to mutate)",
"orchestrator_detail": "✓ `gateway.profile_routes` in each profile folder's `config.yaml`, Hermes's own shape and precedence (thread > chat > guild > platform) (`docs/ORCHESTRATOR-IR.md` §2.3)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "config get"
},
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "config set"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "agents bindings"
}
],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "store",
"harness": "orchestrator",
"path": "config.yaml"
},
{
"kind": "code",
"path": "crates/harness/src/routes.rs",
"symbol": "fn hermes_rows"
},
{
"kind": "code",
"path": "crates/harness/src/routes.rs",
"symbol": "HarnessId::ORCHESTRATOR => {"
}
],
"orchestrator_note": "ORC-7: `routes list --harness orchestrator` reads every profile folder's route table with Hermes's own specificity weights, and emits the unmatched-traffic default row exactly once, for the ROOT folder — a named profile's config does not get to claim it. Executed against a seeded root; `--profile` filtering works because the rows carry the target profile like every other harness's.",
"provenance": "inventory concept 4 (Routing / binding), build list: observed; write later, S",
"status": "implemented",
"evidence": [
{
"kind": "store",
"harness": "hermes",
"path": "config.yaml"
},
{
"kind": "store",
"harness": "openclaw",
"path": "openclaw.json"
},
{
"kind": "code",
"path": "crates/harness/src/routes.rs",
"symbol": "pub fn list_routes"
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "\"harness.v1.routes.list\""
}
],
"note": "ORCH-15 (observed): `harness.v1.routes.list` / `supercode routes list` read Hermes `gateway.profile_routes` (config.yaml; weights thread 8 > chat 4 > guild 2 > platform 0) and OpenClaw `bindings[]` (openclaw.json; the documented cascade ranked exact peer 8 … channel 1) with the default profile/agent as the rank-0 row. Editing a route stays the harness's own config edit.",
"cost": "trivial"
},
{
"id": "orch-inbound-trigger-list",
"concept": "inbound_trigger",
"verbs": "list",
"capability": "Inbound trigger: list",
"semantics": "Enumerate the webhooks / mapped events that can open a turn without a human prompt",
"hermes": "yes",
"openclaw": "yes",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes webhook list` over dynamic subscriptions (`/webhooks/<name>`; `subscribe`/`remove`/`test` complete the set)",
"openclaw_detail": "✓ `openclaw hooks list` + `hooks info <name>` / `hooks check` over mapped hooks (e.g. `hook:gmail:<id>` sessions)",
"orchestrator_detail": "✓ `webhook_subscriptions.json` per profile folder, Hermes's shape; the route is `/webhooks/<name>` (`/p/<profile>/webhooks/<name>` for a named profile) and the secret is a ref (§2.6)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "webhook list"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "hooks list"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "hooks info"
}
],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "store",
"harness": "orchestrator",
"path": "webhook_subscriptions.json"
},
{
"kind": "code",
"path": "crates/harness/src/triggers.rs",
"symbol": "fn hermes_rows"
},
{
"kind": "code",
"path": "crates/harness/src/triggers.rs",
"symbol": "HarnessId::ORCHESTRATOR => {"
}
],
"orchestrator_note": "ORC-7: `triggers list --harness orchestrator` reads every profile folder's subscriptions through the Hermes reader, reporting name, events, delivery target, enabled, and `authenticated` by the PRESENCE of a secret — the value is never read. Executed against a seeded root. The daemon does serve `POST /webhooks/<name>` (ORC-5, HMAC-verified), but the port it bound is runtime state no store carries, so a listed trigger's row cannot say WHERE it is reachable — the same limit as the gateway-health row below.",
"provenance": "inventory concept 10 (Inbound trigger), build list: observed (list), S; note that `hermes hooks` is lifecycle shell hooks (Domain 7), not inbound",
"status": "implemented",
"evidence": [
{
"kind": "store",
"harness": "hermes",
"path": "webhook_subscriptions.json"
},
{
"kind": "store",
"harness": "hermes",
"path": "config.yaml"
},
{
"kind": "store",
"harness": "openclaw",
"path": "openclaw.json"
},
{
"kind": "code",
"path": "crates/harness/src/triggers.rs",
"symbol": "pub fn list_triggers"
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "\"harness.v1.triggers.list\""
}
],
"note": "ORCH-16 (observed): `harness.v1.triggers.list` / `supercode triggers list` read Hermes webhook subscriptions (`webhook_subscriptions.json`) + static routes (`platforms.webhook.extra.routes` in config.yaml) and OpenClaw's pinned `hooks` block (built-in /wake and /agent endpoints + `hooks.mappings[]`) from openclaw.json. Per-route HMAC secrets and the hook token are read for presence only and never emitted. Note: at the pin `openclaw hooks` manages INTERNAL lifecycle hook packs, not inbound triggers — the spec's CLI door was wrong; the config file is the store.",
"cost": "trivial"
},
{
"id": "orch-gateway-health",
"concept": "gateway_health",
"verbs": "status/health",
"capability": "Gateway health",
"semantics": "Report whether the always-on daemon that owns channels and automation is up and healthy",
"hermes": "yes",
"openclaw": "yes",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes gateway status` (plus `hermes status` for the whole install)",
"openclaw_detail": "✓ `openclaw gateway health` + `gateway status` (service + probe), `gateway probe`, `openclaw health`",
"orchestrator_detail": "✓ one daemon per home, whose lease `<home>/orchestrator.lock` names the serving pid; it multiplexes adapters, so like Hermes it has no single endpoint",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "gateway status"
},
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "status"
}
],
"openclaw_evidence": [
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "gateway health"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "gateway status"
},
{
"kind": "cli_verb",
"harness": "openclaw",
"verb": "health"
}
],
"orchestrator_status": "partial",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/harness/src/orchestrator.rs",
"symbol": "pub fn live_lease"
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "HarnessId::ORCHESTRATOR => {"
},
{
"kind": "code",
"path": "crates/cli/src/main.rs",
"symbol": "fn orchestrator_status_cmd"
}
],
"orchestrator_note": "ORC-7: the GATEWAY column of `harness list` and `supercode orchestrator status` both answer from the lease `<home>/orchestrator.lock` plus a liveness check on the pid it names, so a lease whose process is gone reports DOWN as a stale lease and never up. Executed: down → start → up → stop → down. Missing: everything a health answer holds beyond up/down. The daemon does bind a webhook listener (ORC-5) and connect its adapters, but the bound port and the per-adapter state and breaker live in `runtime` (§2.8), which is never persisted and which the daemon publishes only on its own stdout — so the row carries no endpoint, no uptime, no last tick, and no version (the entry is a Node module, not a CLI with `--version`).",
"provenance": "inventory concept 1 (Gateway), build list: observed (status/health), S",
"status": "partial",
"evidence": [
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "fn gateway_health("
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "fn openclaw_gateway_endpoint("
},
{
"kind": "code",
"path": "crates/harness/src/harness_service.rs",
"symbol": "fn probe_running_instance("
}
],
"note": "ORCH-17 (observed): every `harness.v1.harnesses.list` row carries `gateway {state up|down|unknown, endpoint, version, evidence, checked_at_ms}` and `supercode harness list` shows a GATEWAY column. State is derived from the UNI-7 running-instance probe (OpenClaw: TCP connect to the gateway endpoint resolved from openclaw.json — url, else port, else ws://127.0.0.1:18789; Hermes: state.db-wal freshness under ~/.hermes) and the executable version. Partial: Hermes's own `hermes gateway status` text IS consulted since #687 (launchd `supervised … (PID n)` / `not running` / `not installed` parsed; the WAL heuristic is the fallback), but it has no JSON form and Hermes exposes no single endpoint, so `endpoint` stays null; OpenClaw's `gateway status` needs the token and is not called.",
"cost": "trivial"
},
{
"id": "orch-board-init",
"concept": "board",
"verbs": "init",
"capability": "Board: init",
"semantics": "Create the board if missing",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban init`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow init` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban init"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'init'"
}
],
"orchestrator_note": "`supercode workflow init` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'init'"
}
],
"note": "supercode works a Hermes board with `supercode workflow init`, its own implementation of the verb."
},
{
"id": "orch-board-boards",
"concept": "board",
"verbs": "boards",
"capability": "Board: boards",
"semantics": "Manage a home's boards: list, create, rm, switch, show, rename, set-default-workdir, export, import",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban boards`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow boards` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban boards"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'boards'"
}
],
"orchestrator_note": "Archives are Hermes's own format (`hermes-kanban-board` manifest, scrubbed of machine-local state) and import both ways.",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'boards'"
}
],
"note": "Archives are Hermes's own format (`hermes-kanban-board` manifest, scrubbed of machine-local state) and import both ways."
},
{
"id": "orch-board-create",
"concept": "board",
"verbs": "create",
"capability": "Board: create",
"semantics": "File a card: assignee, parents, workspace, tenant, priority, triage, idempotency key, runtime cap, skills, retries, model, goal",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban create`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow create` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban create"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'create'"
}
],
"orchestrator_note": "`--project` resolves Hermes's projects registry (`projects.db` in the home) and anchors the card's worktree and branch as Hermes does; `--goal` runs the goal loop.",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'create'"
}
],
"note": "`--project` resolves Hermes's projects registry (`projects.db` in the home) and anchors the card's worktree and branch as Hermes does; `--goal` runs the goal loop."
},
{
"id": "orch-board-swarm",
"concept": "board",
"verbs": "swarm",
"capability": "Board: swarm",
"semantics": "A parallel worker graph with a verifier and a synthesizer over a shared blackboard root",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban swarm`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow swarm` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban swarm"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'swarm'"
}
],
"orchestrator_note": "`supercode workflow swarm` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'swarm'"
}
],
"note": "supercode works a Hermes board with `supercode workflow swarm`, its own implementation of the verb."
},
{
"id": "orch-board-list",
"concept": "board",
"verbs": "list",
"capability": "Board: list",
"semantics": "List cards, filtered and sorted",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban list`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow list` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban list"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'list'"
}
],
"orchestrator_note": "`supercode workflow list` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'list'"
}
],
"note": "supercode works a Hermes board with `supercode workflow list`, its own implementation of the verb."
},
{
"id": "orch-board-show",
"concept": "board",
"verbs": "show",
"capability": "Board: show",
"semantics": "A card with its thread, runs, diagnostics and handoff",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban show`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow show` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban show"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'show'"
}
],
"orchestrator_note": "`supercode workflow show` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'show'"
}
],
"note": "supercode works a Hermes board with `supercode workflow show`, its own implementation of the verb."
},
{
"id": "orch-board-assign",
"concept": "board",
"verbs": "assign",
"capability": "Board: assign",
"semantics": "Assign a card to a profile",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban assign`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow assign` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban assign"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'assign'"
}
],
"orchestrator_note": "`supercode workflow assign` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'assign'"
}
],
"note": "supercode works a Hermes board with `supercode workflow assign`, its own implementation of the verb."
},
{
"id": "orch-board-set-model",
"concept": "board",
"verbs": "set-model",
"capability": "Board: set-model",
"semantics": "Set or clear a card's model and provider",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban set-model`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow set-model` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban set-model"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'set-model'"
}
],
"orchestrator_note": "`supercode workflow set-model` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'set-model'"
}
],
"note": "supercode works a Hermes board with `supercode workflow set-model`, its own implementation of the verb."
},
{
"id": "orch-board-reclaim",
"concept": "board",
"verbs": "reclaim",
"capability": "Board: reclaim",
"semantics": "Release a running card's claim",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban reclaim`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow reclaim` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban reclaim"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'reclaim'"
}
],
"orchestrator_note": "`supercode workflow reclaim` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'reclaim'"
}
],
"note": "supercode works a Hermes board with `supercode workflow reclaim`, its own implementation of the verb."
},
{
"id": "orch-board-reassign",
"concept": "board",
"verbs": "reassign",
"capability": "Board: reassign",
"semantics": "Reassign, optionally reclaiming first",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban reassign`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow reassign` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban reassign"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'reassign'"
}
],
"orchestrator_note": "`supercode workflow reassign` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'reassign'"
}
],
"note": "supercode works a Hermes board with `supercode workflow reassign`, its own implementation of the verb."
},
{
"id": "orch-board-diagnostics",
"concept": "board",
"verbs": "diagnostics",
"capability": "Board: diagnostics",
"semantics": "Distress signals per card with suggested actions",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban diagnostics`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow diagnostics` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban diagnostics"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'diagnostics'"
}
],
"orchestrator_note": "Rules: repeated failures and crashes, stuck blocked, block/unblock cycling, stranded in ready, review deadlock, phantom card references, and supercode's own (repeated session loss, machine offline). Hermes's triage-auxiliary-model rule has no subject: supercode triages with sessions.",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'diagnostics'"
}
],
"note": "Rules: repeated failures and crashes, stuck blocked, block/unblock cycling, stranded in ready, review deadlock, phantom card references, and supercode's own (repeated session loss, machine offline). Hermes's triage-auxiliary-model rule has no subject: supercode triages with sessions."
},
{
"id": "orch-board-link",
"concept": "board",
"verbs": "link",
"capability": "Board: link",
"semantics": "Add a parent->child dependency",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban link`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow link` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban link"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'link'"
}
],
"orchestrator_note": "`supercode workflow link` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'link'"
}
],
"note": "supercode works a Hermes board with `supercode workflow link`, its own implementation of the verb."
},
{
"id": "orch-board-unlink",
"concept": "board",
"verbs": "unlink",
"capability": "Board: unlink",
"semantics": "Remove a dependency",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban unlink`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow unlink` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban unlink"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'unlink'"
}
],
"orchestrator_note": "`supercode workflow unlink` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'unlink'"
}
],
"note": "supercode works a Hermes board with `supercode workflow unlink`, its own implementation of the verb."
},
{
"id": "orch-board-claim",
"concept": "board",
"verbs": "claim",
"capability": "Board: claim",
"semantics": "Claim a ready card and print its workspace",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban claim`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow claim` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban claim"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'claim'"
}
],
"orchestrator_note": "`supercode workflow claim` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'claim'"
}
],
"note": "supercode works a Hermes board with `supercode workflow claim`, its own implementation of the verb."
},
{
"id": "orch-board-comment",
"concept": "board",
"verbs": "comment",
"capability": "Board: comment",
"semantics": "Append to a card's thread",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban comment`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow comment` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban comment"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'comment'"
}
],
"orchestrator_note": "`supercode workflow comment` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'comment'"
}
],
"note": "supercode works a Hermes board with `supercode workflow comment`, its own implementation of the verb."
},
{
"id": "orch-board-attach",
"concept": "board",
"verbs": "attach",
"capability": "Board: attach",
"semantics": "Attach a file to a card",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban attach`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow attach` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban attach"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'attach'"
}
],
"orchestrator_note": "`supercode workflow attach` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'attach'"
}
],
"note": "supercode works a Hermes board with `supercode workflow attach`, its own implementation of the verb."
},
{
"id": "orch-board-attachments",
"concept": "board",
"verbs": "attachments",
"capability": "Board: attachments",
"semantics": "List a card's attachments",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban attachments`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow attachments` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban attachments"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'attachments'"
}
],
"orchestrator_note": "`supercode workflow attachments` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'attachments'"
}
],
"note": "supercode works a Hermes board with `supercode workflow attachments`, its own implementation of the verb."
},
{
"id": "orch-board-attach-rm",
"concept": "board",
"verbs": "attach-rm",
"capability": "Board: attach-rm",
"semantics": "Delete an attachment",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban attach-rm`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow attach-rm` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban attach-rm"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'attach-rm'"
}
],
"orchestrator_note": "`supercode workflow attach-rm` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'attach-rm'"
}
],
"note": "supercode works a Hermes board with `supercode workflow attach-rm`, its own implementation of the verb."
},
{
"id": "orch-board-complete",
"concept": "board",
"verbs": "complete",
"capability": "Board: complete",
"semantics": "Mark cards done with a result, summary and metadata",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban complete`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow complete` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban complete"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'complete'"
}
],
"orchestrator_note": "`supercode workflow complete` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'complete'"
}
],
"note": "supercode works a Hermes board with `supercode workflow complete`, its own implementation of the verb."
},
{
"id": "orch-board-edit",
"concept": "board",
"verbs": "edit",
"capability": "Board: edit",
"semantics": "Correct a done card's result",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban edit`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow edit` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban edit"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'edit'"
}
],
"orchestrator_note": "`supercode workflow edit` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'edit'"
}
],
"note": "supercode works a Hermes board with `supercode workflow edit`, its own implementation of the verb."
},
{
"id": "orch-board-block",
"concept": "board",
"verbs": "block",
"capability": "Board: block",
"semantics": "Block cards with a typed reason",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban block`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow block` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban block"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'block'"
}
],
"orchestrator_note": "`supercode workflow block` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'block'"
}
],
"note": "supercode works a Hermes board with `supercode workflow block`, its own implementation of the verb."
},
{
"id": "orch-board-schedule",
"concept": "board",
"verbs": "schedule",
"capability": "Board: schedule",
"semantics": "Park cards in scheduled",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban schedule`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow schedule` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban schedule"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'schedule'"
}
],
"orchestrator_note": "`supercode workflow schedule` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'schedule'"
}
],
"note": "supercode works a Hermes board with `supercode workflow schedule`, its own implementation of the verb."
},
{
"id": "orch-board-unblock",
"concept": "board",
"verbs": "unblock",
"capability": "Board: unblock",
"semantics": "Return blocked or scheduled cards",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban unblock`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow unblock` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban unblock"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'unblock'"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "`UNBLOCK: ${args.reason}`"
}
],
"orchestrator_note": "`supercode workflow unblock` takes Hermes's flags (--reason is recorded as an `UNBLOCK:` comment) and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'unblock'"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "`UNBLOCK: ${args.reason}`"
}
],
"note": "`supercode workflow unblock` takes Hermes's flags (--reason is recorded as an `UNBLOCK:` comment) and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9)."
},
{
"id": "orch-board-request-review",
"concept": "board",
"verbs": "request-review",
"capability": "Board: request-review",
"semantics": "Move a card to review",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban request-review`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow request-review` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban request-review"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'request-review'"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "request_review:"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "export const requestReview"
}
],
"orchestrator_note": "`supercode workflow request-review` takes Hermes's flags: a card under a live claim is its worker's to hand off (the worker names its run as Hermes's expected_run_id does: HERMES_KANBAN_RUN_ID, or the run the board recorded for the calling session), anyone else passes --force; the reviewer who asked for changes is asked again; the handoff is recorded on the run (docs/architecture/orchestrator.md §2.9). The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine.",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'request-review'"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "request_review:"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "export const requestReview"
}
],
"note": "`supercode workflow request-review` takes Hermes's flags: a card under a live claim is its worker's to hand off (the worker names its run as Hermes's expected_run_id does: HERMES_KANBAN_RUN_ID, or the run the board recorded for the calling session), anyone else passes --force; the reviewer who asked for changes is asked again; the handoff is recorded on the run (docs/architecture/orchestrator.md §2.9). The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine."
},
{
"id": "orch-board-request-changes",
"concept": "board",
"verbs": "request-changes",
"capability": "Board: request-changes",
"semantics": "A reviewer returns the card to its implementer",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban request-changes`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow request-changes` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban request-changes"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'request-changes'"
}
],
"orchestrator_note": "`supercode workflow request-changes` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'request-changes'"
}
],
"note": "supercode works a Hermes board with `supercode workflow request-changes`, its own implementation of the verb."
},
{
"id": "orch-board-reopen-review",
"concept": "board",
"verbs": "reopen-review",
"capability": "Board: reopen-review",
"semantics": "Send review cards back",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban reopen-review`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow reopen-review` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban reopen-review"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'reopen-review'"
}
],
"orchestrator_note": "`supercode workflow reopen-review` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'reopen-review'"
}
],
"note": "supercode works a Hermes board with `supercode workflow reopen-review`, its own implementation of the verb."
},
{
"id": "orch-board-promote",
"concept": "board",
"verbs": "promote",
"capability": "Board: promote",
"semantics": "Move todo/blocked cards to ready",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban promote`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow promote` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban promote"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'promote'"
}
],
"orchestrator_note": "`supercode workflow promote` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'promote'"
}
],
"note": "supercode works a Hermes board with `supercode workflow promote`, its own implementation of the verb."
},
{
"id": "orch-board-archive",
"concept": "board",
"verbs": "archive",
"capability": "Board: archive",
"semantics": "Archive cards; delete archived ones",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban archive`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow archive` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban archive"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'archive'"
}
],
"orchestrator_note": "`supercode workflow archive` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'archive'"
}
],
"note": "supercode works a Hermes board with `supercode workflow archive`, its own implementation of the verb."
},
{
"id": "orch-board-tail",
"concept": "board",
"verbs": "tail",
"capability": "Board: tail",
"semantics": "Follow a card's events",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban tail`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow tail` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban tail"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'tail'"
}
],
"orchestrator_note": "`supercode workflow tail` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'tail'"
}
],
"note": "supercode works a Hermes board with `supercode workflow tail`, its own implementation of the verb."
},
{
"id": "orch-board-dispatch",
"concept": "board",
"verbs": "dispatch",
"capability": "Board: dispatch",
"semantics": "One dispatcher pass",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban dispatch`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow dispatch` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'dispatch'"
}
],
"orchestrator_note": "`supercode workflow dispatch` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'dispatch'"
}
],
"note": "supercode works a Hermes board with `supercode workflow dispatch`, its own implementation of the verb."
},
{
"id": "orch-board-daemon",
"concept": "board",
"verbs": "daemon",
"capability": "Board: daemon",
"semantics": "The dispatcher loop",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban daemon`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow daemon` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban daemon"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'daemon'"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "args['failure-limit']"
}
],
"orchestrator_note": "Also `serve`, with Hermes's --interval, --max, --failure-limit, --pidfile and --verbose; the orchestrator runs the same loop while it serves a home.",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'daemon'"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "args['failure-limit']"
}
],
"note": "Also `serve`, with Hermes's --interval, --max, --failure-limit, --pidfile and --verbose; the orchestrator runs the same loop while it serves a home."
},
{
"id": "orch-board-watch",
"concept": "board",
"verbs": "watch",
"capability": "Board: watch",
"semantics": "Stream the board's events",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban watch`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow watch` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban watch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'watch'"
}
],
"orchestrator_note": "`supercode workflow watch` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'watch'"
}
],
"note": "supercode works a Hermes board with `supercode workflow watch`, its own implementation of the verb."
},
{
"id": "orch-board-stats",
"concept": "board",
"verbs": "stats",
"capability": "Board: stats",
"semantics": "Counts per status and assignee, oldest ready age",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban stats`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow stats` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban stats"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'stats'"
}
],
"orchestrator_note": "Adds counts per machine.",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'stats'"
}
],
"note": "Adds counts per machine."
},
{
"id": "orch-board-notify-subscribe",
"concept": "board",
"verbs": "notify-subscribe",
"capability": "Board: notify-subscribe",
"semantics": "Subscribe a destination to a card's events",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban notify-subscribe`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow notify-subscribe` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban notify-subscribe"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'notify-subscribe'"
}
],
"orchestrator_note": "A supercode session address is told by the dispatcher; a chat-platform subscription is told through the orchestrator's channel adapter while the orchestrator serves the home (as Hermes's are told only while its gateway runs).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'notify-subscribe'"
}
],
"note": "A supercode session address is told by the dispatcher; a chat-platform subscription is told through the orchestrator's channel adapter while the orchestrator serves the home (as Hermes's are told only while its gateway runs)."
},
{
"id": "orch-board-notify-list",
"concept": "board",
"verbs": "notify-list",
"capability": "Board: notify-list",
"semantics": "List subscriptions",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban notify-list`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow notify-list` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban notify-list"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'notify-list'"
}
],
"orchestrator_note": "`supercode workflow notify-list` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'notify-list'"
}
],
"note": "supercode works a Hermes board with `supercode workflow notify-list`, its own implementation of the verb."
},
{
"id": "orch-board-notify-unsubscribe",
"concept": "board",
"verbs": "notify-unsubscribe",
"capability": "Board: notify-unsubscribe",
"semantics": "Remove a subscription",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban notify-unsubscribe`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow notify-unsubscribe` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban notify-unsubscribe"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'notify-unsubscribe'"
}
],
"orchestrator_note": "`supercode workflow notify-unsubscribe` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'notify-unsubscribe'"
}
],
"note": "supercode works a Hermes board with `supercode workflow notify-unsubscribe`, its own implementation of the verb."
},
{
"id": "orch-board-log",
"concept": "board",
"verbs": "log",
"capability": "Board: log",
"semantics": "A card's worker log",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban log`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow log` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban log"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'log'"
}
],
"orchestrator_note": "A pane session keeps no log file: `log` names the session whose transcript it is.",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'log'"
}
],
"note": "A pane session keeps no log file: `log` names the session whose transcript it is."
},
{
"id": "orch-board-runs",
"concept": "board",
"verbs": "runs",
"capability": "Board: runs",
"semantics": "A card's runs",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban runs`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow runs` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban runs"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'runs'"
}
],
"orchestrator_note": "`supercode workflow runs` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'runs'"
}
],
"note": "supercode works a Hermes board with `supercode workflow runs`, its own implementation of the verb."
},
{
"id": "orch-board-heartbeat",
"concept": "board",
"verbs": "heartbeat",
"capability": "Board: heartbeat",
"semantics": "A worker says it is alive",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban heartbeat`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow heartbeat` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban heartbeat"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'heartbeat'"
}
],
"orchestrator_note": "Recorded; supercode's dispatcher never relies on it (it reads liveness from the fleet or the pid).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'heartbeat'"
}
],
"note": "Recorded; supercode's dispatcher never relies on it (it reads liveness from the fleet or the pid)."
},
{
"id": "orch-board-assignees",
"concept": "board",
"verbs": "assignees",
"capability": "Board: assignees",
"semantics": "Profiles and their card counts",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban assignees`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow assignees` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban assignees"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'assignees'"
}
],
"orchestrator_note": "Adds each profile's lane (pane or headless).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'assignees'"
}
],
"note": "Adds each profile's lane (pane or headless)."
},
{
"id": "orch-board-context",
"concept": "board",
"verbs": "context",
"capability": "Board: context",
"semantics": "The text a worker reads first",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban context`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow context` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban context"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'context'"
}
],
"orchestrator_note": "`supercode workflow context` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'context'"
}
],
"note": "supercode works a Hermes board with `supercode workflow context`, its own implementation of the verb."
},
{
"id": "orch-board-specify",
"concept": "board",
"verbs": "specify",
"capability": "Board: specify",
"semantics": "Turn a triage card into a spec",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban specify`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow specify` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban specify"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'specify'"
}
],
"orchestrator_note": "With `--title/--body` it applies the spec; without, a session in the card's lane writes it (Hermes asks an auxiliary model).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'specify'"
}
],
"note": "With `--title/--body` it applies the spec; without, a session in the card's lane writes it (Hermes asks an auxiliary model)."
},
{
"id": "orch-board-decompose",
"concept": "board",
"verbs": "decompose",
"capability": "Board: decompose",
"semantics": "Fan a triage card into children it waits on",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban decompose`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow decompose` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban decompose"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'decompose'"
}
],
"orchestrator_note": "With `--child` it files them; without, a session in the card's lane does (Hermes asks an auxiliary model).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'decompose'"
}
],
"note": "With `--child` it files them; without, a session in the card's lane does (Hermes asks an auxiliary model)."
},
{
"id": "orch-board-gc",
"concept": "board",
"verbs": "gc",
"capability": "Board: gc",
"semantics": "Remove archived workspaces, old events and logs",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban gc`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow gc` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban gc"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'gc'"
}
],
"orchestrator_note": "`supercode workflow gc` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'gc'"
}
],
"note": "supercode works a Hermes board with `supercode workflow gc`, its own implementation of the verb."
},
{
"id": "orch-board-repair",
"concept": "board",
"verbs": "repair",
"capability": "Board: repair",
"semantics": "Integrity check and index repair",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `hermes kanban repair`",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ `supercode workflow repair` over the same kanban.db format",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban repair"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'repair'"
}
],
"orchestrator_note": "`supercode workflow repair` takes Hermes's flags and prints Hermes's lines, on the kanban.db Hermes reads (docs/architecture/orchestrator.md §2.9).",
"provenance": "hermes kanban --help @ 0.21.0 (parity/fixtures/hermes-help.txt); exercised on a scratch home through `supercode workflow`",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'repair'"
}
],
"note": "supercode works a Hermes board with `supercode workflow repair`, its own implementation of the verb."
},
{
"id": "orch-board-dispatch-gate",
"concept": "board_dispatch",
"verbs": "gate",
"capability": "Board dispatcher: gate",
"semantics": "The dispatcher runs where the home is served unless kanban.dispatch_in_gateway is false",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban daemon`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban daemon"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board.mjs",
"symbol": "kanban.dispatch_in_gateway"
}
],
"orchestrator_note": "The dispatcher runs where the home is served unless kanban.dispatch_in_gateway is false",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board.mjs",
"symbol": "kanban.dispatch_in_gateway"
}
],
"note": "The dispatcher runs where the home is served unless kanban.dispatch_in_gateway is false"
},
{
"id": "orch-board-dispatch-interval",
"concept": "board_dispatch",
"verbs": "interval",
"capability": "Board dispatcher: interval",
"semantics": "One tick every kanban.dispatch_interval_seconds (60, at least 1)",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban daemon`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban daemon"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "dispatch_interval_seconds"
}
],
"orchestrator_note": "One tick every kanban.dispatch_interval_seconds (60, at least 1)",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "dispatch_interval_seconds"
}
],
"note": "One tick every kanban.dispatch_interval_seconds (60, at least 1)"
},
{
"id": "orch-board-dispatch-live-settings",
"concept": "board_dispatch",
"verbs": "live-settings",
"capability": "Board dispatcher: live-settings",
"semantics": "The kanban settings are read again every tick",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban daemon`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban daemon"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "await laneState(root)"
}
],
"orchestrator_note": "The kanban settings are read again every tick",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "await laneState(root)"
}
],
"note": "The kanban settings are read again every tick"
},
{
"id": "orch-board-dispatch-workflow-ir",
"concept": "board_dispatch",
"verbs": "dispatch",
"capability": "Board: the whole dispatch behaviour as data",
"semantics": "Statuses, what runs in each, events, who may send them, guards, validators, actions, prompts and the dispatcher's order and caps are declared in the orchestration IR and interpreted",
"hermes": "variant",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓* hard-coded in kanban_db.py (dispatch_once and the task functions), a handful of kanban.* keys read from config.yaml",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/workflow.rs",
"symbol": "pub struct Workflow"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "initial:"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/workflow.mjs",
"symbol": "export function fire("
}
],
"orchestrator_note": "Orchestration.workflow (crates/interchange orchestration/workflow.rs): a statechart after ASL and XState, no modes or switches. Hermes's dispatcher is the built-in instance (hermes.workflow.yaml), its kanban.* keys the instance's params; a home's own workflow.yaml replaces it. The board engine (board/workflow.mjs) keeps no rule of its own.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/workflow.rs",
"symbol": "pub struct Workflow"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "initial:"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/workflow.mjs",
"symbol": "export function fire("
}
],
"note": "Orchestration.workflow (crates/interchange orchestration/workflow.rs): a statechart after ASL and XState, no modes or switches. Hermes's dispatcher is the built-in instance (hermes.workflow.yaml), its kanban.* keys the instance's params; a home's own workflow.yaml replaces it. The board engine (board/workflow.mjs) keeps no rule of its own."
},
{
"id": "orch-board-dispatch-emergency-stop",
"concept": "board_dispatch",
"verbs": "emergency-stop",
"capability": "Board dispatcher: emergency-stop",
"semantics": "The ESTOP sentinel (home or ~/.hermes) stops new starts; running work goes on",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban daemon`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban daemon"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "export function paused"
}
],
"orchestrator_note": "Also `supercode workflow pause|resume`.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "export function paused"
}
],
"note": "Also `supercode workflow pause|resume`."
},
{
"id": "orch-board-dispatch-auto-decompose",
"concept": "board_dispatch",
"verbs": "auto-decompose",
"capability": "Board dispatcher: auto-decompose",
"semantics": "Triage cards are decomposed automatically, auto_decompose_per_tick at a time",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban daemon`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban daemon"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "guard: params.auto_decompose"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "max: params.auto_decompose_per_tick"
}
],
"orchestrator_note": "By a session in the card's pane lane, where Hermes asks an auxiliary model. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "guard: params.auto_decompose"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "max: params.auto_decompose_per_tick"
}
],
"note": "By a session in the card's pane lane, where Hermes asks an auxiliary model. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine."
},
{
"id": "orch-board-dispatch-corrupt-board",
"concept": "board_dispatch",
"verbs": "corrupt-board",
"capability": "Board dispatcher: corrupt-board",
"semantics": "A corrupt board is skipped until its file changes",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban daemon`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban daemon"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "corrupt-seen"
}
],
"orchestrator_note": "A corrupt board is skipped until its file changes",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "corrupt-seen"
}
],
"note": "A corrupt board is skipped until its file changes"
},
{
"id": "orch-board-dispatch-stuck-warning",
"concept": "board_dispatch",
"verbs": "stuck-warning",
"capability": "Board dispatcher: stuck-warning",
"semantics": "Ready work and nothing started for six ticks is warned about",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban daemon`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban daemon"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "stuck[r.board] >= 6"
}
],
"orchestrator_note": "Ready work and nothing started for six ticks is warned about",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "stuck[r.board] >= 6"
}
],
"note": "Ready work and nothing started for six ticks is warned about"
},
{
"id": "orch-board-dispatch-single-dispatcher",
"concept": "board_dispatch",
"verbs": "single-dispatcher",
"capability": "Board dispatcher: single-dispatcher",
"semantics": "One dispatcher per board, across Hermes and supercode",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban daemon`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban daemon"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board.mjs",
"symbol": "holdDispatcherLock"
}
],
"orchestrator_note": "The same kanban/.dispatcher.lock Hermes's gateways take.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board.mjs",
"symbol": "holdDispatcherLock"
}
],
"note": "The same kanban/.dispatcher.lock Hermes's gateways take."
},
{
"id": "orch-board-dispatch-boards",
"concept": "board_dispatch",
"verbs": "boards",
"capability": "Board dispatcher: boards",
"semantics": "Every live board of the home is ticked; archived ones are not",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban daemon`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban daemon"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/store.mjs",
"symbol": "a board archived in its metadata is not dispatched"
}
],
"orchestrator_note": "Every live board of the home is ticked; archived ones are not",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/store.mjs",
"symbol": "a board archived in its metadata is not dispatched"
}
],
"note": "Every live board of the home is ticked; archived ones are not"
},
{
"id": "orch-board-dispatch-tick-lock",
"concept": "board_dispatch",
"verbs": "tick-lock",
"capability": "Board dispatcher: tick-lock",
"semantics": "One tick at a time per board, whoever ticks",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "holdBoardTickLock"
}
],
"orchestrator_note": "Hermes's kanban.db.dispatch.lock.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "holdBoardTickLock"
}
],
"note": "Hermes's kanban.db.dispatch.lock."
},
{
"id": "orch-board-dispatch-reaping",
"concept": "board_dispatch",
"verbs": "reaping",
"capability": "Board dispatcher: reaping",
"semantics": "Exited workers are reaped",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "detached: true, stdio: ['ignore', out, out]"
}
],
"orchestrator_note": "A worker is detached under its own shell and reaped by the system when the tick that spawned it has exited.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "detached: true, stdio: ['ignore', out, out]"
}
],
"note": "A worker is detached under its own shell and reaped by the system when the tick that spawned it has exited."
},
{
"id": "orch-board-dispatch-claims",
"concept": "board_dispatch",
"verbs": "claims",
"capability": "Board dispatcher: claims",
"semantics": "A claim with a TTL; a live worker's expiring claim is extended, a dead one's reclaimed",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function supervise"
}
],
"orchestrator_note": "A claim with a TTL; a live worker's expiring claim is extended, a dead one's reclaimed",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function supervise"
}
],
"note": "A claim with a TTL; a live worker's expiring claim is extended, a dead one's reclaimed"
},
{
"id": "orch-board-dispatch-orphans",
"concept": "board_dispatch",
"verbs": "orphans",
"capability": "Board dispatcher: orphans",
"semantics": "A running card with broken claim bookkeeping and nothing live behind it is requeued",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "orphaned_running"
}
],
"orchestrator_note": "A running card with broken claim bookkeeping and nothing live behind it is requeued",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "orphaned_running"
}
],
"note": "A running card with broken claim bookkeeping and nothing live behind it is requeued"
},
{
"id": "orch-board-dispatch-stale",
"concept": "board_dispatch",
"verbs": "stale",
"capability": "Board dispatcher: stale",
"semantics": "A worker past dispatch_stale_timeout_seconds with no heartbeat for an hour is stopped",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "stale: [{ by: [platform]"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "observe('stale'"
}
],
"orchestrator_note": "Headless lanes, as Hermes. A pane session is not staled: idle does not end its run (owner approval 2026-09-28, 'all of your kanban notes sound right', volter-manager-runtime briefs/dispatcher.md note (2): \"a run ends when its card is done or blocked or its session is closed; idle doesn't end it\"), and its liveness is read from the fleet each tick, not inferred from heartbeats. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "stale: [{ by: [platform]"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "observe('stale'"
}
],
"note": "Headless lanes, as Hermes. A pane session is not staled: idle does not end its run (owner approval 2026-09-28, 'all of your kanban notes sound right', volter-manager-runtime briefs/dispatcher.md note (2): \"a run ends when its card is done or blocked or its session is closed; idle doesn't end it\"), and its liveness is read from the fleet each tick, not inferred from heartbeats. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine."
},
{
"id": "orch-board-dispatch-crashes",
"concept": "board_dispatch",
"verbs": "crashes",
"capability": "Board dispatcher: crashes",
"semantics": "A worker gone without finishing its card is a crash; a clean exit is a protocol violation that trips the breaker; exit 75 is a rate limit, requeued without a failure",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "protocol_violation"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "HERMES_KANBAN_CRASH_GRACE_SECONDS"
}
],
"orchestrator_note": "The exit code is recorded by the shell the worker runs under; the grace after launch is HERMES_KANBAN_CRASH_GRACE_SECONDS (30). A pane session is lost, not crashed, and is resumed first.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "protocol_violation"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "HERMES_KANBAN_CRASH_GRACE_SECONDS"
}
],
"note": "The exit code is recorded by the shell the worker runs under; the grace after launch is HERMES_KANBAN_CRASH_GRACE_SECONDS (30). A pane session is lost, not crashed, and is resumed first."
},
{
"id": "orch-board-dispatch-max-runtime",
"concept": "board_dispatch",
"verbs": "max-runtime",
"capability": "Board dispatcher: max-runtime",
"semantics": "A card past max_runtime_seconds is stopped (SIGTERM, then SIGKILL) and counted",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "signal('SIGKILL')"
}
],
"orchestrator_note": "A card past max_runtime_seconds is stopped (SIGTERM, then SIGKILL) and counted",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "signal('SIGKILL')"
}
],
"note": "A card past max_runtime_seconds is stopped (SIGTERM, then SIGKILL) and counted"
},
{
"id": "orch-board-dispatch-dependencies",
"concept": "board_dispatch",
"verbs": "dependencies",
"capability": "Board dispatcher: dependencies",
"semantics": "A card waits in todo until every parent is done, then becomes ready",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "# recompute_ready"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "export function recomputeReady(board)"
}
],
"orchestrator_note": "A card waits in todo until every parent is done, then becomes ready. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "# recompute_ready"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "export function recomputeReady(board)"
}
],
"note": "A card waits in todo until every parent is done, then becomes ready. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine."
},
{
"id": "orch-board-dispatch-max-spawn",
"concept": "board_dispatch",
"verbs": "max-spawn",
"capability": "Board dispatcher: max-spawn",
"semantics": "kanban.max_spawn caps a board's running cards",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "max: params.max_spawn"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "max_spawn: Number(args.max)"
}
],
"orchestrator_note": "kanban.max_spawn caps a board's running cards",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "max: params.max_spawn"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "max_spawn: Number(args.max)"
}
],
"note": "kanban.max_spawn caps a board's running cards"
},
{
"id": "orch-board-dispatch-max-in-progress",
"concept": "board_dispatch",
"verbs": "max-in-progress",
"capability": "Board dispatcher: max-in-progress",
"semantics": "kanban.max_in_progress caps running cards across every board of the home",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "hostRunning"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function derivedMaxInProgress"
}
],
"orchestrator_note": "kanban.max_in_progress caps running cards across every board of the home; unset, it is Hermes's default from the host's memory (one per 512 MiB, 2 to 8, from /proc/meminfo; no cap where that cannot be read).",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "hostRunning"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function derivedMaxInProgress"
}
],
"note": "kanban.max_in_progress caps running cards across every board of the home; unset, it is Hermes's default from the host's memory (one per 512 MiB, 2 to 8, from /proc/meminfo; no cap where that cannot be read)."
},
{
"id": "orch-board-dispatch-memory-pressure",
"concept": "board_dispatch",
"verbs": "memory-pressure",
"capability": "Board dispatcher: memory-pressure",
"semantics": "Spawning stops or slows under host memory pressure",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function memoryPressure"
}
],
"orchestrator_note": "Read from /proc/meminfo as Hermes reads it (unknown elsewhere, which restricts nothing); it holds every start on this machine: one-shot workers and pane sessions whose card names this machine.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function memoryPressure"
}
],
"note": "Read from /proc/meminfo as Hermes reads it (unknown elsewhere, which restricts nothing); it holds every start on this machine: one-shot workers and pane sessions whose card names this machine."
},
{
"id": "orch-board-dispatch-review-reservation",
"concept": "board_dispatch",
"verbs": "review-reservation",
"capability": "Board dispatcher: review-reservation",
"semantics": "While review work waits, one slot is held back from the ready lane",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "reserve: { for: \"card.status == 'review'\", slots: 1 }"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "held for others"
}
],
"orchestrator_note": "While review work waits, one slot is held back from the ready lane. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "reserve: { for: \"card.status == 'review'\", slots: 1 }"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "held for others"
}
],
"note": "While review work waits, one slot is held back from the ready lane. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine."
},
{
"id": "orch-board-dispatch-default-assignee",
"concept": "board_dispatch",
"verbs": "default-assignee",
"capability": "Board dispatcher: default-assignee",
"semantics": "An unassigned ready card goes to kanban.default_assignee",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "implementer: card.assignee ?? params.default_assignee"
}
],
"orchestrator_note": "An unassigned ready card goes to kanban.default_assignee",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "implementer: card.assignee ?? params.default_assignee"
}
],
"note": "An unassigned ready card goes to kanban.default_assignee"
},
{
"id": "orch-board-dispatch-nonspawnable",
"concept": "board_dispatch",
"verbs": "nonspawnable",
"capability": "Board dispatcher: nonspawnable",
"semantics": "A card assigned to no profile of the home waits and is counted",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "report.nonspawnable"
}
],
"orchestrator_note": "A card assigned to no profile of the home waits and is counted",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "report.nonspawnable"
}
],
"note": "A card assigned to no profile of the home waits and is counted"
},
{
"id": "orch-board-dispatch-per-profile-cap",
"concept": "board_dispatch",
"verbs": "per-profile-cap",
"capability": "Board dispatcher: per-profile-cap",
"semantics": "kanban.max_in_progress_per_profile caps each profile",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "max: lane.capacity ?? params.max_in_progress_per_profile"
}
],
"orchestrator_note": "Also worker.capacity per profile and kanban.machines.<m>.capacity per machine, where an idle session holds its place. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "max: lane.capacity ?? params.max_in_progress_per_profile"
}
],
"note": "Also worker.capacity per profile and kanban.machines.<m>.capacity per machine, where an idle session holds its place. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine."
},
{
"id": "orch-board-dispatch-respawn-guard",
"concept": "board_dispatch",
"verbs": "respawn-guard",
"capability": "Board dispatcher: respawn-guard",
"semantics": "No respawn after an auth/quota failure, inside a rate-limit cooldown, after a fresh completion, or with an open PR",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "message: rate_limit_cooldown"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "message: recent_success"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "message: active_pr"
}
],
"orchestrator_note": "Every lane. A pane card whose session is lost is resumed rather than started twice, and the guard applies to what starts after that. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "message: rate_limit_cooldown"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "message: recent_success"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "message: active_pr"
}
],
"note": "Every lane. A pane card whose session is lost is resumed rather than started twice, and the guard applies to what starts after that. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine."
},
{
"id": "orch-board-dispatch-claim",
"concept": "board_dispatch",
"verbs": "claim",
"capability": "Board dispatcher: claim",
"semantics": "A ready card is claimed and a run opened before its worker starts",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "export function claimIn"
}
],
"orchestrator_note": "A ready card is claimed and a run opened before its worker starts",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "export function claimIn"
}
],
"note": "A ready card is claimed and a run opened before its worker starts"
},
{
"id": "orch-board-dispatch-workspaces",
"concept": "board_dispatch",
"verbs": "workspaces",
"capability": "Board dispatcher: workspaces",
"semantics": "A card's workspace is made: scratch, dir, or a git worktree (a project's anchored one)",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function resolveLocalWorkspace"
}
],
"orchestrator_note": "Another machine's card names its directory there.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function resolveLocalWorkspace"
}
],
"note": "Another machine's card names its directory there."
},
{
"id": "orch-board-dispatch-worker-launch",
"concept": "board_dispatch",
"verbs": "worker-launch",
"capability": "Board dispatcher: worker-launch",
"semantics": "The worker gets its profile, skills, model, provider, reasoning and the task environment",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "HERMES_KANBAN_RUN_ID"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/tools.mjs",
"symbol": "export async function boardTool"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/worker-prompt.mjs",
"symbol": "export function taskProtocol"
},
{
"kind": "code",
"path": "sdk/orchestrator/kanban-worker.mjs",
"symbol": "function recordSession"
},
{
"kind": "code",
"path": "sdk/orchestrator/mcp/server.mjs",
"symbol": "HERMES_ANSWERED"
}
],
"orchestrator_note": "Headless: Hermes's worker argv and environment; the worker runs no Hermes code, installed or not (its session recorded on the run, its harness's own memory, `worker.permission.unattended` for requests, the board tools answered by supercode's engine in board/tools.mjs, the task protocol by board/worker-prompt.mjs). A profile whose worker is Hermes runs Hermes as its harness. Pane: an interactive session with a session id the dispatcher chose.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "HERMES_KANBAN_RUN_ID"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/tools.mjs",
"symbol": "export async function boardTool"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/worker-prompt.mjs",
"symbol": "export function taskProtocol"
},
{
"kind": "code",
"path": "sdk/orchestrator/kanban-worker.mjs",
"symbol": "function recordSession"
},
{
"kind": "code",
"path": "sdk/orchestrator/mcp/server.mjs",
"symbol": "HERMES_ANSWERED"
}
],
"note": "Headless: Hermes's worker argv and environment; the worker runs no Hermes code, installed or not (its session recorded on the run, its harness's own memory, `worker.permission.unattended` for requests, the board tools answered by supercode's engine in board/tools.mjs, the task protocol by board/worker-prompt.mjs). A profile whose worker is Hermes runs Hermes as its harness. Pane: an interactive session with a session id the dispatcher chose."
},
{
"id": "orch-board-dispatch-worker-log",
"concept": "board_dispatch",
"verbs": "worker-log",
"capability": "Board dispatcher: worker-log",
"semantics": "Each worker writes to its card's log, rotated past worker_log_rotate_bytes",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function rotateLog"
}
],
"orchestrator_note": "Each worker writes to its card's log, rotated past worker_log_rotate_bytes",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function rotateLog"
}
],
"note": "Each worker writes to its card's log, rotated past worker_log_rotate_bytes"
},
{
"id": "orch-board-dispatch-spawn-failure",
"concept": "board_dispatch",
"verbs": "spawn-failure",
"capability": "Board dispatcher: spawn-failure",
"semantics": "A start that fails is recorded and counted",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "spawn_failed: # the launch itself failed"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "'spawn_failed'"
}
],
"orchestrator_note": "A start that fails is recorded and counted. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "spawn_failed: # the launch itself failed"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "'spawn_failed'"
}
],
"note": "A start that fails is recorded and counted. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine."
},
{
"id": "orch-board-dispatch-failure-breaker",
"concept": "board_dispatch",
"verbs": "failure-breaker",
"capability": "Board dispatcher: failure-breaker",
"semantics": "Consecutive failures past the limit block the card (gave_up)",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "export function recordFailure"
}
],
"orchestrator_note": "Consecutive failures past the limit block the card (gave_up)",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "export function recordFailure"
}
],
"note": "Consecutive failures past the limit block the card (gave_up)"
},
{
"id": "orch-board-dispatch-hooks",
"concept": "board_dispatch",
"verbs": "hooks",
"capability": "Board dispatcher: hooks",
"semantics": "Lifecycle hooks at claim, spawn, exit, stale claim, completion, block, update and each tick",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function fireHooks"
}
],
"orchestrator_note": "kanban.hooks.<hook> commands get the event as JSON on stdin; Hermes runs Python plugins at the same points.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function fireHooks"
}
],
"note": "kanban.hooks.<hook> commands get the event as JSON on stdin; Hermes runs Python plugins at the same points."
},
{
"id": "orch-board-dispatch-wal-checkpoint",
"concept": "board_dispatch",
"verbs": "wal-checkpoint",
"capability": "Board dispatcher: wal-checkpoint",
"semantics": "A WAL board is checkpointed after each tick",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "wal_checkpoint(PASSIVE)"
}
],
"orchestrator_note": "A WAL board is checkpointed after each tick",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "wal_checkpoint(PASSIVE)"
}
],
"note": "A WAL board is checkpointed after each tick"
},
{
"id": "orch-board-dispatch-review-lane",
"concept": "board_dispatch",
"verbs": "review-lane",
"capability": "Board dispatcher: review-lane",
"semantics": "Review cards are dispatched to a reviewer with the sdlc-review skill",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "session: reviewer"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "exit: [{ close_session: reviewer }]"
}
],
"orchestrator_note": "Review cards are dispatched to a reviewer with the sdlc-review skill. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "session: reviewer"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "exit: [{ close_session: reviewer }]"
}
],
"note": "Review cards are dispatched to a reviewer with the sdlc-review skill. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine."
},
{
"id": "orch-board-dispatch-goal-loop",
"concept": "board_dispatch",
"verbs": "goal-loop",
"capability": "Board dispatcher: goal-loop",
"semantics": "A goal card keeps its session working until done or its turn budget is spent",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'set-goal'"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "session_idle: # ours: the heartbeat"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function observeIdle"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "params.goal_mode_default)}}"
}
],
"orchestrator_note": "Goal cards keep Hermes's loop; beyond Hermes, every running pane card's idle session is asked each tick to decide done (request-review) or blocked, and a session that stays idle undecided for the turn budget has its card blocked needs_input for its creator. Headless workers get the goal environment. Beyond Hermes, `set-goal` sets goal mode on a live card and `kanban.goal_mode_default` on every new one. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'set-goal'"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "session_idle: # ours: the heartbeat"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function observeIdle"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "params.goal_mode_default)}}"
}
],
"note": "Goal cards keep Hermes's loop; beyond Hermes, every running pane card's idle session is asked each tick to decide done (request-review) or blocked, and a session that stays idle undecided for the turn budget has its card blocked needs_input for its creator. Headless workers get the goal environment. Beyond Hermes, `set-goal` sets goal mode on a live card and `kanban.goal_mode_default` on every new one. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine."
},
{
"id": "orch-board-dispatch-cleanup",
"concept": "board_dispatch",
"verbs": "cleanup",
"capability": "Board dispatcher: cleanup",
"semantics": "A completed card's scratch directory or worktree is removed once no child needs it",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "function cleanupWorkspace"
}
],
"orchestrator_note": "A completed card's scratch directory or worktree is removed once no child needs it",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "function cleanupWorkspace"
}
],
"note": "A completed card's scratch directory or worktree is removed once no child needs it"
},
{
"id": "orch-board-dispatch-notify-sessions",
"concept": "board_dispatch",
"verbs": "notify-sessions",
"capability": "Board dispatcher: notify-sessions",
"semantics": "Subscribed supercode sessions are told of their cards' events",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function notify"
}
],
"orchestrator_note": "Subscribed supercode sessions are told of their cards' events",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function notify"
}
],
"note": "Subscribed supercode sessions are told of their cards' events"
},
{
"id": "orch-board-dispatch-notify-chats",
"concept": "board_dispatch",
"verbs": "notify-chats",
"capability": "Board dispatcher: notify-chats",
"semantics": "Subscribed chats are told through the served home's channel adapters",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "export async function notifyChats"
}
],
"orchestrator_note": "Subscribed chats are told through the served home's channel adapters",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "export async function notifyChats"
}
],
"note": "Subscribed chats are told through the served home's channel adapters"
},
{
"id": "orch-board-dispatch-notify-kinds",
"concept": "board_dispatch",
"verbs": "notify-kinds",
"capability": "Board dispatcher: notify-kinds",
"semantics": "Hermes's terminal kinds are told; archived and unblocked move the cursor silently",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "notify:"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "export function noticeOf"
}
],
"orchestrator_note": "Who is told which events, in what words, is the workflow's notify (per audience: creator, worker, dependency, chat), transcribed from the notifier's kinds and texts in the built-in instance.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "notify:"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "export function noticeOf"
}
],
"note": "Who is told which events, in what words, is the workflow's notify (per audience: creator, worker, dependency, chat), transcribed from the notifier's kinds and texts in the built-in instance."
},
{
"id": "orch-board-dispatch-notify-drop",
"concept": "board_dispatch",
"verbs": "notify-drop",
"capability": "Board dispatcher: notify-drop",
"semantics": "A subscription whose sends fail 12 times in a row is dropped",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "MAX_SEND_FAILURES = 12"
}
],
"orchestrator_note": "A subscription whose sends fail 12 times in a row is dropped",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "MAX_SEND_FAILURES = 12"
}
],
"note": "A subscription whose sends fail 12 times in a row is dropped"
},
{
"id": "orch-board-dispatch-notify-archive",
"concept": "board_dispatch",
"verbs": "notify-archive",
"capability": "Board dispatcher: notify-archive",
"semantics": "An archived card's subscriptions are removed once told",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban dispatch`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban dispatch"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "task?.status === 'archived'"
}
],
"orchestrator_note": "An archived card's subscriptions are removed once told",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "task?.status === 'archived'"
}
],
"note": "An archived card's subscriptions are removed once told"
},
{
"id": "orch-board-dispatch-notify-creator",
"concept": "board_dispatch",
"verbs": "notify-creator",
"capability": "Board dispatcher: notify-creator",
"semantics": "A card's creator is subscribed when it files the card",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban create`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban create"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "engine.subscribe(b, created.id, address, 'creator')"
}
],
"orchestrator_note": "A card's creator is subscribed when it files the card",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "engine.subscribe(b, created.id, address, 'creator')"
}
],
"note": "A card's creator is subscribed when it files the card"
},
{
"id": "orch-board-dispatch-notify-inherit",
"concept": "board_dispatch",
"verbs": "notify-inherit",
"capability": "Board dispatcher: notify-inherit",
"semantics": "A child hears what its parents' subscribers hear",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban link`, the gateway's watcher and notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban link"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "function inheritSubscriptions"
}
],
"orchestrator_note": "A child hears what its parents' subscribers hear",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "function inheritSubscriptions"
}
],
"note": "A child hears what its parents' subscribers hear"
},
{
"id": "orch-board-dispatch-notify-artifacts",
"concept": "board_dispatch",
"verbs": "notify-artifacts",
"capability": "Board dispatcher: notify-artifacts",
"semantics": "A completed card's artifact files go to chat subscribers as uploads",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban notify-subscribe`, the gateway's notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban notify-subscribe"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function artifactsOf"
}
],
"orchestrator_note": "Its completion metadata's `artifacts`, then absolute paths its summary or result names; the Chat SDK adapter uploads them (`files`).",
"provenance": "Hermes 0.21.0 read as the reference: gateway/kanban_watchers.py (notifier); exercised through a stand-in adapter",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "function artifactsOf"
}
],
"note": "Its completion metadata's `artifacts`, then absolute paths its summary or result names; the Chat SDK adapter uploads them (`files`)."
},
{
"id": "orch-board-dispatch-notify-wake",
"concept": "board_dispatch",
"verbs": "notify-wake",
"capability": "Board dispatcher: notify-wake",
"semantics": "A subscriber's agent is woken by the notice (Hermes's notify+wake and wake modes)",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ Hermes's dispatcher (`hermes kanban notify-subscribe`, the gateway's notifier)",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban notify-subscribe"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "queue: sub.delivery_mode === 'notify'"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "if (mode !== 'notify' && wake)"
},
{
"kind": "code",
"path": "sdk/orchestrator/loop.mjs",
"symbol": "wake: (sub, text)"
}
],
"orchestrator_note": "Hermes's delivery modes on every subscription: `notify` is passive (a supercode session reads it at its next turn; a chat gets the message), `wake` starts a turn (a supercode session's idle turn; a chat's own session in the daemon), `notify+wake` does both. Sessions the board subscribes are `notify+wake`.",
"provenance": "Hermes 0.21.0 read as the reference: gateway/kanban_watchers.py (notifier); exercised through a stand-in adapter",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "queue: sub.delivery_mode === 'notify'"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/dispatch.mjs",
"symbol": "if (mode !== 'notify' && wake)"
},
{
"kind": "code",
"path": "sdk/orchestrator/loop.mjs",
"symbol": "wake: (sub, text)"
}
],
"note": "Hermes's delivery modes on every subscription: `notify` is passive (a supercode session reads it at its next turn; a chat gets the message), `wake` starts a turn (a supercode session's idle turn; a chat's own session in the daemon), `notify+wake` does both. Sessions the board subscribes are `notify+wake`."
},
{
"id": "orch-board-dispatch-reopen-invalidation",
"concept": "board_dispatch",
"verbs": "reopen",
"capability": "Board: reopen invalidates descendants",
"semantics": "A done card reopened pulls every descendant that moved on because of it back to todo, with its resume status, and stops a running one's worker",
"hermes": "variant",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓* dashboard only: moving a done card back in `hermes dashboard`'s kanban plugin runs `invalidate_descendants_for_parent_reopen`; `hermes kanban` has no reopen verb",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "dashboard"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'reopen'"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "invalidate_descendants"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "function invalidateDescendants"
}
],
"orchestrator_note": "`supercode workflow reopen <id>` is supercode's own verb for what Hermes does only from its dashboard, with Hermes's invalidation transcribed: its events (`descendant_invalidated`, `status` ancestor_reopened) and comment, a running one-shot descendant's worker terminated as Hermes terminates it; a pane session is told through its card's notices. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "case 'reopen'"
},
{
"kind": "code",
"path": "crates/interchange/src/orchestration/hermes.workflow.yaml",
"symbol": "invalidate_descendants"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "function invalidateDescendants"
}
],
"note": "`supercode workflow reopen <id>` is supercode's own verb for what Hermes does only from its dashboard, with Hermes's invalidation transcribed: its events (`descendant_invalidated`, `status` ancestor_reopened) and comment, a running one-shot descendant's worker terminated as Hermes terminates it; a pane session is told through its card's notices. The behaviour is data: a transition of the built-in workflow (hermes.workflow.yaml), run by the board engine."
},
{
"id": "orch-board-dispatch-reclaim-terminates",
"concept": "board_dispatch",
"verbs": "reclaim",
"capability": "Board: a reclaimed worker is stopped",
"semantics": "A run taken back (reclaim, archive, reopened ancestor) stops its worker and a superseded worker changes nothing",
"hermes": "yes",
"openclaw": "no",
"orchestrator": "yes",
"hermes_detail": "✓ `_terminate_reclaimed_worker`; tools refuse a superseded run",
"openclaw_detail": "— OpenClaw has no board at the pin",
"orchestrator_detail": "✓ supercode's dispatcher (sdk/orchestrator/board/)",
"hermes_evidence": [
{
"kind": "cli_verb",
"harness": "hermes",
"verb": "kanban reclaim"
}
],
"openclaw_evidence": [],
"orchestrator_status": "implemented",
"orchestrator_evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "function terminate(pid)"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/tools.mjs",
"symbol": "is no longer its current run"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "function workerRun"
}
],
"orchestrator_note": "One-shot workers on this host (by the claim's host, as Hermes checks) get SIGTERM, then SIGKILL if alive five seconds later, off the board's write lock; a pane session is a person-visible session and is never killed from the board. A worker names its run (Hermes's expected_run_id: HERMES_KANBAN_RUN_ID, or the run recorded for its session), and a superseded run changes nothing.",
"provenance": "Hermes 0.21.0 read as the reference: kanban_db.dispatch_once, gateway/kanban_watchers.py (dispatcher and notifier); exercised on scratch homes through supercode workflow",
"status": "implemented",
"evidence": [
{
"kind": "code",
"path": "sdk/orchestrator/board/engine.mjs",
"symbol": "function terminate(pid)"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/tools.mjs",
"symbol": "is no longer its current run"
},
{
"kind": "code",
"path": "sdk/orchestrator/board/cli.mjs",
"symbol": "function workerRun"
}
],
"note": "One-shot workers on this host (by the claim's host, as Hermes checks) get SIGTERM, then SIGKILL if alive five seconds later, off the board's write lock; a pane session is a person-visible session and is never killed from the board. A worker names its run (Hermes's expected_run_id: HERMES_KANBAN_RUN_ID, or the run recorded for its session), and a superseded run changes nothing."
}
]