> 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-session01-use-cases-hub-and-role-pages/tasks.md). # Task Checklist **Session ID**: `phase15-session01-use-cases-hub-and-role-pages` **Total Tasks**: 23 **Estimated Duration**: 3-4 hours **Created**: 2026-06-01 *** ## Legend * `[x]` = Completed * `[ ]` = Pending * `[P]` = Parallelizable (can run with other \[P] tasks) * `[S1501]` = Session reference (15=phase number, 01=session number) * `TNNN` = Task ID *** ## Progress Summary | Category | Total | Done | Remaining | | -------------- | ------ | ------ | --------- | | Setup | 3 | 3 | 0 | | Foundation | 6 | 6 | 0 | | Implementation | 10 | 10 | 0 | | Testing | 4 | 4 | 0 | | **Total** | **23** | **23** | **0** | *** ## Setup (3 tasks) Initial configuration and environment preparation. * [x] T001 \[S1501] Verify public website prerequisites, package scripts, existing routes, and Phase 14 link targets before adding `/use-cases` (`public-website/package.json`) * [x] T002 \[S1501] Review existing product, features, how-it-works, layout, CTA, and marketing component patterns for use-case route composition (`public-website/src/pages/product.astro`) * [x] T003 \[S1501] Confirm route constants, external demo/docs destinations, primary navigation capacity, and footer use-case reachability (`public-website/src/data/site.ts`) *** ## Foundation (6 tasks) Core structures and base implementations. * [x] T004 \[S1501] Define typed use-case route metadata, role keys, shared pain points, workflow rows, surface mappings, proof examples, CTA targets, and boundary copy with types matching declared contract; exhaustive enum handling (`public-website/src/data/use-cases.ts`) * [x] T005 \[S1501] Add use-case route constants and canonical URLs for hub and role pages without duplicating literal paths in route metadata (`public-website/src/data/site.ts`) * [x] T006 \[S1501] \[P] Create accessible use-case grid component for role cards, shared pain points, and route links with platform-appropriate accessibility labels, focus management, and input support (`public-website/src/components/marketing/UseCaseGrid.astro`) * [x] T007 \[S1501] \[P] Create reusable role-page component for problem, workflow, surfaces, proof examples, boundary notes, and CTAs with mobile-safe wrapping and no color-only semantics (`public-website/src/components/marketing/UseCaseRolePage.astro`) * [x] T008 \[S1501] \[P] Add hub and role CTA/link helpers for demo, docs, product, features, how-it-works, and security handoffs without implying hosted accounts or analytics (`public-website/src/data/use-cases.ts`) * [x] T009 \[S1501] Add Use Cases to primary/mobile navigation and verify footer link alignment with active-route behavior (`public-website/src/data/navigation.ts`) *** ## Implementation (10 tasks) Main feature implementation. * [x] T010 \[S1501] Implement `/use-cases` hub route with BaseLayout, Shell, canonical metadata, structured data, hero copy, shared pain points, role grid, and static-site boundary copy (`public-website/src/pages/use-cases/index.astro`) * [x] T011 \[S1501] Implement engineering teams role route with problem statement, before/after workflow, surfaces, examples, and CTAs while avoiding hosted team-management claims (`public-website/src/pages/use-cases/engineering-teams.astro`) * [x] T012 \[S1501] Implement AI platform teams role route with protocol, hooks, event visibility, diagnostics, integration guardrails, and CTAs while avoiding inbound command claims (`public-website/src/pages/use-cases/ai-platform-teams.astro`) * [x] T013 \[S1501] Implement founders role route with multi-agent control, demo/docs exploration, product wedge clarity, examples, and CTAs while avoiding metrics or ROI claims (`public-website/src/pages/use-cases/founders.astro`) * [x] T014 \[S1501] Implement power users role route with local control, replay, prompt lifecycle visibility, approvals, diagnostics, demo exploration, and CTAs (`public-website/src/pages/use-cases/power-users.astro`) * [x] T015 \[S1501] Populate engineering teams data with shared visibility, review context, mission status, local privacy boundaries, examples, and role-specific links (`public-website/src/data/use-cases.ts`) * [x] T016 \[S1501] Populate AI platform teams data with provider-neutral hooks, protocol boundaries, event visibility, diagnostics, guardrail-friendly integration, and role-specific links (`public-website/src/data/use-cases.ts`) * [x] T017 \[S1501] Populate founders data with multiple-agent control, conservative product wedge copy, zero-install exploration, proof examples, and no unverifiable metrics (`public-website/src/data/use-cases.ts`) * [x] T018 \[S1501] Populate power users data with local control, replay, prompt lifecycle visibility, approval context, diagnostics, proof examples, and demo/docs handoffs (`public-website/src/data/use-cases.ts`) * [x] T019 \[S1501] Finalize responsive scoped CSS for hub cards, pain point panels, role workflows, surface lists, proof examples, and CTA rows with stable dimensions and no text overlap (`public-website/src/components/marketing/UseCaseRolePage.astro`) *** ## Testing (4 tasks) Verification and quality assurance. * [x] T020 \[S1501] Run package typecheck and resolve any Astro or TypeScript errors (`public-website/package.json`) * [x] T021 \[S1501] Run static website build and verify built use-case hub plus all four role route outputs include expected metadata, links, and boundary copy (`public-website/dist/use-cases/index.html`) * [x] T022 \[S1501] Manually smoke desktop, tablet, 360px mobile, keyboard focus, reduced-motion posture, hub grid wrapping, role workflow stacking, CTA rows, and navigation reachability (`public-website/src/pages/use-cases/index.astro`) * [x] T023 \[S1501] Validate ASCII encoding, Unix LF line endings, and copy guardrails for no hosted overclaim, no analytics, no hosted forms, no ROI metrics, and static demo/docs separation (`public-website/src/data/use-cases.ts`) *** ## 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 implement workflow step to begin AI-led implementation. --- # 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-session01-use-cases-hub-and-role-pages/tasks.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.