> 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/phase14-session02-battlefield-preview-and-product-mockups/tasks.md). # Task Checklist **Session ID**: `phase14-session02-battlefield-preview-and-product-mockups` **Total Tasks**: 22 **Estimated Duration**: 3-4 hours **Created**: 2026-06-01 *** ## 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 | 4 | 4 | 0 | | **Total** | **22** | **22** | **0** | *** ## Setup (3 tasks) Initial configuration and environment preparation. * [x] T001 \[S1402] Verify public website prerequisites, package commands, and static-site boundary (`public-website/package.json`) * [x] T002 \[S1402] Review existing homepage hero integration and marketing component patterns (`public-website/src/pages/index.astro`) * [x] T003 \[S1402] Confirm marketing component placement for the battlefield preview (`public-website/src/components/marketing`) *** ## Foundation (5 tasks) Core structures and base implementations. * [x] T004 \[S1402] \[P] Extend homepage data types for battlefield agents, missions, traces, and events with simulated-only wording (`public-website/src/data/homepage.ts`) * [x] T005 \[S1402] \[P] Define synthetic mission map, agent token, status ring, route, and coordinate data with no real user, prompt, or local path values (`public-website/src/data/homepage.ts`) * [x] T006 \[S1402] \[P] Define bounded file/tool trace and event stream snippets with deterministic ordering and types matching the declared data contract (`public-website/src/data/homepage.ts`) * [x] T007 \[S1402] Create `BattlefieldPreview.astro` shell using existing Section, Panel, and Badge primitives with semantic region labels (`public-website/src/components/marketing/BattlefieldPreview.astro`) * [x] T008 \[S1402] Add base preview CSS structure with a stable 16:9 desktop frame and bounded content regions (`public-website/src/components/marketing/BattlefieldPreview.astro`) *** ## Implementation (10 tasks) Main feature implementation. * [x] T009 \[S1402] Implement battlefield map grid and mission route rendering with labels that do not rely on color alone (`public-website/src/components/marketing/BattlefieldPreview.astro`) * [x] T010 \[S1402] Render agent tokens and active status rings with text labels, state badges, and non-color-only status treatment (`public-website/src/components/marketing/BattlefieldPreview.astro`) * [x] T011 \[S1402] Implement mission state panel with active objective, progress, and local/static boundary copy without hosted runtime claims (`public-website/src/components/marketing/BattlefieldPreview.astro`) * [x] T012 \[S1402] Implement file/tool trace rail with sanitized labels, bounded list height, and deterministic ordering (`public-website/src/components/marketing/BattlefieldPreview.astro`) * [x] T013 \[S1402] Implement event stream snippets with explicit sample labels and no live telemetry implication (`public-website/src/components/marketing/BattlefieldPreview.astro`) * [x] T014 \[S1402] Add tactical coordinate, grid, and map legend treatment with accessible captions and non-color-only state descriptions (`public-website/src/components/marketing/BattlefieldPreview.astro`) * [x] T015 \[S1402] Add lightweight route, ring, or scan animation with reduced-motion rules that preserve static state labels (`public-website/src/components/marketing/BattlefieldPreview.astro`) * [x] T016 \[S1402] Add responsive desktop and tablet layout that preserves the 16:9 board, readable rails, and no clipping (`public-website/src/components/marketing/BattlefieldPreview.astro`) * [x] T017 \[S1402] Add mobile workpad fallback layout with stacked map, trace, event, and mission summary regions and no horizontal overflow (`public-website/src/components/marketing/BattlefieldPreview.astro`) * [x] T018 \[S1402] Integrate `BattlefieldPreview` immediately after the hero while preserving homepage metadata and hero CTA reachability (`public-website/src/pages/index.astro`) *** ## Testing (4 tasks) Verification and quality assurance. * [x] T019 \[S1402] Run Astro typecheck and fix component, import, or homepage data typing issues (`public-website/package.json`) * [x] T020 \[S1402] Run static website build and fix route, CSS, or homepage rendering issues (`public-website/package.json`) * [x] T021 \[S1402] Manually verify 360px, 768px, 1280px, wide desktop, reduced-motion behavior, and focus behavior if controls exist (`.spec_system/specs/phase14-session02-battlefield-preview-and-product-mockups/implementation-notes.md`) * [x] T022 \[S1402] Validate ASCII encoding and Unix LF line endings for session artifacts and touched website files (`.spec_system/specs/phase14-session02-battlefield-preview-and-product-mockups`) *** ## 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 implement workflow step to begin AI-led implementation. --- # 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/phase14-session02-battlefield-preview-and-product-mockups/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.