> 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-notes.md). # Implementation Notes **Session ID**: `phase15-session05-roadmap-faq-and-legal-pages` **Package**: public-website **Started**: 2026-06-02 01:09 **Last Updated**: 2026-06-02 01:09 *** ## Session Progress | Metric | Value | | ------------------- | ------- | | Tasks Completed | 22 / 22 | | Estimated Remaining | 0 hours | | Blockers | 0 | *** ### Task T001 - Verify prerequisites and route absence **Started**: 2026-06-02 01:07 **Completed**: 2026-06-02 01:09 **Duration**: 2 minutes **Notes**: * Ran the spec analyzer and resolved the active session to `phase15-session05-roadmap-faq-and-legal-pages`. * Confirmed the package context is `public-website`. * Verified required prior sessions are marked complete in spec state and Phase 15 session prerequisites are documented. * Confirmed `roadmap`, `faq`, and legal route/data/component targets are absent before implementation. * Confirmed Node 26.2.0 and npm 11.16.0 are available by prefixing PATH with the local nvm Node 26 binary directory. **Files Changed**: * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T001 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Initialized session notes and logged prerequisite verification. **BQC Fixes**: * N/A - setup verification only. *** ### Task T002 - Review website route and layout patterns **Started**: 2026-06-02 01:09 **Completed**: 2026-06-02 01:11 **Duration**: 2 minutes **Notes**: * Reviewed `site.ts`, navigation data, `BaseLayout`, `Shell`, `LegalLayout`, metadata helpers, JSON-LD validation, footer/header navigation, `SecurityFaq`, and company/contact/press route patterns. * Confirmed legal pages should use `LegalLayout` with `noindex` default review posture. * Confirmed new pages should keep data in typed package-local modules and compose static Astro routes without client scripts. * Confirmed footer already has placeholder roadmap/FAQ/legal links that should be moved to route constants. **Files Changed**: * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T002 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged current website pattern review. **BQC Fixes**: * N/A - setup review only. *** ### Task T003 - Review no-claim and legal-review boundaries **Started**: 2026-06-02 01:11 **Completed**: 2026-06-02 01:12 **Duration**: 1 minute **Notes**: * Reviewed the active security posture and project considerations before drafting page copy. * Confirmed cumulative open findings require no hosted identity, no trusted unified erasure, and no production-hosted validation claims. * Confirmed the static website must not add analytics, trackers, hosted forms, cookies, auth, CMS, runtime personalization, or server behavior. * Confirmed legal pages must remain visibly pre-review unless owner/legal-approved text is supplied, which was not supplied for this session. **Files Changed**: * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T003 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged active copy and trust boundaries. **BQC Fixes**: * Trust boundary enforcement: captured copy constraints up front so roadmap, FAQ, and legal routes do not overclaim unsupported hosted, data, or legal behavior. *** ### Task T004 - Extend site route constants and URLs **Started**: 2026-06-02 01:12 **Completed**: 2026-06-02 01:13 **Duration**: 1 minute **Notes**: * Added typed route constants and absolute URL constants for roadmap, FAQ, legal privacy, legal terms, and legal acceptable-use pages. * Added blog and news index constants so roadmap and FAQ links do not keep hard-coded route strings. **Files Changed**: * `public-website/src/data/site.ts` - Extended `sitePaths` and `siteUrls`. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T004 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged route constant implementation. **BQC Fixes**: * Contract alignment: centralized route constants so metadata, navigation, and data modules can share the same path contract. *** ### Task T005 - Create typed roadmap data **Started**: 2026-06-02 01:13 **Completed**: 2026-06-02 01:18 **Duration**: 5 minutes **Notes**: * Added typed roadmap metadata, route links, hero copy, current focus, planned themes, later themes, recently shipped items, CTA copy, and guardrails. * Wired recently shipped entries to existing news slugs and the news index instead of inventing release claims. * Kept roadmap copy theme-based with no exact delivery dates, no guaranteed sequencing, no SLA claims, and no hosted-service overclaims. **Files Changed**: * `public-website/src/data/roadmap.ts` - Created typed roadmap content and link contract. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T005 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged roadmap data implementation. **BQC Fixes**: * Contract alignment: used `satisfies` across route links, groups, shipped items, and CTA data so missing link keys fail type checking. * Trust boundary enforcement: embedded no-date, no-SLA, no-production-validation, no-hosted-identity, no-erasure, and no-certification guardrails in the page source data. *** ### Task T006 - Create typed FAQ data **Started**: 2026-06-02 01:18 **Completed**: 2026-06-02 01:25 **Duration**: 7 minutes **Notes**: * Added typed FAQ metadata, hero copy, seven categories, conservative entries, route links, CTA copy, boundary copy, and shared structured-data source. * Covered product, setup, privacy/security, demo/docs, integrations, teams, and hosted options. * Generated `FAQPage` JSON-LD from the same answer data used for rendering to keep content aligned. **Files Changed**: * `public-website/src/data/faq.ts` - Created typed FAQ content, link contract, and structured data. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T006 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged FAQ data implementation. **BQC Fixes**: * Contract alignment: centralized FAQ links and JSON-LD data with type-checked category and link keys. * Trust boundary enforcement: FAQ copy explicitly avoids hosted identity, trusted erasure, production validation, formal certification, analytics, hosted forms, and market/customer/fundraising claims. * Error information boundaries: external and mailto links carry explicit labels so visitors can distinguish destinations before navigation. *** ### Task T007 - Create roadmap timeline component **Started**: 2026-06-02 01:25 **Completed**: 2026-06-02 01:33 **Duration**: 8 minutes **Notes**: * Added a static `RoadmapTimeline` component that renders the roadmap guardrail, grouped roadmap sections, supporting links, recently shipped items, and deterministic empty states. * Used semantic sections, ordered lists for roadmap items, article headings, labelled navigation, and standard links with visible focus behavior inherited from global styles. * Kept the component free of scripts, runtime fetches, dynamic search, local storage, timers, subscriptions, or mutable UI state. **Files Changed**: * `public-website/src/components/marketing/RoadmapTimeline.astro` - Created grouped roadmap renderer. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T007 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged roadmap component implementation. **BQC Fixes**: * Accessibility and platform compliance: used native links, semantic headings, labelled sections, and deterministic empty-state text. * State freshness/resource cleanup: no client state, timers, subscriptions, storage, or event listeners were introduced. *** ### Task T008 - Create FAQ list component **Started**: 2026-06-02 01:33 **Completed**: 2026-06-02 01:41 **Duration**: 8 minutes **Notes**: * Added a static `FaqList` component that renders the no-overclaim boundary, category anchor navigation, native `details` disclosures, supporting links, and deterministic empty states. * Kept disclosure behavior platform-native with no scripts, dynamic search, runtime fetches, storage, or subscriptions. * Ensured external and mailto links are labelled separately and mailto links do not open in a new tab. **Files Changed**: * `public-website/src/components/marketing/FaqList.astro` - Created categorized FAQ renderer. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T008 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged FAQ component implementation. **BQC Fixes**: * Accessibility and platform compliance: used native `details`/`summary`, labelled category navigation, labelled supporting links, and visible focus behavior. * State freshness/resource cleanup: no custom disclosure state, timers, event listeners, or client-side lifecycle resources were introduced. *** ### Task T009 - Implement roadmap route **Started**: 2026-06-02 01:41 **Completed**: 2026-06-02 01:49 **Duration**: 8 minutes **Notes**: * Added `/roadmap` using `BaseLayout`, `Shell`, canonical metadata, social metadata, existing structured data, and `RoadmapTimeline`. * Rendered hero posture badges, supporting links, no-commitment boundary copy, shipped news evidence links, and a static CTA. * Kept the route script-free and static. **Files Changed**: * `public-website/src/pages/roadmap.astro` - Created roadmap route. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T009 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged roadmap route implementation. **BQC Fixes**: * Trust boundary enforcement: route-level copy states the roadmap is not a schedule, SLA, legal notice, funding update, customer announcement, or production validation claim. * Accessibility and platform compliance: used labelled hero, nav regions, native links, and responsive wrapping constraints. *** ### Task T010 - Implement FAQ route **Started**: 2026-06-02 01:49 **Completed**: 2026-06-02 01:56 **Duration**: 7 minutes **Notes**: * Added `/faq` using `BaseLayout`, `Shell`, canonical metadata, social metadata, organization/site structured data, and FAQ structured data generated from typed FAQ answers. * Rendered the hero, static boundary, native disclosure list, category navigation, and CTA. * Kept the route script-free with no dynamic search behavior. **Files Changed**: * `public-website/src/pages/faq.astro` - Created FAQ route. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T010 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged FAQ route implementation. **BQC Fixes**: * Contract alignment: FAQPage JSON-LD uses the same typed entries rendered by the route. * Accessibility and platform compliance: native disclosures, labelled category navigation, and link labels keep keyboard behavior platform-native. * State freshness/resource cleanup: no client-side search state, storage, fetches, timers, or event listeners were introduced. *** ### Task T011 - Implement legal hub route **Started**: 2026-06-02 01:56 **Completed**: 2026-06-02 02:01 **Duration**: 5 minutes **Notes**: * Added `/legal` using `LegalLayout` with policy route cards for privacy, terms, and acceptable use. * Marked each policy as a pre-review placeholder and documented the static-site scope. * Kept the route `noindex` through the existing legal layout default. **Files Changed**: * `public-website/src/pages/legal/index.astro` - Created legal hub route. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T011 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged legal hub implementation. **BQC Fixes**: * Trust boundary enforcement: legal index states it is not final legal approval, consent capture, account terms acceptance, or a hosted policy workflow. * Accessibility and platform compliance: policy cards use stable IDs, labelled headings, and normal links/buttons. *** ### Task T012 - Implement privacy policy route **Started**: 2026-06-02 02:01 **Completed**: 2026-06-02 02:07 **Duration**: 6 minutes **Notes**: * Added `/legal/privacy` with `LegalLayout`, explicit pre-review status, static website data posture, separate external-boundary notes, and reviewer prompts. * Stated no analytics, hosted forms, cookies, accounts, auth, localStorage writes, runtime personalization, or sensitive payload collection is added by the website. * Kept broader hosted identity, trusted erasure, and production-hosted validation findings open. **Files Changed**: * `public-website/src/pages/legal/privacy.astro` - Created privacy placeholder route. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T012 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged privacy route implementation. **BQC Fixes**: * Trust boundary enforcement: policy copy is explicitly pre-review and does not imply final legal approval or website data collection. * Error information boundaries: privacy route exposes only stable boundary statements, not internal security evidence details. *** ### Task T013 - Implement terms route **Started**: 2026-06-02 02:07 **Completed**: 2026-06-02 02:12 **Duration**: 5 minutes **Notes**: * Added `/legal/terms` with `LegalLayout`, explicit pre-review status, website scope, placeholder limitations, reviewer prompts, and supporting links. * Stated the placeholder does not create a contract, checkout flow, account terms acceptance, or service agreement. * Kept roadmap, warranty, hosted validation, hosted identity, trusted erasure, and future hosted-service claims bounded. **Files Changed**: * `public-website/src/pages/legal/terms.astro` - Created terms placeholder route. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T013 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged terms route implementation. **BQC Fixes**: * Trust boundary enforcement: terms route explicitly avoids final legal approval and policy acceptance workflow claims. * Accessibility and platform compliance: route uses semantic sections, headings, lists, and labelled supporting links. *** ### Task T014 - Implement acceptable-use route **Started**: 2026-06-02 02:12 **Completed**: 2026-06-02 02:18 **Duration**: 6 minutes **Notes**: * Added `/legal/acceptable-use` with `LegalLayout`, explicit pre-review status, conservative use themes, no hosted enforcement claim, and reviewer prompts. * Stated the placeholder does not create hosted account policy, moderation workflow, enforcement system, or final product terms. **Files Changed**: * `public-website/src/pages/legal/acceptable-use.astro` - Created acceptable-use placeholder route. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T014 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged acceptable-use route implementation. **BQC Fixes**: * Trust boundary enforcement: route avoids hosted account enforcement, moderation, SSO, organization membership, production auditability, or final policy claims. * Accessibility and platform compliance: route uses semantic sections, labelled navigation, and static cards with responsive wrapping. *** ### Task T015 - Wire roadmap shipped links to existing news **Started**: 2026-06-02 02:18 **Completed**: 2026-06-02 02:20 **Duration**: 2 minutes **Notes**: * Verified roadmap recently shipped entries point to existing news markdown slugs. * Kept shipped copy framed as existing website evidence rather than invented release claims or exact delivery history. **Files Changed**: * `public-website/src/data/roadmap.ts` - Recently shipped links and evidence copy already implemented in T005 and verified here. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T015 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged shipped-link verification. **BQC Fixes**: * Contract alignment: verified every shipped link key resolves to an existing news content slug. * Trust boundary enforcement: kept shipped references evidence-based and avoided release history invention. *** ### Task T016 - Wire FAQ links and boundary answers **Started**: 2026-06-02 02:20 **Completed**: 2026-06-02 02:22 **Duration**: 2 minutes **Notes**: * Verified FAQ internal links point to existing product, features, how-it-works, use-case, security, contact, roadmap, FAQ, and legal routes. * Kept demo/docs as explicit external destinations and product/security contact as mailto links. * Confirmed FAQ answer copy preserves no hosted identity, no analytics, no hosted form, and no production validation boundaries. **Files Changed**: * `public-website/src/data/faq.ts` - FAQ links and conservative copy already implemented in T006 and verified here. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T016 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged FAQ link verification. **BQC Fixes**: * Contract alignment: verified linked route files exist for each internal FAQ target. * Trust boundary enforcement: preserved external/mailto labels and no-overclaim wording. *** ### Task T017 - Align footer navigation route constants **Started**: 2026-06-02 02:22 **Completed**: 2026-06-02 02:24 **Duration**: 2 minutes **Notes**: * Replaced hard-coded footer links for blog, news, roadmap, FAQ, and legal subpages with `sitePaths` constants. * Added footer link descriptions for the new trust and legal routes while preserving product, company, demo, docs, blog, and news reachability. **Files Changed**: * `public-website/src/data/navigation.ts` - Updated footer navigation hrefs and descriptions. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T017 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged navigation update. **BQC Fixes**: * Contract alignment: footer navigation now shares the same route constants as pages, data modules, and metadata. *** ### Task T018 - Review metadata, JSON-LD, CTAs, labels, and no-overclaim copy **Started**: 2026-06-02 02:24 **Completed**: 2026-06-02 02:28 **Duration**: 4 minutes **Notes**: * Reviewed new page metadata, canonical path usage, FAQ structured-data source, legal review labels, CTAs, and no-overclaim language across all six routes. * Moved older hard-coded blog, news, and FAQ links in existing data modules to `sitePaths` constants. * Confirmed scan hits for hosted identity, trusted erasure, production validation, certification, analytics, hosted forms, final approval, and customer/market/fundraising terms appear only in explicit no-claim or pre-review contexts. **Files Changed**: * `public-website/src/data/company.ts` - Reused `sitePaths.blog` and `sitePaths.news`. * `public-website/src/data/security.ts` - Reused `sitePaths.faq` and updated FAQ link description. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T018 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged metadata and copy consistency pass. **BQC Fixes**: * Contract alignment: removed stale route literals outside the central `sitePaths` definition. * Trust boundary enforcement: verified sensitive terms are used as explicit no-claim or pre-review language rather than positive claims. *** ### Task T019 - Run package typecheck **Started**: 2026-06-02 02:28 **Completed**: 2026-06-02 02:29 **Duration**: 1 minute **Notes**: * Ran `npm --workspace @factionos/public-website run typecheck` under Node 26.2.0. * Initial run found two FAQ data type issues: contact target optional label access and overly narrow tuple inference when flattening FAQ entries. * Fixed `createMailtoLink` to use a stable mailto label and typed `faqEntries` as `readonly FaqEntry[]`. * Reran the command successfully. **Files Changed**: * `public-website/src/data/faq.ts` - Fixed FAQ type contracts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T019 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged typecheck results. **BQC Fixes**: * Contract alignment: resolved TypeScript issues in FAQ link metadata and structured-data source generation. *** ### Task T020 - Run static build and inspect generated HTML **Started**: 2026-06-02 02:29 **Completed**: 2026-06-02 02:31 **Duration**: 2 minutes **Notes**: * Ran `npm --workspace @factionos/public-website run build` under Node 26.2.0. * Build generated `/roadmap`, `/faq`, `/legal`, `/legal/privacy`, `/legal/terms`, and `/legal/acceptable-use`. * Inspected generated HTML for canonical URLs, FAQPage JSON-LD, legal noindex robots, review markers, shipped news links, footer links, and no-date/pre-review boundary copy. **Files Changed**: * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T020 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged build and HTML inspection results. **BQC Fixes**: * Contract alignment: verified built HTML includes expected route metadata, structured data, and generated static paths. * Trust boundary enforcement: verified no-date and pre-review boundary strings are present in built output. *** ### Task T021 - Browser smoke responsive, keyboard, and link behavior **Started**: 2026-06-02 02:31 **Completed**: 2026-06-02 02:35 **Duration**: 4 minutes **Notes**: * Started `astro preview` at `http://127.0.0.1:4325/`. * Ran a Playwright smoke script across desktop 1440px, tablet 820px, and 360px mobile viewports for `/roadmap`, `/faq`, `/legal`, `/legal/privacy`, `/legal/terms`, and `/legal/acceptable-use`. * Verified no horizontal overflow, footer reachability, FAQ category anchor navigation, keyboard-opened FAQ disclosures, visible keyboard focus, legal review markers, external demo/docs links, and mailto links. * Saved screenshots under `/tmp/factionos-session05-smoke`. **Files Changed**: * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T021 complete and updated progress counts. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged browser smoke results. **BQC Fixes**: * Accessibility and platform compliance: validated FAQ disclosure keyboard behavior, visible focus, footer reachability, and responsive rendering. * State freshness/resource cleanup: browser smoke closed Playwright contexts and did not find client-side state regressions in the new static routes. *** ### Task T022 - Validate encoding, line endings, behavior absence, and copy guardrails **Started**: 2026-06-02 02:35 **Completed**: 2026-06-02 02:37 **Duration**: 2 minutes **Notes**: * Validated touched source and spec files are ASCII-only. * Validated touched source and spec files use Unix LF line endings. * Scanned new route, component, and data files for client directives, scripts, local storage, cookies, fetches, WebSockets, EventSource, timers, analytics, hosted forms, and sensitive claim terms. * Confirmed sensitive terms appear only in explicit no-claim, no-collection, or pre-review language. * Stopped the local preview server after browser smoke validation. **Files Changed**: * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/tasks.md` - Marked T022 and completion checklist complete. * `.spec_system/specs/phase15-session05-roadmap-faq-and-legal-pages/implementation-notes.md` - Logged final guardrail validation. **BQC Fixes**: * Trust boundary enforcement: verified no positive hosted identity, trusted erasure, production validation, certification, exact roadmap date, analytics, hosted form, customer, traction, revenue, market-size, or fundraising claims were introduced. * Resource cleanup: stopped the preview server used for smoke testing. *** ## Session Closeout **Completed**: 2026-06-02 02:37 **Final Status**: * Tasks completed: 22 / 22 * Typecheck: pass * Build: pass * Browser smoke: pass * ASCII/LF: pass * Ready for validate workflow step ## Task Log ### 2026-06-02 - Session Start **Environment verified**: * [x] Spec system prerequisites confirmed * [x] Package directory and manifest available * [x] Node 26.2.0 and npm 11.16.0 available through the local nvm install * [x] Directory structure ready * [x] Database not applicable *** --- # 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-notes.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.