> 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-session06-cross-linking-and-copy-consistency-pass/tasks.md).

# Task Checklist

**Session ID**: `phase15-session06-cross-linking-and-copy-consistency-pass` **Total Tasks**: 18 **Estimated Duration**: 3-4 hours **Created**: 2026-06-02

***

## Legend

* `[x]` = Completed
* `[ ]` = Pending
* `[P]` = Parallelizable (can run with other \[P] tasks)
* `[S1506]` = Session reference (15=phase number, 06=session number)
* `TNNN` = Task ID

***

## Progress Summary

| Category       | Total  | Done   | Remaining |
| -------------- | ------ | ------ | --------- |
| Setup          | 2      | 2      | 0         |
| Foundation     | 4      | 4      | 0         |
| Implementation | 9      | 9      | 0         |
| Testing        | 3      | 3      | 0         |
| **Total**      | **18** | **18** | **0**     |

***

## Setup (2 tasks)

Initial configuration and environment preparation.

* [x] T001 \[S1506] Verify Phase 15 Session 06 prerequisites, completed session dependencies, package scripts, and first-release route existence before implementation (`.spec_system/PRD/phase_15/session_06_cross_linking_and_copy_consistency_pass.md`)
* [x] T002 \[S1506] Inventory current public website routes, header/footer labels, page-body CTAs, demo/docs links, legal markers, metadata sources, and active no-claim boundaries with deterministic ordering and explicit missing-route notes (`public-website/src/data/navigation.ts`)

***

## Foundation (4 tasks)

Core structures and base implementations.

* [x] T003 \[S1506] Create built-site route/link/copy checker with deterministic file traversal, approved external destinations, legal-marker checks, guarded-copy checks, and explicit failure messages (`scripts/check-public-website-links.mjs`)
* [x] T004 \[S1506] Extend package validation scripts for the built-site checker without adding production dependencies (`public-website/package.json`)
* [x] T005 \[S1506] \[P] Align shared site route, external destination, proof-point, CTA, and copy guardrail constants with the first-release website contract (`public-website/src/data/site.ts`)
* [x] T006 \[S1506] \[P] Align primary/header and footer navigation data to required IA with Blog and News in primary navigation and Investors, About, Contact, Press, Roadmap, FAQ, Legal, demo, and docs in footer (`public-website/src/data/navigation.ts`)

***

## Implementation (9 tasks)

Main feature implementation.

* [x] T007 \[S1506] Update header rendering for the expanded primary IA with platform-appropriate accessibility labels, visible focus, stable wrapping, and input support (`public-website/src/components/navigation/Header.astro`)
* [x] T008 \[S1506] Update mobile navigation rendering for the expanded primary IA with explicit external labels, visible focus, stable menu reachability, and input support (`public-website/src/components/navigation/MobileNavigation.astro`)
* [x] T009 \[S1506] Update footer rendering for company, trust, resource, legal, demo, and docs link density with explicit external labels, visible focus, and stable responsive wrapping (`public-website/src/components/navigation/Footer.astro`)
* [x] T010 \[S1506] Align homepage proof points, demo/docs CTA language, synthetic-demo labels, static-sample labels, and no-claim copy (`public-website/src/data/homepage.ts`)
* [x] T011 \[S1506] \[P] Align product proof points, surface labels, CTA targets, optional War Room wording, outbound adapter wording, and local-first boundary copy (`public-website/src/data/product.ts`)
* [x] T012 \[S1506] \[P] Align features and how-it-works proof points, pipeline labels, generic event API language, optional output wording, and demo/docs CTAs (`public-website/src/data/features.ts`)
* [x] T013 \[S1506] \[P] Align security and use-case copy for hosted identity, trusted erasure, analytics, War Room optionality, demo separation, and docs/demo CTAs (`public-website/src/data/security.ts`)
* [x] T014 \[S1506] \[P] Align company, contact, press, and investor CTAs, mailto destinations, no-metrics copy, press download boundaries, and external labels (`public-website/src/data/company.ts`)
* [x] T015 \[S1506] Clean roadmap, FAQ, legal, blog, and news cross-links, route references, no-date wording, hosted-options answers, review markers, and launch claims without implying real-user demo data, default prompt/path upload, inbound adapter control, hosted collaboration requirement, revenue, adoption, certification, or production-hosted validation (`public-website/src/data/roadmap.ts`)

***

## Testing (3 tasks)

Verification and quality assurance.

* [x] T016 \[S1506] Run package typecheck and resolve Astro or TypeScript errors from expanded navigation, route constants, data modules, and validation script integration (`public-website/package.json`)
* [x] T017 \[S1506] Run static website build plus the built-site route/link/copy checker, then fix internal dead links, unapproved external destinations, missing legal markers, metadata label drift, and guarded-copy failures (`scripts/check-public-website-links.mjs`)
* [x] T018 \[S1506] Manually smoke desktop and 360px mobile navigation, footer, route discoverability, CTAs, long-label wrapping, legal review markers, external demo/docs/mailto links, ASCII encoding, Unix LF line endings, and no analytics/hosted-form/client-data behavior (`public-website/src/components/navigation/MobileNavigation.astro`)

***

## 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-session06-cross-linking-and-copy-consistency-pass/tasks.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.
