[Full Runtime][M3] Hermes Company Brain Adapter Smoke

[100yenadmin]

TL;DR

Provide a CLI/MCP/tool smoke proving Hermes and OpenClaw can both query Company Brain.

Owner Repo

electricsheephq/eva-brain

Milestone

Full Runtime M3: Hermes Runtime Coexistence

Why This Exists

The shared layer between runtimes should be Company Brain. This smoke proves a fact written from one runtime can be retrieved by the other without sharing private memory.

Acceptance Criteria

• Hermes can query GBrain through a documented CLI/MCP/tool path

• OpenClaw can query the same fact

• A fact written by OpenClaw is retrievable by Hermes and vice versa

• Private runtime transcripts remain out of Company Brain by default

Proof / Validation

• Cross-runtime fact smoke passes on Golden

Boundary Reminder

Repo boundary rule

• evaos-golden is the clone-safe customer VM baseline only. It owns runtime install scripts, service templates, local doctors, OpenClaw UI patches, Hermes/Eva Brain installers, and browser runtime setup.
• evaos-support-control owns private support/control-plane operations: VM health, snapshots, guarded restarts, support runbooks, drift checks, alert policy, and rollout orchestration.
• electric-sheep-website-dashboard-6158a244 owns customer/admin UI, Supabase migrations, runtime registry, product IA, support/admin actions, and usage ledger UI.
• evaos-ws-proxy owns authenticated customer /vm/... routing into customer VM runtimes and must not own support mutations.
• eva-brain is the intentional maintained GBrain fork for Company Brain, OpenClaw/Codex plugins, support KB setup, updater, and no-key OAuth extraction.
• openclaw-support-kb owns support knowledge base content and the source-scoped install/update contract only.

[100yenadmin]

Runtime reset note (2026-05-15): Hermes is explicitly out of the current feature scope. This adapter smoke should not block the current Golden/customer rollout.

Current rollout scope is OpenClaw + Company Brain/GBrain + support KB + browser GUI runtime + dashboard route. Hermes Company Brain adapter validation should return as a separate Hermes-specific sprint later.

[100yenadmin]

Correction from architecture regroup (2026-05-15): Hermes is not globally deferred. Hermes UI/runtime access and Company Brain/GBrain interop remain in scope.

Golden-specific guardrail: do not run hermes doctor or user-data migration on the empty/userless Golden VM. Interop smoke should be validated with a non-empty customer canary or fixture-backed runtime, not by pretending Golden has user state.