> 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/phase14-session01-hero-cockpit-and-primary-ctas/tasks.md). # Task Checklist **Session ID**: `phase14-session01-hero-cockpit-and-primary-ctas` **Total Tasks**: 22 **Estimated Duration**: 2-4 hours **Created**: 2026-06-01 *** ## Legend * `[x]` = Completed * `[ ]` = Pending * `[P]` = Parallelizable (can run with other \[P] tasks) * `[SNNMM]` = Session reference (NN=phase number, MM=session number) * `TNNN` = Task ID *** ## Progress Summary | Category | Total | Done | Remaining | | -------------- | ------ | ------ | --------- | | Setup | 3 | 3 | 0 | | Foundation | 6 | 6 | 0 | | Implementation | 9 | 9 | 0 | | Testing | 4 | 4 | 0 | | **Total** | **22** | **22** | **0** | *** ## Setup (3 tasks) Initial configuration and environment preparation. * [x] T001 \[S1401] Verify public website prerequisites and package commands (`public-website/package.json`) * [x] T002 \[S1401] Create marketing component directory for homepage deliverables (`public-website/src/components/marketing`) * [x] T003 \[S1401] Review existing homepage placeholder and integration points (`public-website/src/pages/index.astro`) *** ## Foundation (6 tasks) Core structures and base implementations. * [x] T004 \[S1401] \[P] Create typed homepage hero copy and simulated readout data with no-live-data labels (`public-website/src/data/homepage.ts`) * [x] T005 \[S1401] \[P] Define terminal prompt rows, provider labels, and trust badges with static-only wording (`public-website/src/data/homepage.ts`) * [x] T006 \[S1401] \[P] Create `LiveStatusPanel.astro` shell with bounded status list markup and accessible labels (`public-website/src/components/marketing/LiveStatusPanel.astro`) * [x] T007 \[S1401] \[P] Create `HeroCockpit.astro` shell using existing Section, ButtonLink, Badge, and media primitives (`public-website/src/components/marketing/HeroCockpit.astro`) * [x] T008 \[S1401] Add registry-backed brand asset usage or text-first fallback without promoting conditional showcase media (`public-website/src/components/marketing/HeroCockpit.astro`) * [x] T009 \[S1401] Add component-scoped cockpit grid, terminal, and readout styles with stable dimensions (`public-website/src/components/marketing/HeroCockpit.astro`) *** ## Implementation (9 tasks) Main feature implementation. * [x] T010 \[S1401] Implement simulated local runtime status cards with explicit static-data and no-analytics copy (`public-website/src/components/marketing/LiveStatusPanel.astro`) * [x] T011 \[S1401] Implement terminal command and event hints with wrapping and deterministic ordering (`public-website/src/components/marketing/HeroCockpit.astro`) * [x] T012 \[S1401] Wire demo and docs CTAs from site data with accessible names, external-link semantics, and focus support (`public-website/src/components/marketing/HeroCockpit.astro`) * [x] T013 \[S1401] Implement privacy and local-first badges without hosted identity or production-validation claims (`public-website/src/components/marketing/HeroCockpit.astro`) * [x] T014 \[S1401] Add responsive desktop hero composition that keeps brand, product concept, and CTAs in the first viewport (`public-website/src/components/marketing/HeroCockpit.astro`) * [x] T015 \[S1401] Add mobile hero composition with full-width CTA controls, clean wrapping, and no horizontal overflow (`public-website/src/components/marketing/HeroCockpit.astro`) * [x] T016 \[S1401] Add reduced-motion handling for hero scanlines, pulses, and decorative effects while preserving static state labels (`public-website/src/components/marketing/HeroCockpit.astro`) * [x] T017 \[S1401] Replace the Phase 13 homepage placeholder hero with `HeroCockpit` and updated homepage metadata (`public-website/src/pages/index.astro`) * [x] T018 \[S1401] Add reusable global helpers only if needed for hero layout or wrapping behavior (`public-website/src/styles/global.css`) *** ## Testing (4 tasks) Verification and quality assurance. * [x] T019 \[S1401] Run Astro typecheck and fix component or data typing issues (`public-website/package.json`) * [x] T020 \[S1401] Run static website build and fix route, image, or metadata output issues (`public-website/package.json`) * [x] T021 \[S1401] Manually verify 360px, 768px, 1280px, wide desktop, keyboard focus, and reduced-motion hero behavior (`.spec_system/specs/phase14-session01-hero-cockpit-and-primary-ctas/implementation-notes.md`) * [x] T022 \[S1401] Validate ASCII encoding and Unix LF line endings for session artifacts and touched website files (`.spec_system/specs/phase14-session01-hero-cockpit-and-primary-ctas`) *** ## 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/phase14-session01-hero-cockpit-and-primary-ctas/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.