> 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/sessions/phase18-session01-memory-upgrade-write/tasks.md). # Task Checklist **Session ID**: `phase18-session01-memory-upgrade-write` **Total Tasks**: 21 **Estimated Duration**: 3-4 hours **Created**: 2026-06-02 *** ## Legend * `[x]` = Completed * `[ ]` = Pending * `[P]` = Parallelizable (can run with other \[P] tasks) * `[SNNMM]` = Session reference (NN=phase number, MM=session number) * `TNNN` = Task ID *** ## Progress Summary | Category | Total | Done | Remaining | | -------------- | ------ | ------ | --------- | | Setup | 3 | 3 | 0 | | Foundation | 5 | 5 | 0 | | Implementation | 10 | 10 | 0 | | Testing | 3 | 3 | 0 | | **Total** | **21** | **21** | **0** | *** ## Setup (3 tasks) Initial confirmation and implementation notes. * [x] T001 \[S1801] Resolve upstream Memory anchors and document the Obsidian write-safety assumptions (`.spec_system/specs/phase18-session01-memory-upgrade-write/implementation-notes.md`) * [x] T002 \[S1801] Verify existing memory, sessions, profiles, and Obsidian admin contracts for reuse (`src/hooks/use-hermes.ts`) * [x] T003 \[S1801] Map current Memory card gaps against the v2.3 Memory section before editing (`src/components/hermes/hermes-memory-card.tsx`) *** ## Foundation (5 tasks) Core props, helpers, fixtures, and formatting. * [x] T004 \[S1801] Extend Memory card props for memory, sessions, profiles, and admin actions with exhaustive disabled-state derivation (`src/components/hermes/hermes-memory-card.tsx`) * [x] T005 \[S1801] Define memory layer helpers for metadata, section splitting, SOUL cleanup, char-budget percentage, and bounded path/status copy (`src/components/hermes/hermes-memory-card.tsx`) * [x] T006 \[S1801] Define Obsidian bridge helpers for vault path persistence, confirmation gating, sanitized result formatting, and state reset on vault changes (`src/components/hermes/hermes-memory-card.tsx`) * [x] T007 \[S1801] \[P] Extend Hermes demo profile fixtures for profile grid parity (`src/lib/hermes-demo-data.ts`) * [x] T008 \[S1801] \[P] Add memory, profile, admin, and Obsidian mutation-state fixtures for component tests (`src/components/hermes/__tests__/hermes-sections.test.tsx`) *** ## Implementation (10 tasks) Main Memory upgrade. * [x] T009 \[S1801] Wire `HermesReadOnlyPage` to pass `sessions`, `profiles`, and `admin` into Memory while preserving demo/live tab transitions (`src/components/hermes/hermes-read-only-page.tsx`) * [x] T010 \[S1801] Upgrade the Memory tab layout to render three manuscript layers with explicit loading, empty, error, offline, token-failure, success, and demo states (`src/components/hermes/hermes-memory-card.tsx`) * [x] T011 \[S1801] Implement character-count ring and bounded section rendering for USER and MEMORY with explicit empty handling (`src/components/hermes/hermes-memory-card.tsx`) * [x] T012 \[S1801] Implement SOUL prose rendering with template/frontmatter cleanup and no character-budget ring (`src/components/hermes/hermes-memory-card.tsx`) * [x] T013 \[S1801] Add conversation-history callout from the sessions view with explicit loading, empty, error, offline, and token-failure states (`src/components/hermes/hermes-memory-card.tsx`) * [x] T014 \[S1801] Add token-gated profile memory grid with active/model/gateway fallbacks and no raw private content exposure (`src/components/hermes/hermes-memory-card.tsx`) * [x] T015 \[S1801] Add Obsidian bridge controls for vault path, confirmation checkbox, admin-disabled hints, and duplicate-trigger prevention while in-flight (`src/components/hermes/hermes-memory-card.tsx`) * [x] T016 \[S1801] Render Obsidian pending, success, error, and disconnected states with sanitized local path display and state reset on disconnect/reopen (`src/components/hermes/hermes-memory-card.tsx`) * [x] T017 \[S1801] Preserve sensitive-read and admin-write gating across demo mode, live mode, token failure, and offline transitions (`src/components/hermes/hermes-read-only-page.tsx`) * [x] T018 \[S1801] Add platform-appropriate accessibility labels, focus behavior, and keyboard support for Memory layers, profile grid, and Obsidian controls (`src/components/hermes/hermes-memory-card.tsx`) *** ## Testing (3 tasks) Verification and quality assurance. * [x] T019 \[S1801] Extend component tests for memory layers, conversation states, profile grid, Obsidian disabled/confirm/pending/success/error states, and state reset behavior (`src/components/hermes/__tests__/hermes-sections.test.tsx`) * [x] T020 \[S1801] Add or confirm admin hook tests for Obsidian confirmation payload and duplicate-trigger prevention (`src/hooks/__tests__/use-hermes-admin.test.tsx`) * [x] T021 \[S1801] Run focused Hermes tests, typecheck, lint, and ASCII validation; record results and any unrelated failures (`.spec_system/specs/phase18-session01-memory-upgrade-write/implementation-notes.md`) *** ## Completion Checklist Before marking session complete: * [x] All tasks marked `[x]` * [x] All tests passing * [x] All files ASCII-encoded * [x] `implementation-notes.md` updated * [x] Ready for the validate workflow step *** ## Next Steps Run the `validate` workflow step to verify session completeness. --- # 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/sessions/phase18-session01-memory-upgrade-write/tasks.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.