> 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/phase15-session05-roadmap-faq-and-legal-pages/tasks.md). # Task Checklist **Session ID**: `phase15-session05-roadmap-faq-and-legal-pages` **Total Tasks**: 22 **Estimated Duration**: 3-4 hours **Created**: 2026-06-02 *** ## Legend * `[x]` = Completed * `[ ]` = Pending * `[P]` = Parallelizable (can run with other \[P] tasks) * `[S1505]` = Session reference (15=phase number, 05=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 \[S1505] Verify Phase 15 Session 05 prerequisites, completed session dependencies, package scripts, and roadmap/FAQ/legal route absence before implementation (`.spec_system/PRD/phase_15/session_05_roadmap_faq_and_legal_pages.md`) * [x] T002 \[S1505] Review current public website route, metadata, navigation, security, company/contact, FAQ-like, and legal layout patterns before adding new pages (`public-website/src/layouts/LegalLayout.astro`) * [x] T003 \[S1505] Review active security, privacy, hosted-service, roadmap, legal-review, and static-site no-claim boundaries for implementation copy (`.spec_system/SECURITY-COMPLIANCE.md`) *** ## Foundation (5 tasks) Core structures and base implementations. * [x] T004 \[S1505] Extend site route constants and URLs for roadmap, FAQ, legal hub, privacy, terms, and acceptable-use paths with types matching declared contract; exhaustive enum handling (`public-website/src/data/site.ts`) * [x] T005 \[S1505] \[P] Create typed roadmap data for metadata, current focus, near-term themes, later themes, recently shipped links, CTAs, and no-date guardrails with no exact delivery promises (`public-website/src/data/roadmap.ts`) * [x] T006 \[S1505] \[P] Create typed FAQ data for product, setup, privacy/security, demo/docs, integrations, teams, and hosted options with conservative boundary answers and structured-data source fields (`public-website/src/data/faq.ts`) * [x] T007 \[S1505] \[P] Create roadmap timeline component with semantic grouped sections, shipped/news links, deterministic empty states, and platform-appropriate accessibility labels, focus management, and input support (`public-website/src/components/marketing/RoadmapTimeline.astro`) * [x] T008 \[S1505] \[P] Create FAQ list component with categorized answers or native disclosures, no dynamic search, stable responsive wrapping, and platform-appropriate accessibility labels, focus management, and input support (`public-website/src/components/marketing/FaqList.astro`) *** ## Implementation (10 tasks) Main feature implementation. * [x] T009 \[S1505] \[P] Implement `/roadmap` route with BaseLayout, Shell, canonical metadata, roadmap timeline, shipped links, CTAs, and explicit roadmap-change/no-date guardrail (`public-website/src/pages/roadmap.astro`) * [x] T010 \[S1505] \[P] Implement `/faq` route with BaseLayout, Shell, category navigation or grouped FAQ sections, related links, FAQPage structured data, and no dynamic search behavior (`public-website/src/pages/faq.astro`) * [x] T011 \[S1505] \[P] Implement legal hub route with LegalLayout, policy list, policy review statuses, policy scope summaries, and links to privacy, terms, and acceptable-use pages (`public-website/src/pages/legal/index.astro`) * [x] T012 \[S1505] \[P] Implement privacy policy route with LegalLayout, clear pre-review marker, static-site data-collection boundary, no analytics/form/account claims, and no final-approval implication (`public-website/src/pages/legal/privacy.astro`) * [x] T013 \[S1505] \[P] Implement terms route with LegalLayout, clear pre-review marker, non-final terms placeholder or owner-approved copy, and no policy-acceptance workflow claim (`public-website/src/pages/legal/terms.astro`) * [x] T014 \[S1505] \[P] Implement acceptable-use route with LegalLayout, clear pre-review marker, conservative prohibited-use themes, and no hosted account enforcement claim (`public-website/src/pages/legal/acceptable-use.astro`) * [x] T015 \[S1505] Wire roadmap recently shipped entries to existing news or safe news-index links without inventing release claims or exact delivery history (`public-website/src/data/roadmap.ts`) * [x] T016 \[S1505] Wire FAQ answers to existing product, features, how-it-works, security, contact, demo, docs, and legal links with external-link labeling and no hosted identity or analytics overclaim (`public-website/src/data/faq.ts`) * [x] T017 \[S1505] Align footer/resource/legal navigation hrefs and descriptions with route constants while preserving existing product, company, demo, docs, blog, and news links (`public-website/src/data/navigation.ts`) * [x] T018 \[S1505] Review and refine metadata, social descriptions, JSON-LD, review labels, CTAs, and no-overclaim boundary copy across all six routes (`public-website/src/data/site.ts`) *** ## Testing (4 tasks) Verification and quality assurance. * [x] T019 \[S1505] Run package typecheck and resolve Astro or TypeScript errors from route props, data modules, link keys, legal layout props, and structured-data contracts (`public-website/package.json`) * [x] T020 \[S1505] Run static website build and inspect built roadmap, FAQ, and legal HTML for metadata, canonical paths, links, review markers, structured data, and no-date or pre-review boundary copy (`public-website/dist/legal/index.html`) * [x] T021 \[S1505] Manually smoke desktop, tablet, 360px mobile, keyboard focus, FAQ disclosure/category navigation, long-text wrapping, CTA wrapping, legal review markers, footer reachability, and external demo/docs/mailto links (`public-website/src/pages/faq.astro`) * [x] T022 \[S1505] Validate ASCII encoding, Unix LF line endings, no dynamic search/client data collection, and copy guardrails for no hosted identity, trusted erasure, production-hosted validation, certification, broad media readiness, exact roadmap dates, analytics, hosted forms, customer, traction, revenue, market-size, or fundraising claims (`public-website/src/data/roadmap.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 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/phase15-session05-roadmap-faq-and-legal-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.