> 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/archive/phases/phase_16/session_01_guardrails_architecture_parity_baseline.md). # Session 01: Guardrails, Architecture Decision And Parity Baseline **Session ID**: `phase16-session01-guardrails-architecture-parity-baseline` **Status**: Not Started **Estimated Tasks**: \~12-16 **Estimated Duration**: 2-3 hours *** ## Objective Confirm and record the porting architecture decision (port v2.3 features into aios modules, not the monolith), settle the information architecture for the expanded page (tabs vs. scroll), and snapshot the current Hermes test suite as the parity baseline before any new code lands. Source-code anchors are the existing `AIOS/` Hermes modules plus the v2.3 route/component inventory listed in the Phase 16 PRD. *** ## Scope ### In Scope (MVP) * Record the architecture decision: ports into aios-style modules under `AIOS/src/components/hermes/`, routed through aios hooks/types/demo-data, every write forced through the admin-token + loopback gate. Feature parity, not file parity. (Source: Core Decision in the Phase 16 PRD.) * Resolve **Open Question 1 (IA)**: new top-level tabs vs. nested sub-tabs vs. long-scroll for the \~12 added surfaces. Recommendation: keep the Tabs shell and add new tabs `Chat`, `Mission`, `Documents`, `Mnemosyne`, `Connections` rather than one long scroll. The new tabs are added to `AIOS/src/components/hermes/hermes-read-only-page.tsx` (TabsList `:150`, TabsContent blocks `:177-189`). * Snapshot `AIOS/src/components/hermes/__tests__/hermes-sections.test.tsx` (and the other current Hermes tests `hermes-admin-types.test.ts`, live-data validation) as the parity baseline; document the current 5-tab read-only surface (`Sessions` / `Memory` / `Pantheon` / `Skills` / `Admin`). * Index and confirm the two extracted bridge modules are the extension points: `AIOS/scripts/lib/hermes-dev-bridge.ts` (970 lines, register fn `:964`) and `AIOS/scripts/lib/hermes-admin-bridge.ts` (937 lines, register fn `:926`), wired from `AIOS/vite.config.ts:11-12`. * Confirm the v2.3 component inventory (full list in the Phase 16 PRD) maps to the planned tabs and sessions. ### Out of Scope * Any new endpoint, hook, type, or component implementation (Sessions 02-03 and Phases 17-20). * Any visual/shell change (Phase 17 Session 01). *** ## Prerequisites * [ ] Phase 15 is complete. * [ ] Source repos available: `V23/` = `/home/aiwithapex/projects/claudeos/claude-os-v2.3/`; diff at `/home/aiwithapex/projects/claudeos/diff-v1-v2.3/`. * [ ] The Phase 16 PRD master reference (this directory) is the source of truth for the legend, decision, inventory, and contracts. *** ## Deliverables 1. A recorded architecture decision and IA decision (tabs shell + new tabs `Chat`, `Mission`, `Documents`, `Mnemosyne`, `Connections`), captured in the spec/decision artifact for the session. 2. A parity baseline: snapshot/record of current Hermes tests and the current 5-tab read-only surface to diff against during the port. 3. A confirmed extension-point map (dev-bridge `:964`, admin-bridge `:926`, hooks, types, demo-data) and v2.3 component-to-tab mapping. *** ## Success Criteria * [ ] The architecture decision (modules, not monolith; feature parity) is written down and references the Core Decision section. * [ ] The IA is decided and recorded with the target tab list and the `hermes-read-only-page.tsx` insertion points (TabsList `:150`, TabsContent `:177-189`). * [ ] The current Hermes test suite and read-only surface are snapshotted as the parity baseline. * [ ] No production code changed; the page still renders the current 5 tabs. --- # 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/archive/phases/phase_16/session_01_guardrails_architecture_parity_baseline.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.