Completion Lane Roadmap

The phase pages describe historical delivery order. Completion lanes describe the remaining product work required for Gormes to become Hermes in Go. The default rule is parity with Hermes across runtime behavior, config, commands, providers, and operator experience; any Go-native divergence must be explicit, tested, and visible to operators.

Use this page when deciding what to audit, plan, or build next. Use progress.json for the actual queue, and use Hermes And Honcho Feature Map when deciding where an upstream feature belongs in Go.

Lane Crosswalk

Lane Exit Gates

Lane Dependency Graph

Lane 0 Control Plane
  -> Lane 1 Native Agent Spine
  -> Lane 2 Goncho Memory
  -> Lane 3 Tools / Security / Skills
  -> Lane 4 Gateway / Cron / Delivery
  -> Lane 5 CLI / API / TUI / Release
  -> Lane 6 Learning Loop

The graph is directional for planning priority, not a total freeze. A row may advance out of order when it is fixture-ready and either unblocks an earlier lane, closes an operator-control parity gap, or is clearly isolated from the normal agent turn. In particular, CLI/config/provider/TUI parity rows are not late polish just because some of them live in Lane 5; they define how operators configure, run, steer, inspect, and recover Gormes.

Lane Pressure

Lane 0 — Control Plane Discipline

Exit when:

• every active/P0 row has test_commands or no_test_required;
• invalid progress blocks builder selection until a planner pass fixes it;
• repo-local skill routing is documented in AGENTS.md and CLAUDE.md;
• docs/development-skills/ is the canonical skill source and loader directories are symlinks;
• generated queue pages expose sane next work.

Gate:

go test ./internal/progress -count=1
go run ./cmd/progress validate
go test ./docs -count=1

Lane 1 — Native Agent Spine

Exit when:

• a normal CLI/API/gateway agent turn can run entirely through Go provider, prompt/context, memory, tool-call, retry, and finalization paths;
• Phase 4.I Python-free normal agent turn e2e harness is validated or every failing step has a narrower progress row;
• provider-specific behavior is isolated behind adapters and transcript fixtures;
• cancellation and retry behavior are observable and audited.

Gate:

go test ./internal/hermes ./internal/kernel ./internal/gateway ./internal/telemetry -count=1
# After Phase 4.I creates internal/e2e, include: go test ./internal/e2e -count=1

Lane 2 — Goncho Memory And Honcho Compatibility

Exit when:

• local Goncho covers Honcho sessions/messages/memory/search/provenance contracts required by Gormes;
• public compatibility names and fixtures exist for required honcho_* behavior;
• Phase 3.G proves local SDK-style compatibility and normal-turn memory integration without hosted Honcho;
• scoped recall and session lineage are deterministic.

Gate:

go test ./internal/goncho ./internal/gonchotools ./internal/memory ./internal/session ./internal/store -count=1

Lane 3 — Tool Surface, Security, And Skills

Exit when:

• descriptors drive schemas, toolsets, availability, audit, doctor, and prompt-visible exposure;
• dangerous operations are guarded before untrusted callers can reach them;
• Phase 2.G skills substrate supports the remaining Phase 5.F mechanics.

Gate:

go test ./internal/tools ./internal/plugins ./internal/skills ./internal/doctor -count=1

Lane 4 — Gateway, Channels, Cron, And Delivery

Exit when:

• shared gateway policy owns active-turn behavior, command dispatch, delivery, pairing, home channel, status, and restart;
• priority channels are stable and paused channels have explicit rows;
• cron, API, CLI, and tool control surfaces share one scheduler/store.

Gate:

go test ./internal/gateway ./internal/cron ./internal/discord ./internal/slack ./internal/channels/... -count=1

Lane 5 — CLI, API, TUI, Packaging, And Release

Exit when:

• the gormes binary covers Hermes-compatible operator CLI, API, TUI, service, installer, and release workflows without Python or Node runtime requirements;
• command names, aliases, root flags, slash commands, gateway handlers, dynamic plugin commands, config precedence, profiles, provider/model selection, logs/status/doctor/backup/update flows, and secret redaction have Go-native equivalents or explicit tested divergences;
• the local TUI and gateway surfaces preserve the Hermes operator experience for long coding turns: slash completion, busy-turn steering, status/footer evidence, tool progress, approvals, interrupts, edits, and recoverable failure messages;
• public docs and www.gormes.ai match the shipped install/runtime behavior.

Gate:

go test ./cmd/gormes ./internal/cli ./internal/apiserver ./internal/tui ./internal/tuigateway -count=1
go test ./docs -count=1
(cd www.gormes.ai && go test ./... -count=1)

Lane 6 — Learning Loop

Exit when:

• complex tasks can become reviewed, versioned skills;
• skill use is tied to outcomes and operator feedback;
• generated or stale skills never enter prompt injection without review.

Gate:

go test ./internal/skills ./internal/memory ./internal/kernel -count=1

Next-Lane Priority

Until Lane 1 and Lane 2 are closed, prefer work that removes Python from the normal agent turn, makes Goncho/Honcho compatibility testable, or closes a Hermes operator-control gap needed to run that work safely. The current closure rows are Phase 4.I and Phase 3.G plus the Phase 5.O/5.Q command, config, provider-control, and TUI-experience rows they depend on. Channel expansion, browser/media tools, plugins, and release packaging should not outrun those lanes unless a dependency row explicitly requires them.

Planner Split Rules

Use these when a lane row is too broad: