> 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-session05-features-and-how-it-works-pages/tasks.md). # Task Checklist **Session ID**: `phase14-session05-features-and-how-it-works-pages` **Total Tasks**: 23 **Estimated Duration**: 3-4 hours **Created**: 2026-06-01 *** ## Legend * `[x]` = Completed * `[ ]` = Pending * `[P]` = Parallelizable (can run with other \[P] tasks) * `[S1405]` = Session reference (14=phase number, 05=session number) * `TNNN` = Task ID *** ## Progress Summary | Category | Total | Done | Remaining | | -------------- | ------ | ------ | --------- | | Setup | 3 | 3 | 0 | | Foundation | 6 | 6 | 0 | | Implementation | 10 | 10 | 0 | | Testing | 4 | 4 | 0 | | **Total** | **23** | **23** | **0** | *** ## Setup (3 tasks) Initial configuration and environment preparation. * [x] T001 \[S1405] Verify public website prerequisites, package scripts, and current route absence for `/features` and `/how-it-works` (`public-website/package.json`) * [x] T002 \[S1405] Review existing product page composition, marketing primitives, and route linking conventions before adding related routes (`public-website/src/pages/product.astro`) * [x] T003 \[S1405] Confirm canonical path, external demo/docs, product, and security link sources for route metadata and CTAs (`public-website/src/data/site.ts`) *** ## Foundation (6 tasks) Core structures and base implementations. * [x] T004 \[S1405] \[P] Define typed page metadata, feature groups, matrix rows, pipeline steps, setup command groups, trust callouts, and CTA data with exhaustive unions (`public-website/src/data/features.ts`) * [x] T005 \[S1405] \[P] Create feature matrix component consuming typed feature rows with workflow-specific copy, bounded cards, and types matching declared contract with exhaustive enum handling (`public-website/src/components/marketing/FeatureMatrix.astro`) * [x] T006 \[S1405] \[P] Create feature band component for grouped capability sections with trust/docs links, mobile-safe wrapping, and platform-appropriate accessibility labels, focus management, and input support (`public-website/src/components/marketing/FeatureBand.astro`) * [x] T007 \[S1405] \[P] Create pipeline diagram component with ordered hook-to-cockpit steps, text summaries, responsive stacking, and no color-only semantics (`public-website/src/components/marketing/PipelineDiagram.astro`) * [x] T008 \[S1405] \[P] Create static terminal window component for example command panels with code semantics, example-only labels, and no execution affordance (`public-website/src/components/marketing/TerminalWindow.astro`) * [x] T009 \[S1405] \[P] Add shared feature-route CTA and trust-boundary data for demo, docs, product, and security handoffs without duplicating URL constants (`public-website/src/data/features.ts`) *** ## Implementation (10 tasks) Main feature implementation. * [x] T010 \[S1405] Implement `/features` route composition with BaseLayout, Shell, canonical metadata, structured data, feature matrix, feature bands, and static-site boundary copy (`public-website/src/pages/features.astro`) * [x] T011 \[S1405] Implement `/how-it-works` route composition with BaseLayout, Shell, canonical metadata, structured data, pipeline diagram, command panels, and docs handoff (`public-website/src/pages/how-it-works.astro`) * [x] T012 \[S1405] Populate the feature matrix with cockpit navigation, live roster, mission feed, battlefield map, mission detail, replay, approvals, timelines, prompt lifecycle, diagnostics, settings, orchestration, lineage, adapters, export, and audit trail (`public-website/src/data/features.ts`) * [x] T013 \[S1405] Add grouped feature band copy tied to operator workflows and route links while avoiding vague marketing, hosted-service, or certification claims (`public-website/src/data/features.ts`) * [x] T014 \[S1405] Add pipeline step data covering Claude Code hooks, Codex CLI hooks, compatible producers, JSON payloads, local `/event`, `apps/server`, WebSocket stream, `apps/web`, optional adapters, and optional War Room (`public-website/src/data/features.ts`) * [x] T015 \[S1405] Add setup command panels for install, dev, and CLI initialization examples with public docs links and visibly non-interactive labeling (`public-website/src/data/features.ts`) * [x] T016 \[S1405] Add trust-boundary callouts and security-route links that preserve no analytics, forms, auth, CMS, hosted identity, hosted storage, public replay hosting, or trusted erasure claims (`public-website/src/data/features.ts`) * [x] T017 \[S1405] Add outbound adapter copy for Discord, Telegram, and generic HTTPS webhooks as outbound notifications only, with no inbound command or remote execution implication (`public-website/src/data/features.ts`) * [x] T018 \[S1405] Add responsive CSS for feature matrix, feature bands, pipeline diagram, and terminal panels with stable dimensions and no text overlap on mobile (`public-website/src/components/marketing/PipelineDiagram.astro`) * [x] T019 \[S1405] Finalize route metadata, social descriptions, internal page links, and external demo/docs link treatment using existing helpers (`public-website/src/pages/how-it-works.astro`) *** ## Testing (4 tasks) Verification and quality assurance. * [x] T020 \[S1405] Run package typecheck and resolve any Astro or TypeScript errors (`public-website/package.json`) * [x] T021 \[S1405] Run static website build and verify built `/features` and `/how-it-works` output includes expected metadata, links, and example-only command labels (`public-website/dist/features/index.html`) * [x] T022 \[S1405] Manually smoke desktop, tablet, 360px mobile, keyboard focus, reduced-motion posture, matrix wrapping, pipeline stacking, and terminal panel readability (`public-website/src/pages/features.astro`) * [x] T023 \[S1405] Validate ASCII encoding, Unix LF line endings, and copy guardrails for no hosted overclaim, outbound-only adapters, static examples, and docs/security handoffs (`public-website/src/data/features.ts`) *** ## 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-session05-features-and-how-it-works-pages/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.