> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/prd/phase_41/session_08_hermes_mutation_controls.md). # Session 08: Hermes Mutation Controls **Session ID**: `phase41-session08-hermes-mutation-controls` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Make Hermes chat, mission, document, Pantheon, Ministry, and Obsidian mutation controls execute or show real blockers under the all-access contract. *** ## Scope ### In Scope (MVP) * Update Hermes chat command actions, types, message list, composer, and chat tab gating. * Update admin panel, Mission Control, Documents Gallery, Pantheon, Ministry save/copy shell, and Obsidian bridge behavior. * Update demo fixtures so they do not teach manual local admin setup as the product model. * Implement real mutation execution paths with visible results for every retained shipped Hermes mutation control. * Update focused component, route, and e2e tests. ### Out of Scope * OpenClaw and Claude Code execution surfaces owned by Sessions 09 and 10. *** ## Prerequisites * [ ] Session 03 Hermes readiness is complete. * [ ] Session 06 Intelligence action access is complete. *** ## Deliverables 1. Hermes mutation surfaces that are write-ready by default in local dev. 2. Specific blocked states and recovery paths for real token, demo/privacy, offline, provider, credential, and dependency failures. 3. Tests proving real execution, visible results, failed-action handling, and no manual admin env requirement. *** ## Success Criteria * [ ] Chat, mission, document, Pantheon, Ministry, and Obsidian controls do not ask for manual admin env setup in normal local dev. * [ ] Mutations execute end to end with visible success or failed-action recovery output. * [ ] Component and e2e tests assert all-access readiness and named recovery. *** ## Folded Handoff Session Details The following session-specific details were migrated from the former ongoing-projects handoff. They preserve the original objective, scope, outputs, dependencies, notes, and acceptance checks for this session. #### Session 08: Hermes Mutation Controls **Objective**: Make Hermes chat, mission, document, Pantheon, Ministry, and Obsidian mutation controls execute or show real blockers under the all-access contract. **Scope**: * Update `src/components/hermes/chat/command-actions.ts`, `chat-types.ts`, `chat-message-list.tsx`, `chat-composer.tsx`, and `hermes-chat-tab.tsx` so command and slash-action gating reflects real token, demo/privacy, offline, credential, or dependency failures only. * Update `src/components/hermes/hermes-admin-panel.tsx`, `hermes-mission-control.tsx`, `hermes-documents-gallery.tsx`, `hermes-pantheon.tsx`, `ministry/ministry-save-copy-shell.tsx`, and `hermes-obsidian-bridge.tsx`. * Update `src/lib/hermes-demo-data.ts` so fixtures do not teach read-only routing or manual admin setup as the local product model. * Implement real mutation execution paths with visible results for every shipped Hermes mutation control. * Update focused component, route, and e2e tests for chat, Mission Control, Documents, Pantheon, Ministry, Obsidian, and demo fixture states. **Outputs**: * Hermes mutation surfaces that are write-ready by default in local dev. * Specific blocked states and recovery paths for real token, demo/privacy, offline, provider, credential, and dependency failures. * Tests proving real mutation execution, visible results, failed-action handling, and no manual admin env requirement. **Dependencies / Notes**: * Depends on Sessions 03 and 06 because chat, voice, and Intelligence share access and token state. * Demo surfaces must never replace shipped local execution; they may only identify a hosted-demo/privacy boundary and point back to executable local mode. **Acceptance Checks**: * Chat, mission, document, Pantheon, Ministry, and Obsidian write controls do not ask the operator to set `HERMES_DASHBOARD_ADMIN=1` in normal local dev. * Mutations execute end to end with visible success output, failed-action details, recovery paths, and tests. * Component and e2e tests assert all-access readiness, visible success results, and named recovery paths. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/prd/phase_41/session_08_hermes_mutation_controls.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.