> 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_09_documentation_validation_release.md). # Session 09: Documentation Validation Release **Session ID**: `phase25-session09-documentation-validation-release` **Status**: Completed **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Document the final Mission Control contract and certify the full Hermes and Claude Code orchestration surface. *** ## Scope ### In Scope (MVP) * Update `docs/agent-pages.md`, `docs/data-contract.md`, and `docs/api/README_api.md` with final Mission Control endpoints, schema version, commit/set-active behavior, and safe write mechanism. * Update `.spec_system/CONSIDERATIONS.md` with lessons from the phase. * Update `.spec_system/SECURITY-COMPLIANCE.md` for the new write surface and authorized commit/snippet posture. * Run the full validation envelope: tests, typecheck, lint, build, e2e, accessibility checks, demo/live parity, and security review. * Certify all ten Mission Control states: idle, loading, success, empty, error, offline, token-failure, demo, admin-disabled, and admin-ready. ### Out of Scope * New product functionality. * New public source collection. * New local-agent execution paths outside Mission Control. *** ## Prerequisites * [x] Sessions 01 through 08 completed. * [x] All implementation notes and validation evidence available. *** ## Deliverables 1. Updated Mission Control contract and agent-page documentation. 2. Updated considerations and security/compliance posture. 3. End-to-end phase validation record. *** ## Success Criteria * [x] Docs match the shipped Mission Control contracts. * [x] Full suite and focused e2e checks pass or record actionable blockers. * [x] Admin gate and token redaction are verified intact. * [x] Phase binary outcome is YES. *** ## Folded Comparison Detail This section preserves the shared Phase 25 reference context and the complete S25-09 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-09 - Mission Control Documentation & End-to-End Validation / Release **Resolves:** Priority 3.9, Finding #7 (documentation half), Testing Comparison (full envelope), Bottom Line (activation). **Reference (v2.3):** `v2.3/README.md` and `v2.3/CHANGELOG.md` for the original Mission Control product framing and intent to reconcile against the shipped AI OS contract; the endpoint contract comments at `v2.3/src/components/hermes-mission-control.tsx:243-249` and the `v2.3/vite.config.ts` mission handlers (778-1124) as the behavioral baseline the new docs supersede. Note: v2.3 has no contract/API doc or test suite, so the documentation and validation envelope are AI OS-new. **Objective.** Document the final contract and certify the whole surface. **Scope (in).** * Document the final Mission Control contract, endpoints (including `/__hermes_missions/commit` and any set-active path), schema version, and the safe write mechanism in `docs/agent-pages.md`, `docs/data-contract.md`, and `docs/api/README_api.md`. * Carry forward lessons into `.spec_system/CONSIDERATIONS.md` and update `.spec_system/SECURITY-COMPLIANCE.md` for the new write surface. * Full validation pass: complete test suite green; all ten UI states verified; demo/live parity; accessibility; a security review of the new write/commit endpoints and the authorized-snippet mechanism. **Scope (out).** New functionality. **Build steps.** 1. Write/refresh the contract docs and cross-surface references. 2. Run and green the full suite + accessibility + security review. 3. Certify the phase outcome. **Exit criteria.** * Docs describe the activated Mission Control loop accurately and match the shipped contracts. * The full suite passes; the admin gate is verified intact; the phase binary outcome is YES. *** --- # 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_09_documentation_validation_release.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.