> 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/phase13-session05-asset-pipeline-and-brand-media-prep/tasks.md). # Task Checklist **Session ID**: `phase13-session05-asset-pipeline-and-brand-media-prep` **Total Tasks**: 18 **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 | 5 | 5 | 0 | | Implementation | 7 | 7 | 0 | | Testing | 3 | 3 | 0 | | **Total** | **18** | **18** | **0** | *** ## Setup (3 tasks) Initial configuration and environment preparation. * [x] T001 \[S1305] Verify Phase 13 prerequisites, completed Sessions 01-04 deliverables, Node 26.2.0+ PATH, and current Astro image API assumptions (`.spec_system/specs/phase13-session05-asset-pipeline-and-brand-media-prep/implementation-notes.md`) * [x] T002 \[S1305] Inventory existing brand/showcase assets, current website favicon/manifest, social metadata defaults, and absent mockup status before editing (`.spec_system/specs/phase13-session05-asset-pipeline-and-brand-media-prep/asset-provenance-notes.md`) * [x] T003 \[S1305] Create target directories for optimized brand assets, showcase assets, media components, and press pass-through files (`public-website/src/assets/brand/factionos-logo.webp`) *** ## Foundation (5 tasks) Core structures and base implementations. * [x] T004 \[S1305] \[P] Create website asset provenance notes with launch-ready, conditional, blocked, source, destination, and validation fields (`.spec_system/specs/phase13-session05-asset-pipeline-and-brand-media-prep/asset-provenance-notes.md`) * [x] T005 \[S1305] \[P] Import approved brand logo sources into package-local Astro asset paths with provenance recorded and no unknown-provenance promotion (`public-website/src/assets/brand/factionos-logo.webp`) * [x] T006 \[S1305] \[P] Import approved showcase strip, cover, banner, and frame sources into package-local Astro asset paths with byte-size and source notes (`public-website/src/assets/showcase/factionos-strip.webp`) * [x] T007 \[S1305] Create typed media registry for imported images, alt text, use cases, dimensions, provenance status, and exhaustive asset-key handling (`public-website/src/lib/media.ts`) * [x] T008 \[S1305] Create optimized media component pattern using Astro image primitives with required alt text, loading policy, dimensions, and fallback behavior (`public-website/src/components/media/OptimizedMedia.astro`) *** ## Implementation (7 tasks) Main feature implementation. * [x] T009 \[S1305] Create or select Open Graph fallback image from approved brand media with documented source and no generated-draft promotion (`public-website/src/assets/brand/og-default.png`) * [x] T010 \[S1305] Update site data defaults for social image path, social image alt text, Twitter card posture, and static website identity boundaries (`public-website/src/data/site.ts`) * [x] T011 \[S1305] Update metadata resolution for the approved social image fallback with absolute URL output and deterministic fallback behavior (`public-website/src/lib/metadata.ts`) * [x] T012 \[S1305] Update SEO component metadata output for Open Graph/Twitter image fields without breaking existing page and article routes (`public-website/src/components/seo/Seo.astro`) * [x] T013 \[S1305] Review and refine favicon SVG against approved brand mark while preserving accessible title and small-size readability (`public-website/public/favicon.svg`) * [x] T014 \[S1305] Review and refine web manifest for static-site browser metadata, theme colors, icon references, and no unsupported PWA/install claims (`public-website/public/site.webmanifest`) * [x] T015 \[S1305] Create press pass-through policy and copy only approved downloadable launch files when available with explicit provenance notes (`public-website/public/press/README.md`) *** ## Testing (3 tasks) Verification and quality assurance. * [x] T016 \[S1305] Run public website typecheck and build, then inspect generated social metadata, favicon, manifest, and optimized asset output (`public-website/package.json`) * [x] T017 \[S1305] Run focused Biome format/lint checks and relevant media gates or document why unchanged shared-media gates are not applicable (`public-website/src/lib/media.ts`) * [x] T018 \[S1305] Validate ASCII/LF encoding and record verification notes, residual media risks, and no-overclaim review (`.spec_system/specs/phase13-session05-asset-pipeline-and-brand-media-prep/implementation-notes.md`) *** ## 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/phase13-session05-asset-pipeline-and-brand-media-prep/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.