> 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/public-website/docs/archive-docs_public-website/documentation-audit.md).

# Documentation Audit

Audit date: 2026-06-02

Scope: `public-website/` standalone documentation, with `.spec_system` treated as removable.

## Audit Mode

Full public-website documentation audit.

Reason: the website was built through archived phase/session records, and the requested outcome is that deleting `.spec_system` should not remove necessary website documentation.

## Coverage Summary

| Area                                       | Status   | Stable document                               |
| ------------------------------------------ | -------- | --------------------------------------------- |
| Docs index and source map                  | complete | `README_docs_public-website.md`               |
| Build history and completed phases         | complete | `build-site-plan.md`                          |
| Architecture                               | complete | `architecture.md`                             |
| Local development                          | complete | `development.md`                              |
| Routes and information architecture        | complete | `routes-and-information-architecture.md`      |
| UX and visual system                       | complete | `website_ux.md`                               |
| Content authoring                          | complete | `content-authoring.md`                        |
| SEO and metadata                           | complete | `seo-and-metadata.md`                         |
| Media provenance and press policy          | complete | `media-assets.md`                             |
| Security, privacy, and claim boundaries    | complete | `security-privacy-and-claim-boundaries.md`    |
| Accessibility, responsive, and performance | complete | `accessibility-responsive-and-performance.md` |
| Deployment                                 | complete | `deployment.md`                               |
| Launch readiness evidence                  | complete | `launch-readiness.md`                         |
| Post-launch backlog                        | complete | `post-launch-backlog.md`                      |
| Validation commands and QA checklist       | complete | `validation.md`                               |

## Spec-System Records Promoted

The following information is now represented in stable docs:

* Phase 13-16 objectives, sessions, outcomes, and technical decisions.
* Astro static architecture and package dependency decisions.
* Route map and current 31-route build count.
* Blog/news schemas, generated routes, draft behavior, RSS behavior.
* SEO metadata, canonical URL, social card, manifest, robots, sitemap, and JSON-LD ownership.
* Media inventory, SHA-256 hashes, release statuses, pass-through press policy, and blocked media rules.
* Static privacy boundary and no-claim language.
* Accessibility, responsive, reduced-motion, image, and performance evidence.
* Cloudflare Pages workflow, credential-safe deploy skipping, manual fallback, and bounded smoke rules.
* Launch gate evidence from 2026-06-02.
* Production deploy, legal approval, accessibility certification, analytics, search, CMS, forms, and server rendering backlog items.

## Remaining Human-Input Gaps

These gaps are intentionally documented as pending/no-claim, not missing docs:

| Gap                                     | Status      | Where documented                                                        |
| --------------------------------------- | ----------- | ----------------------------------------------------------------------- |
| Authorized Cloudflare Pages deploy      | no-claim    | `deployment.md`, `launch-readiness.md`, `post-launch-backlog.md`        |
| Production HTTPS homepage smoke         | no-claim    | `deployment.md`, `launch-readiness.md`, `post-launch-backlog.md`        |
| Cloudflare dashboard/domain evidence    | unavailable | `launch-readiness.md`, `post-launch-backlog.md`                         |
| Formal legal/privacy owner approval     | pending     | `security-privacy-and-claim-boundaries.md`, `launch-readiness.md`       |
| Formal accessibility/VPAT certification | no-claim    | `accessibility-responsive-and-performance.md`, `post-launch-backlog.md` |
| Physical mobile-device QA               | no-claim    | `accessibility-responsive-and-performance.md`, `post-launch-backlog.md` |

## Docs That Must Stay Current

When code changes, update these docs in the same pull:

| Change type                            | Docs to update                                                                                              |
| -------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| New fixed route                        | `routes-and-information-architecture.md`, `development.md`, `validation.md`                                 |
| New blog/news schema or route behavior | `content-authoring.md`, `seo-and-metadata.md`, `validation.md`                                              |
| New external destination               | `routes-and-information-architecture.md`, `security-privacy-and-claim-boundaries.md`, `validation.md`       |
| Media addition or press download       | `media-assets.md`, `website_ux.md`, `accessibility-responsive-and-performance.md`                           |
| Metadata behavior change               | `seo-and-metadata.md`, `validation.md`                                                                      |
| Runtime collection or client behavior  | `security-privacy-and-claim-boundaries.md`, `development.md`, `validation.md`                               |
| Deployment workflow change             | `deployment.md`, `launch-readiness.md`, `post-launch-backlog.md`                                            |
| Legal approval status change           | `security-privacy-and-claim-boundaries.md`, `launch-readiness.md`, `routes-and-information-architecture.md` |

## Deletion Readiness

For public-website purposes, the required documentation from phases 13-16 has been moved into `public-website/docs_public-website/`.

Deleting `.spec_system` would still remove historical workflow evidence for the whole repository, but it should not remove required operating, architecture, development, deployment, content, media, validation, or launch-handoff documentation for `public-website/`.


---

# 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/public-website/docs/archive-docs_public-website/documentation-audit.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.