> 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/phase21-session07-final-regression-and-documentation/documentation-audit.md). # Documentation Audit **Session ID**: `phase21-session07-final-regression-and-documentation` **Package**: apps/web **Date**: 2026-06-29 *** ## Audit Scope Stable documentation reviewed for the Phase 21 closeout: * `docs/orchestration-quickstart.md` * `apps/web/README_web.md` * `docs/README_docs.md` * `docs/ARCHITECTURE.md` * `README.md` The audit looked for: * The primary Command Center entry path. * Campaigns, Queue, File/Git, terminal runtime controls, and other workbench locations. * Any wording that treats summary or detail popups as the primary Command Center work surface. * No-claim boundaries for hosted execution, production-hosted validation, hosted identity, formal certification, remote execution, and trusted erasure. *** ## Findings | File | Finding | Required action | | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | `docs/orchestration-quickstart.md` | The quickstart says to use the Orchestration surface and lists Command Center tabs, but it does not name the bottom-rail compact/focused path or explain that focused mode is the primary working surface. | Update Open The Command Center and affected steps to use the bottom-rail Orchestration focused Command Center path. | | `apps/web/README_web.md` | The README documents Command Center workbench contracts and adjacent-surface links, but it lacks the Phase 21 compact/focused bottom-rail contract and does not call retained summaries secondary inspectors. | Add a bottom-rail focused-surface contract tying compact and focused Quest Board, Orchestration, and War Room surfaces to one mounted implementation. | | `docs/README_docs.md` | Command Center routing lists Phase 19 and Phase 20 sources only. It does not mention Phase 21 focused-surface routing. | Add Phase 21 focused-surface routing guidance to the Command Center docs table. | | `docs/ARCHITECTURE.md` | Architecture says the web cockpit consumes Command Center snapshots in the Orchestration panel, but it does not describe compact and focused Orchestration presentations. | Update the Command Center architecture paragraph to include bottom-rail compact/focused Orchestration surfaces. | | `README.md` | Product Surface lists Command Center and Quest Board, but it does not describe focused bottom-rail access to Quest Board, Command Center, and War Room. | Add concise product-surface wording for the focused bottom-rail path. | *** ## No-Claim Boundary Check | Boundary | Result | Evidence | | ------------------------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Hosted execution and remote execution | PASS | `README.md` keeps remote/hosted execution as a no-claim boundary; `docs/README_docs.md` and `docs/ARCHITECTURE.md` keep broad remote execution and hosted execution out of shipped behavior. | | Production-hosted validation | PASS | `apps/web/README_web.md` and `docs/ARCHITECTURE.md` distinguish local browser evidence from production-hosted validation. | | Hosted identity and hosted storage | PASS | `README.md`, `docs/README_docs.md`, `docs/ARCHITECTURE.md`, and `apps/web/README_web.md` preserve local-first and no hosted account/storage language. | | Formal certification | PASS | `apps/web/README_web.md` avoids turning local accessibility evidence into certification; no reviewed file makes a formal certification claim. | | Trusted erasure | PASS | `apps/web/README_web.md`, `docs/README_docs.md`, and `docs/ARCHITECTURE.md` preserve trusted erasure no-claim language. | *** ## Summary The stable docs preserve the required no-claim boundaries. The needed updates are routing and product-surface clarity only: Campaigns, Queue, File/Git, terminal runtime controls, and other workbenches should be described as Command Center work under the bottom-rail Orchestration focused surface, while any retained summaries or detail popups remain secondary inspectors. --- # 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/phase21-session07-final-regression-and-documentation/documentation-audit.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.