Lucienne review addendum: Luci runtime independence + hermes_client reference

Reviewed: 2026-05-22 Reviewer: Lucienne Subject: /home/lucienne/workspace/reports/luci-control-room-runtime-independence-plan.md Additional source: https://github.com/lotsoftick/hermes_client Source note: /home/lucienne/workspace/mission-control/reports/mission-control-hermes-client-source-note.md

Verdict

Approved direction, with one important refinement: hermes_client should be treated as a concrete reference implementation for the Hermes-specific adapter layer, not as a replacement control room.

Luci's plan is directionally correct. It keeps Mission Control as the durable source of truth and treats Hermes, Claude Code, Codex, Kimi, Gemini, direct API scripts, browser harnesses, and future runtimes as replaceable adapters. The hermes_client repo strengthens that direction because it shows a working CLI/SSE/session-sync pattern for Hermes without requiring the Hermes gateway to become the orchestration layer.

What hermes_client changes in the plan

It does not change the north star.

It does add implementation evidence for these Phase 3 / Phase 5 items:

1. Hermes CLI adapter pattern
2. Spawn hermes with argv, not shell strings.
3. Stream stdout over SSE.
4. Capture stderr/session ids separately.

5. Kill or detach deliberately on browser disconnect.

6. Hermes profile cockpit pattern

7. UI agents can map to Hermes profiles.

8. Mission Control must still keep role/persona separate from runtime/profile.

9. Session reconciliation pattern

10. Hermes session JSON can remain source evidence while MC mirrors it into its own ticket/thread DB.

11. This is the right pattern for preserving CLI-originated and UI-originated turns.

12. Cron mirror pattern

13. Hermes cron files can be inspected and surfaced without moving production scheduling into Hermes cron.

14. MC scheduler remains authoritative for production scheduled work.

15. PTY setup/workbench pattern

16. A safe xterm.js/PT Y setup card is useful for runtime setup and diagnostics.
17. This must be gated: local/trusted by default, no unauthenticated remote PTY.

Required boundary

Do not fork or import hermes_client wholesale into Mission Control.

Mission Control's differentiated value is the governance cockpit:

• tickets
• WAT decisions
• runtime_sessions ledger
• history harvesting
• review/send-back loops
• scheduled-task visibility
• role/persona routing
• runtime switch continuity
• Telegram/topic routing invariants

hermes_client is valuable as a reference for Hermes-facing mechanics, not as the product architecture.

Recommended amendment to Luci's plan

Add a Phase 3.5 or Phase 5B item:

Hermes adapter reference hardening

Acceptance criteria:

• Create an MC adapter contract note for HermesProfileRuntimeAdapter.
• Explicitly define CliProcessInvocation, SseTurnStream, SessionFileReconciler, CronStateMirror, and PtySetupWorkbenchCard.
• Add security defaults: no hardcoded admin credentials, no open CORS, no unauthenticated PTY, no extra Telegram poller.
• Add a smoke test for one low-risk Hermes profile/session path before any production runtime routing changes.
• Keep production scheduling in MC unless a separate architecture decision says otherwise.

Things to preserve from Luci's current plan

• MC remains the source of truth.
• Control room remains governance/navigation, not a second live-state store.
• Runtime/provider/model/profile terminology is correct and should not be loosened.
• Subscription routing remains a capacity/reliability/sensitivity/tool-support decision, not only a token-cost decision.
• Telegram one-poller rule remains non-negotiable.
• Runtime-switch continuity must be validated with a low-risk session before claiming done.

Notes against overreach

This addendum is intentionally docs/inventory only.

No service restarts, runtime-profile changes, scheduler changes, Telegram routing changes, Hermes default changes, or WebUI changes were made or recommended as immediate actions.

Lucienne sign-off

PASS-WITH-NOTES for continuing the runtime-independence initiative.

The next safe action is to add hermes_client as a referenced implementation pattern in the control-room documentation and the living plan, then run Atlas-style signoff before any canonical MC runtime contract is changed.