> 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_06_intelligence_action_access.md). # Session 06: Intelligence Action Access **Session ID**: `phase41-session06-intelligence-action-access` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Make typed Ask Hermes and Intelligence portal actions use local all-access readiness instead of legacy disabled defaults. *** ## Scope ### In Scope (MVP) * Update `src/hooks/use-hermes-intelligence-voice.ts`. * Update Intelligence portal components and types. * Remove normal local manual admin setup recovery copy from Ask Hermes, Start Voice, and related Intelligence states. * Preserve provider-key, credential, voice token, broker, demo/privacy, offline, and dependency blockers. * Update portal and voice/intelligence hook tests. ### Out of Scope * Voice token bootstrap internals owned by Session 05. * Hermes mutation controls owned by Session 08. *** ## Prerequisites * [ ] Session 03 Hermes hook readiness is complete. * [ ] Session 05 voice token bootstrap is complete. *** ## Deliverables 1. Intelligence and Ask Hermes flows that can execute under normal local all-access readiness. 2. Clear recovery paths for real voice, provider, token, credential, offline, and demo/privacy failures. 3. Focused tests for local success and each named blocked state. *** ## Success Criteria * [ ] Ask Hermes no longer surfaces manual admin recovery copy in normal local mode. * [ ] Start Voice and typed Intelligence actions show visible results or specific recovery guidance. * [ ] Tests cover successful readiness, token failure, broker failure, and provider-key failure. *** ## 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 06: Intelligence Action Access **Objective**: Make typed Ask Hermes and Intelligence portal actions use local all-access readiness instead of admin-disabled defaults. **Scope**: * Update `src/hooks/use-hermes-intelligence-voice.ts`, `src/components/hermes/intelligence/intelligence-portal.tsx`, and `src/components/hermes/intelligence/intelligence-types.ts`. * Remove normal local `admin-disabled` and manual admin setup recovery copy from Ask Hermes, Start Voice, and related Intelligence states. * Preserve provider-key, browser credential, voice token failure, broker unavailable, demo/privacy, offline, and real dependency blockers. * Update Intelligence portal and voice/intelligence hook tests. **Outputs**: * Intelligence and Ask Hermes UI flows that can execute under normal local all-access readiness. * Clear recovery paths for real voice, provider, token, credential, offline, and demo/privacy failures. * Focused tests for local success and each named blocked state. **Dependencies / Notes**: * Depends on Session 03 for Hermes hook readiness and Session 05 for voice token bootstrap. * Do not claim voice or Intelligence execution unless the route and tests prove real execution or a real recoverable failure. **Acceptance Checks**: * Ask Hermes no longer surfaces admin-disabled recovery copy in normal local mode. * Start Voice and typed Intelligence actions use automatic local readiness and show visible results or specific recovery guidance. * Tests cover successful local action readiness, token failure, broker failure, and provider-key failure. --- # 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_06_intelligence_action_access.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.