> 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/implementation_summary.md).

# Implementation Summary

**Session ID**: `phase15-session05-roadmap-faq-and-legal-pages` **Package**: `public-website` **Completed**: 2026-06-02 **Duration**: 1.5 hours

***

## Overview

Built the final planned trust, content, and conversion surfaces for the public website phase: `/roadmap`, `/faq`, and the legal hub plus placeholder policy routes. The session kept the copy conservative, static, and type-driven, with explicit no-date and pre-review guardrails to avoid overclaiming roadmap, privacy, or legal posture.

***

## Deliverables

### Files Created

| File                                                            | Purpose                                                           | Lines |
| --------------------------------------------------------------- | ----------------------------------------------------------------- | ----- |
| `public-website/src/data/roadmap.ts`                            | Typed roadmap copy, grouped themes, shipped links, and guardrails | \~320 |
| `public-website/src/data/faq.ts`                                | Typed FAQ copy, categories, links, and FAQPage source data        | \~360 |
| `public-website/src/components/marketing/RoadmapTimeline.astro` | Static grouped roadmap renderer                                   | \~220 |
| `public-website/src/components/marketing/FaqList.astro`         | Static categorized FAQ renderer with native disclosures           | \~240 |
| `public-website/src/pages/roadmap.astro`                        | Roadmap route entry point and metadata wiring                     | \~240 |
| `public-website/src/pages/faq.astro`                            | FAQ route entry point and structured data wiring                  | \~240 |
| `public-website/src/pages/legal/index.astro`                    | Legal hub and policy index                                        | \~200 |
| `public-website/src/pages/legal/privacy.astro`                  | Privacy placeholder route with review markers                     | \~190 |
| `public-website/src/pages/legal/terms.astro`                    | Terms placeholder route with review markers                       | \~180 |
| `public-website/src/pages/legal/acceptable-use.astro`           | Acceptable-use placeholder route with review markers              | \~180 |

### Files Modified

| File                                    | Changes                                                |
| --------------------------------------- | ------------------------------------------------------ |
| `public-website/src/data/site.ts`       | Added roadmap, FAQ, and legal route constants and URLs |
| `public-website/src/data/navigation.ts` | Aligned footer/resource links with new route constants |
| `public-website/src/data/company.ts`    | Reused shared route constants for blog/news links      |
| `public-website/src/data/security.ts`   | Reused shared route constants for FAQ links and copy   |
| `public-website/package.json`           | Bumped package version from `0.0.14` to `0.0.15`       |

***

## Technical Decisions

1. **Typed data owns the copy**: Roadmap and FAQ content live in data modules so links, categories, and guardrails stay reviewable and type-checked.
2. **Legal pages stay visibly pre-review**: The policy routes use `LegalLayout` and explicit draft language to avoid implying final legal approval.
3. **Static-only presentation**: The routes are Astro-only with no runtime search, analytics, forms, storage, or server-backed behavior.

***

## Test Results

| Metric   | Value                                     |
| -------- | ----------------------------------------- |
| Tests    | 2 package gates plus browser smoke checks |
| Passed   | 2 package gates plus browser smoke checks |
| Coverage | N/A                                       |

***

## Lessons Learned

1. Centralizing route constants reduced stale-link cleanup across navigation, SEO, and content modules.
2. Copy guardrails are easiest to validate when they are embedded in the same typed data that feeds the rendered page.

***

## Future Considerations

Items for future sessions:

1. Complete the phase-wide cross-linking and copy consistency pass.
2. Replace the legal placeholders with owner- or legal-approved copy when it becomes available.

***

## Session Statistics

* **Tasks**: 22 completed
* **Files Created**: 10
* **Files Modified**: 5
* **Tests Added**: 0
* **Blockers**: 0 resolved


---

# 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/implementation_summary.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.