> 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_25/session_07_mission_archive_actions.md). # Session 07: Mission Archive Actions **Session ID**: `phase25-session07-mission-archive-actions` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Make the existing mission list actionable by allowing archived missions to be reactivated or set active through an admin-gated path. *** ## Scope ### In Scope (MVP) * Add an authorized set-active endpoint or reuse the commit path with an existing mission ID. * Validate that the target mission exists before switching active pointers. * Add archive-list actions for "Set active" or "Reactivate". * Require confirmation when replacing a different active mission. * Guard against active switching while another mission write is in flight. * Test pointer integrity and gated rejection paths. ### Out of Scope * Bulk archive operations. * Deleting archived missions. * Changing the on-disk mission file location. *** ## Prerequisites * [ ] Session 01 completed. * [ ] Session 02 completed. * [ ] Active mission and mission list UI available. *** ## Deliverables 1. Admin-gated set-active/reactivate write path. 2. Archive action UI with confirmation and busy guards. 3. Bridge and component tests for pointer integrity. *** ## Success Criteria * [ ] Operators can reactivate archived missions. * [ ] Active mission pointer stays consistent after switching. * [ ] Closed admin gate and malformed target IDs are rejected and tested. * [ ] Archive actions never bypass hook-mediated writes. *** ## Folded Comparison Detail This section preserves the shared Phase 25 reference context and the complete S25-07 session detail from the folded Phase 25 comparison record. This stub is self-contained so the old ongoing-project document can be deleted without losing source anchors, implementation scope, build steps, or exit criteria. ### Source Project Reference Links #### AI OS * [Hermes route](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/src/routes/agents.hermes.tsx) * [Hermes page shell](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/src/components/hermes/hermes-read-only-page.tsx) * [Mission Control UI](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/src/components/hermes/hermes-mission-control.tsx) * [Claude Code mission page](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/src/components/hermes/claude-code-mission-page.tsx) * [Hermes read hook](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/src/hooks/use-hermes.ts) * [Hermes admin hook](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/src/hooks/use-hermes-admin.ts) * [Hermes read contracts](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/src/lib/hermes-types.ts) * [Hermes admin contracts](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/src/lib/hermes-admin-types.ts) * [Hermes read bridge](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/scripts/lib/hermes-dev-bridge.ts) * [Hermes admin bridge](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/scripts/lib/hermes-admin-bridge.ts) * [Hermes demo fixtures](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/src/lib/hermes-demo-data.ts) #### Claude OS v2.3 Reference * [Reference Hermes route](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/src/routes/agents.hermes.tsx) * [Reference Mission Control component](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/src/components/hermes-mission-control.tsx) * [Reference Vite middleware/endpoints](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/vite.config.ts) * [Reference Documents Gallery](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/src/components/hermes-documents-gallery.tsx) * [Reference Mnemosyne component](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/src/components/hermes-mnemosyne.tsx) * [Reference README](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/README.md) * [Reference CHANGELOG](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/CHANGELOG.md) ### Reference Source Map Every session below carries a **Reference (v2.3)** line pointing at the exact reference code to mirror. Citations are relative to the reference root `v2.3/` = `/home/aiwithapex/projects/claudeos/claude-os-v2.3/`. Line numbers are the 2026-06-08 inspection snapshot - treat them as anchors and re-confirm before editing. The two reference files that matter for this plan: * `v2.3/src/components/hermes-mission-control.tsx` - the entire Mission Control UI, planning prompt, per-card copy, briefing renderer, and goal rail. Key anchors: `Actor`/`Status`/`MiniGoal`/`Mission` types (265-286); endpoint contract comments (243-249); `LONG_PROMPT_BODY` (313-509); `buildLongPrompt` (511-523); `MissionControlAgent` (532); `refetch` GET (547-555); exact-decimal progress geometry (561-569); tick/clear fetches (610, 633); `EmptyPanel` + `copy()` + Copy-prompt button (783-944); `MissionBody` (945-1034); `estimateToPips` (1035-1073); `buildCopyText` incl. `/goal` safety net (1074-1128); `formatHumanBrief` + `HUMAN_BRIEF_LABELS` (1130-1196); `BriefingDrawer` (1209-1577); `MissionGoalRail` incl. progress bar + milestone ticks (1583-1987). * `v2.3/vite.config.ts` - the local mission endpoints: GET `/__hermes_missions` (778-799), `optimize` (799-943), `create` (944-1050), `tick` (1051-1099), `clear` (1100-1124); `MISSIONS_FILE` (751). Where a session has no reference, the capability has no v2.3 equivalent and is marked **Reference (v2.3): none - AI OS-new**; the AI OS contracts/bridges named in that session are the substrate to build on. ### Phase Outcome (binary) `/agents/hermes` (and the Claude Code mission route) fully restore the v2.3 Mission Control orchestration loop - planning prompt, discovery-driven decomposition, multi-goal authoring, optimized preview -> commit, per-goal `/goal` and human-briefing copy, and archive management - on top of the AI OS typed-contract, admin-gated, tested architecture, with documentation and end-to-end validation. YES/NO at the end of the last session. ### Cross-Cutting Guardrails (every session must hold these) These are the AI OS strengths the plan must preserve while adding v2.3 affordances. No session may regress them: 1. Admin-gate is never weakened. All writes keep requiring loopback + valid per-run `X-Claude-OS-Token` + `HERMES_DASHBOARD_ADMIN=1` + non-demo + hook-mediated path. 2. Typed contracts stay authoritative. New fields/endpoints get read/admin parsers that reject malformed payloads; no ad hoc JSON. 3. State machine stays explicit. idle / loading / success / empty / error / offline / token-failure / demo / admin-disabled / admin-ready all keep rendering and stay tested. 4. Errors stay bounded and redacted through the existing display helpers. 5. Reads use query invalidation, not polling or fetch bypasses. 6. Demo/live parity holds; demo mode never triggers a real write. 7. Both agent presentations (`hermes`, `claude-code`) stay at parity at the contract layer; differences remain presentation copy only. 8. Every new affordance ships with unit/component coverage in the same session; responsive/e2e coverage lands by S25-08. ### S25-07 - Mission Archive Actions & Multi-Mission Management **Resolves:** Priority 3.7, Suggested Target UX item 5, Mission Data Contract (archive list). **Reference (v2.3): none - AI OS-new.** v2.3 tracks a single active mission only: `create` (`v2.3/vite.config.ts:944-1050`) replaces whatever was active and `clear` (`:1100-1124`) drops it; there is no archive, list, or reactivate path, and the component never renders inactive missions. The substrate for this session is the AI OS-side mission list already produced by the read bridge (`scripts/lib/hermes-dev-bridge.ts` envelope `missions[]`) and the commit/active-pointer path from S25-01. **Objective.** Make the existing mission list actionable so old missions can be reactivated or set active. **Scope (in).** * Archive list actions: "Set active" / "Reactivate" persisting through an admin-gated write (reusing/extending the S25-01 commit/active path); ensure active-pointer integrity when switching. * Guard against switching while a write is in flight; explicit confirmation when replacing a different active mission. **Scope (out).** Bulk operations beyond set-active/reactivate. **Build steps.** 1. Add an authorized set-active endpoint or reuse commit with an existing-ID path; validate the target exists. 2. Wire archive-list actions + confirmation + busy guards. 3. Test pointer integrity and rejection under a closed admin gate. **Exit criteria.** * An operator can reactivate any archived mission; the active pointer stays consistent and tested. * Component + bridge tests cover set-active, pointer mismatch, and gated rejection. *** --- # 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_25/session_07_mission_archive_actions.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.