> 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/archive/sessions/phase02-session01-product-surface-requirements-reconciliation/tasks.md). # Task Checklist **Session ID**: `phase02-session01-product-surface-requirements-reconciliation` **Total Tasks**: 18 **Estimated Duration**: 3-4 hours **Created**: 2026-05-29 *** ## 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 | 4 | 4 | 0 | | Implementation | 7 | 7 | 0 | | Testing | 4 | 4 | 0 | | **Total** | **18** | **18** | **0** | *** ## Setup (3 tasks) Initial documentation context and verification planning. * [x] T001 \[S0201] Verify Phase 01 completion, Phase 2 stubs, and current spec workflow state before requirements edits (`.spec_system/specs/phase02-session01-product-surface-requirements-reconciliation/implementation-notes.md`) * [x] T002 \[S0201] Map authoritative stable docs, README entry points, and symlinked PRD/UX targets for the product-surface audit (`.spec_system/specs/phase02-session01-product-surface-requirements-reconciliation/implementation-notes.md`) * [x] T003 \[S0201] Record current web cockpit source inventory, focused test coverage, battlefield docs, and public demo boundaries (`.spec_system/specs/phase02-session01-product-surface-requirements-reconciliation/implementation-notes.md`) *** ## Foundation (4 tasks) Requirements structure, taxonomy, and historical-source boundaries. * [x] T004 \[S0201] \[P] Draft product requirement structure and shipped/planned/deferred/excluded status taxonomy (`.spec_system/PRD/PRD.md`) * [x] T005 \[S0201] \[P] Draft UX requirement structure for interaction, visual, motion, responsive, and accessibility requirements (`.spec_system/PRD/PRD_UX.md`) * [x] T006 \[S0201] Define product-surface gap matrix schema with source, current state, requirement, acceptance, owner, and deferral columns (`.spec_system/PRD/phase_02/product_surface_gap_matrix.md`) * [x] T007 \[S0201] Map historical-source, `EXAMPLES/`, and asset-quarantine rules into product-surface requirements boundaries (`docs/legacy-consolidation.md`) *** ## Implementation (7 tasks) Expanded requirements, gap matrix content, and stable entry points. * [x] T008 \[S0201] Expand product PRD with current shipped surface, Phase 02 objectives, local-first policy, and explicit exclusions (`.spec_system/PRD/PRD.md`) * [x] T009 \[S0201] Expand UX PRD with cockpit, battlefield, overlay, settings, replay, notification, scan UX, public demo, accessibility, and reduced-motion requirements (`.spec_system/PRD/PRD_UX.md`) * [x] T010 \[S0201] Populate gap matrix for cockpit shell, navigation, global commands, hero roster, mission workflow, overlays, permission context, and plan context (`.spec_system/PRD/phase_02/product_surface_gap_matrix.md`) * [x] T011 \[S0201] Populate gap matrix for battlefield, asset parity, public demo, settings, replay, export, notifications, and scan-root UX (`.spec_system/PRD/phase_02/product_surface_gap_matrix.md`) * [x] T012 \[S0201] Update Phase 02 PRD with gap matrix reference, Session 01 output contract, and exclusions that feed Sessions 02-07 (`.spec_system/PRD/phase_02/PRD_phase_02.md`) * [x] T013 \[S0201] \[P] Update docs index references for expanded PRD/UX requirements and evidence-only historical routing (`docs/README_docs.md`) * [x] T014 \[S0201] \[P] Update root README planning references or boundary wording if expanded requirements change public entry points (`README.md`) *** ## Testing (4 tasks) Documentation verification and readiness closeout. * [x] T015 \[S0201] Run stale-claim and historical-source grep checks and record results (`.spec_system/specs/phase02-session01-product-surface-requirements-reconciliation/implementation-notes.md`) * [x] T016 \[S0201] Run markdown path and symlink spot checks for PRD, UX PRD, gap matrix, docs index, README, and legacy-consolidation references (`.spec_system/specs/phase02-session01-product-surface-requirements-reconciliation/implementation-notes.md`) * [x] T017 \[S0201] Run ASCII, LF, and `git diff --check` verification for touched docs (`.spec_system/specs/phase02-session01-product-surface-requirements-reconciliation/implementation-notes.md`) * [x] T018 \[S0201] Review Session 02 readiness and record any remaining requirement gaps or blockers (`.spec_system/specs/phase02-session01-product-surface-requirements-reconciliation/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://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase02-session01-product-surface-requirements-reconciliation/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.