Hermes Mission Control¶

Hermes Mission Control is Jamie's agent-ops coordination hub for the Pixoid crew: Pixoid, Quill, Tinker, and Boba.

Its primary namespace is agent-workflows because the durable knowledge is not the public wiki itself. The durable knowledge is how agents coordinate work: route governance, persona boundaries, issue-backed execution, handoffs, review gates, and durable truth routing.

Crew roles¶

• Pixoid: orchestrator, reviewer, route owner, final verifier.
• Tinker: builder for bounded implementation slices.
• Quill: scribe for vault/docs updates and compiled knowledge pages.
• Boba: explorer/researcher for external signal and reality checks.

What it controls¶

• Crew role boundaries and operating surfaces.
• GitHub issue/PR coordination as durable work truth.
• Obsidian/Git as knowledge and project truth.
• Discord as notification surface, not durable truth.
• Discord council-mode routing: @Crew/crew aliases call Pixoid as coordinator by default; direct worker mentions call individual profiles; bounded huddles collect one worker round, close deterministically, and suppress post-close worker chatter at the gateway layer.
• Cron output as context, not canonical project state.
• Verification gates before tracker closure.

Pixoid Review Surface¶

Interaction Mode Routing clarifies that chat is the command channel, not the whole Hermes interface. Pixoid should generate small review/control surfaces when Jamie needs to approve or steer work, while durable truth remains in GitHub issues/PRs, Obsidian hubs, handoffs, skills, and knowledge entrypoints.

The standard review surface includes status, evidence, risks, files/handles, verification run, options, and Pixoid's recommended next slice.

Discord council-mode hardening milestone¶

As of 2026-06-29, the stable Discord contract is coordinator-first and gateway-enforced:

• @Crew / <@&1521188694915158078> is a Pixoid/default coordinator call.
• crew:, get the crew, and calling the crew are Pixoid/default text aliases.
• @Boba, @Quill, and @Tinker are direct specialist calls in approved channels/threads; they do not answer ambient top-level-channel chatter.
• If Pixoid needs visible crew discussion, it opens a bounded huddle tied to the triggering message/origin, waits for one short worker round or timeout, closes the huddle, and returns one final answer.
• Closed huddle threads suppress ambient worker/bot chatter before model invocation; prompt-level silence is not the enforcement layer.
• Discord reply pings are not direct summons unless the message text explicitly mentions the bot or an owned council role.
• Re-adding the shared Crew role to all worker bots is not the default because it causes duplicate independent work in the user thread.

Routing significance¶

Hermes Mission Control feeds pixi-vault when compiler/publication rules are affected, and it feeds eval-trace when route quality or workflow evidence needs evaluation.

The project should not become a standalone namespace unless it grows an independent audience, source corpus, document types, and freshness lifecycle beyond the broader agent-workflows domain.

Cross-namespace links¶

• pixi-vault — source/output repo boundaries and namespace compiler rules.
• eval-trace — route-quality checks and failure-mode evaluation, including context overfitting.

Related pages¶

• Knowledge Pack Routing
• Agent Entrypoint Mesh
• Interaction Mode Routing
• Pixoid Crew Operating Model

Source¶

Compiled from Projects/Hermes Mission Control/Index.md and related KPR operating docs.