> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/.spec_system/specs/phase24-session09-validation-and-documentation/tasks.md). # Task Checklist **Session ID**: `phase24-session09-validation-and-documentation` **Total Tasks**: 20 **Estimated Duration**: 3-4 hours **Created**: 2026-07-08 *** Legend: `[x]` completed; `[ ]` pending; `[P]` parallelizable; `[SNNMM]` session ref; `TNNN` task ID. *** ## Setup (3 tasks) * [x] T001 \[S2409] Verify analyzer state, active Session 09 package context, and Phase 24 dependency completion (`.spec_system/PRD/phase_24/session_09_validation_and_documentation.md`) * [x] T002 \[S2409] \[P] Inspect Session 06-08 validation, security, implementation, and generated-asset handoff artifacts (`.spec_system/specs/phase24-session08-generated-asset-implementation-handoff/validation.md`) * [x] T003 \[S2409] \[P] Inspect focused Phase 24 validation anchors and stale docs requiring reconciliation (`apps/web/tests/CombatPlaybackLayer.test.tsx`, `docs/game-design/15-phases-yet-to-be-implemented.md`) *** ## Verification (6 tasks) * [x] T004 \[S2409] Run focused Phase 24 web tests for combat playback, live tier, scrying, world cues, honesty, generated assets, Battlefield, and Quest Board evidence with explicit loading, empty, error, and reduced-motion states (`npm test -- apps/web/tests/combatPlayback.test.ts apps/web/tests/combatPlaybackEffects.test.ts apps/web/tests/CombatPlaybackLayer.test.tsx apps/web/tests/liveLegion.test.ts apps/web/tests/LiveLegionLayer.test.tsx apps/web/tests/scryingAndAlertFocus.test.ts apps/web/tests/ScryingAndAlertFocusLayer.test.tsx apps/web/tests/worldCues.test.ts apps/web/tests/useWorldCues.test.tsx apps/web/tests/gameProjection.test.ts apps/web/tests/gameProjectionStore.test.ts apps/web/tests/generatedPhase3Assets.test.ts apps/web/tests/mediaCatalog.test.ts apps/web/tests/Battlefield.test.tsx apps/web/tests/BattlefieldInteraction.test.tsx apps/web/tests/questBoardActions.test.ts apps/web/tests/QuestBoard.test.tsx`) * [x] T005 \[S2409] \[P] Run web package typecheck and capture exact output (`npm --workspace @factionos/web run typecheck`) * [x] T006 \[S2409] \[P] Run root formatting check and capture exact output (`npm run format:check`) * [x] T007 \[S2409] \[P] Verify generated Phase 3 asset paths, app catalog records, typed fallbacks, and no direct runtime generated-path loading (`assets/generated/game-design/phase03/live-enemies/live-enemy-effects-sheet.png`, `apps/web/src/lib/generatedPhase3Assets.ts`) * [x] T008 \[S2409] Triage any validation failure and apply only narrow in-scope Phase 24 closeout fixes with matching tests (`apps/web/src`, `apps/web/tests`) * [x] T009 \[S2409] Run broader tests only if fixes touch shared store, Quest Board, or battlefield behavior outside focused files (`npm test`) *** ## Audit (4 tasks) * [x] T010 \[S2409] Create the Phase 24 phase-exit evidence matrix for all eight section 13A criteria (`.spec_system/specs/phase24-session09-validation-and-documentation/phase-exit-audit.md`) * [x] T011 \[S2409] Audit Fun Law 1 inspect-through and Fun Law 4 no-rewarded-waste boundaries for live tier and combat playback (`.spec_system/specs/phase24-session09-validation-and-documentation/phase-exit-audit.md`) * [x] T012 \[S2409] Audit replay, reconnect, mock, storage, privacy, protocol, server-route, hosted, reward, and trusted-erasure boundaries (`.spec_system/specs/phase24-session09-validation-and-documentation/phase-exit-audit.md`) * [x] T013 \[S2409] Record generated Phase 3 asset implementation evidence, fallback labels, reduced-motion pairings, and media posture (`.spec_system/specs/phase24-session09-validation-and-documentation/phase-exit-audit.md`) *** ## Documentation (5 tasks) * [x] T014 \[S2409] Update web, battlefield, and media docs after validation evidence exists with product-facing copy only and no generated-path runtime overclaim (`apps/web/README_web.md`, `docs/battlefield.md`, `docs/media-assets.md`) * [x] T015 \[S2409] Update privacy and architecture docs for aggregate-only projection data, replay/mock persistence guards, typed asset posture, and no-claim boundaries (`docs/privacy-and-security.md`, `docs/ARCHITECTURE.md`) * [x] T016 \[S2409] Update game-design implemented and pending ledgers so game-design Phase 3 moves only after evidence is recorded (`docs/game-design/14-implemented-phases.md`, `docs/game-design/15-phases-yet-to-be-implemented.md`) * [x] T017 \[S2409] Update game-design change log, master PRD, and Phase 24 PRD with evidence-backed closeout wording without replacing `validate` or `updateprd` bookkeeping (`docs/game-design/11-open-questions-and-change-log.md`, `.spec_system/PRD/PRD.md`, `.spec_system/PRD/phase_24/PRD_phase_24.md`) * [x] T018 \[S2409] Run spec-system analyzer and git visibility checks after documentation changes to record current workflow state and changed-file surface (`.spec_system/state.json`) *** ## Completion (2 tasks) * [x] T019 \[S2409] Record implementation notes, command evidence, docs changes, validation repair decisions, and residual no-claim boundaries (`.spec_system/specs/phase24-session09-validation-and-documentation/implementation-notes.md`) * [x] T020 \[S2409] Run ASCII/LF and whitespace validation for session artifacts and changed docs (`.spec_system/specs/phase24-session09-validation-and-documentation`) *** ## Completion Checklist * [x] All tasks marked `[x]` * [x] All tests and checks passing * [x] All files ASCII-encoded with LF line endings * [x] implementation-notes.md updated * [x] Ready for `creview` (next step in the implement -> creview -> validate sequence) *** ## Next Steps Run the `creview` workflow step. --- # 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://faction-os.gitbook.io/faction-os-docs/.spec_system/specs/phase24-session09-validation-and-documentation/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.