> 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/phases/phase_15/session_05_roadmap_faq_and_legal_pages.md).

# Session 05: Roadmap, FAQ, And Legal Pages

**Session ID**: `phase15-session05-roadmap-faq-and-legal-pages` **Package**: public-website **Status**: Not Started **Estimated Tasks**: \~18-24 **Estimated Duration**: 2-4 hours

***

## Objective

Build roadmap, FAQ, and legal/policy pages with clear review boundaries and no unsupported delivery, legal, or hosted-service claims.

***

## Scope

### In Scope (MVP)

* Create or complete `src/pages/roadmap.astro`.
* Create or complete `src/pages/faq.astro`.
* Create or complete `src/pages/legal/index.astro`.
* Create or complete `src/pages/legal/privacy.astro`.
* Create or complete `src/pages/legal/terms.astro`.
* Create or complete `src/pages/legal/acceptable-use.astro`.
* Add `src/data/roadmap.ts`.
* Add `src/data/faq.ts`.
* Build `RoadmapTimeline.astro` and `FaqList.astro` if not already present.
* Add owner/legal review markers where content is not approved as final.
* Add metadata and internal links.

### Out of Scope

* Binding roadmap to exact dates.
* Formal legal review completion unless the owner provides approved text.
* Privacy policy claiming data collection not implemented by the website.
* Dynamic FAQ search.

***

## Prerequisites

* [ ] Phase 15 security boundaries reviewed.
* [ ] Contact destinations from Session 04 available.

***

## Deliverables

1. `/roadmap` route.
2. `/faq` route.
3. `/legal` index route.
4. `/legal/privacy` route.
5. `/legal/terms` route.
6. `/legal/acceptable-use` route.
7. Roadmap and FAQ data modules.
8. Review markers where legal/policy copy is not final.

***

## Page Content Requirements

Roadmap:

* Current focus.
* Near-term themes.
* Later themes.
* Recently shipped, linked to `/news`.
* Guardrail note that roadmap items may change.
* No exact delivery dates unless owner-approved.

FAQ categories:

* Product.
* Setup.
* Privacy and security.
* Demo and docs.
* Integrations.
* Teams and hosted options.

Legal pages:

* `/legal`: policy list and review status.
* `/legal/privacy`: privacy policy content or clear pre-review placeholder.
* `/legal/terms`: terms page or clear pre-review placeholder.
* `/legal/acceptable-use`: acceptable-use policy or clear pre-review placeholder.

Legal content must not look final unless reviewed.

***

## Task Expansion Guidance

When expanded with `plansession`, keep the checklist to 18-24 tasks covering:

* Roadmap data.
* Roadmap route.
* Roadmap component.
* FAQ data.
* FAQ route.
* FAQ component.
* Legal layout use.
* Legal index.
* Privacy page.
* Terms page.
* Acceptable-use page.
* Review markers.
* Metadata.
* Cross-links.
* Build/typecheck.

***

## Success Criteria

* [ ] Roadmap, FAQ, and legal routes render.
* [ ] Roadmap avoids exact delivery promises.
* [ ] FAQ covers product, setup, privacy/security, demo/docs, integrations, teams, and hosted options.
* [ ] Legal/policy pages are owner-reviewed or clearly marked as pre-review.
* [ ] No legal page introduces unsupported data-collection or hosted-service claims.


---

# 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/phases/phase_15/session_05_roadmap_faq_and_legal_pages.md?ask=<question>&goal=<endgoal>
```

`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.