Required (maintainer, 2026-09-22) - but the shape must be redesigned, not ported. The source ask was a Hermes-parity interactive CLI with a plugin-contributed command registry, and that cannot be built as written: docs/architecture/organisation.md reserves cmd/ for CLI flag parsing and OS signal traps with no domain wiring, while a registry of commands with handlers and a RegisterCommand hook is exactly domain wiring.
Design within the constraint: cmd/ parses flags and routes; the command vocabulary and handlers live in a package below app/. The working precedent is already in this tree - the Telegram command registry exposes specs (gatewayCommandSpecs) that the surface renders and routes, with the spec list owned by the surface rather than the entrypoint. Mirror it: one spec type (name, description, category, usage, handler) owned by a package under internal/, consumed by cmd/archied.
Open decision before coding: what does plugin-contributed mean here? A RegisterCommand hook implies third-party code loaded at startup, which is the same trust boundary as archie-core-ze7y (stored workflow definitions executing argv). If plugins are wanted, settle that first.
Original text is in Dolt history; reworded 2026-09-22.
Notes
docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit 65aa5b4 ('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis.
Maintainer 2026-09-22: agreed - RETHINK REQUIRED, not a port. Evidence: the command registry that exists serves Telegram commands (gatewayCommandSpecs), not the CLI; cmd/archied is flag-based with no subcommand framework. A plugin-contributed CLI registry also cuts against docs/architecture/organisation.md ('cmd/ = CLI flag parsing only, no domain wiring'), so the shape needs redesigning before re-scoping.
Maintainer 2026-09-22: required, not parked. Redesign is about the layering and the plugin trust question, not about the feature being unwanted.
Imported from beads archie-core-1786637495642-223-81391a5c · GitHub #244 · type feature · priority P2 · created 2026-08-08
Required (maintainer, 2026-09-22) - but the shape must be redesigned, not ported. The source ask was a Hermes-parity interactive CLI with a plugin-contributed command registry, and that cannot be built as written: docs/architecture/organisation.md reserves cmd/ for CLI flag parsing and OS signal traps with no domain wiring, while a registry of commands with handlers and a RegisterCommand hook is exactly domain wiring.
Design within the constraint: cmd/ parses flags and routes; the command vocabulary and handlers live in a package below app/. The working precedent is already in this tree - the Telegram command registry exposes specs (gatewayCommandSpecs) that the surface renders and routes, with the spec list owned by the surface rather than the entrypoint. Mirror it: one spec type (name, description, category, usage, handler) owned by a package under internal/, consumed by cmd/archied.
Open decision before coding: what does plugin-contributed mean here? A RegisterCommand hook implies third-party code loaded at startup, which is the same trust boundary as archie-core-ze7y (stored workflow definitions executing argv). If plugins are wanted, settle that first.
Original text is in Dolt history; reworded 2026-09-22.
### Notes
docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit 65aa5b4 ('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis.
Maintainer 2026-09-22: agreed - RETHINK REQUIRED, not a port. Evidence: the command registry that exists serves Telegram commands (gatewayCommandSpecs), not the CLI; cmd/archied is flag-based with no subcommand framework. A plugin-contributed CLI registry also cuts against docs/architecture/organisation.md ('cmd/ = CLI flag parsing only, no domain wiring'), so the shape needs redesigning before re-scoping.
Maintainer 2026-09-22: required, not parked. Redesign is about the layering and the plugin trust question, not about the feature being unwanted.
---
_Imported from beads `archie-core-1786637495642-223-81391a5c` · GitHub #244 · type feature · priority P2 · created 2026-08-08_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Required (maintainer, 2026-09-22) - but the shape must be redesigned, not ported. The source ask was a Hermes-parity interactive CLI with a plugin-contributed command registry, and that cannot be built as written: docs/architecture/organisation.md reserves cmd/ for CLI flag parsing and OS signal traps with no domain wiring, while a registry of commands with handlers and a RegisterCommand hook is exactly domain wiring.
Design within the constraint: cmd/ parses flags and routes; the command vocabulary and handlers live in a package below app/. The working precedent is already in this tree - the Telegram command registry exposes specs (gatewayCommandSpecs) that the surface renders and routes, with the spec list owned by the surface rather than the entrypoint. Mirror it: one spec type (name, description, category, usage, handler) owned by a package under internal/, consumed by cmd/archied.
Open decision before coding: what does plugin-contributed mean here? A RegisterCommand hook implies third-party code loaded at startup, which is the same trust boundary as archie-core-ze7y (stored workflow definitions executing argv). If plugins are wanted, settle that first.
Original text is in Dolt history; reworded 2026-09-22.
Notes
docs/prds/hermes-gap-analysis.md (referenced above) was intentionally deleted in commit
65aa5b4('chore: cleanup', 2026-07-28) after it had already spawned this and ~14 sibling beads issues from its 60 identified gaps — it is not a broken link to restore. This issue's description is the surviving record of its slice of that analysis.Maintainer 2026-09-22: agreed - RETHINK REQUIRED, not a port. Evidence: the command registry that exists serves Telegram commands (gatewayCommandSpecs), not the CLI; cmd/archied is flag-based with no subcommand framework. A plugin-contributed CLI registry also cuts against docs/architecture/organisation.md ('cmd/ = CLI flag parsing only, no domain wiring'), so the shape needs redesigning before re-scoping.
Maintainer 2026-09-22: required, not parked. Redesign is about the layering and the plugin trust question, not about the feature being unwanted.
Imported from beads
archie-core-1786637495642-223-81391a5c· GitHub #244 · type feature · priority P2 · created 2026-08-08