> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_40/session_10_assets_and_media_compliance.md). # Session 10: Assets And Media Compliance **Session ID**: `phase40-session10-assets-and-media-compliance` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Rehome required Ministry and model-vendor visuals without violating AI OS media policy or duplicating existing assets. *** ## Scope ### In Scope (MVP) * Audit the staged upstream 2.8.1 to 2.10.1 media gap: 15 provider `src/assets/logo-*.svg` files and `src/assets/ministry-hero.webp`. * Compare imported root provider logos with existing AI OS `src/assets/logos/` equivalents before final UI wiring, then rehome or document root usage. * Validate SVG contents and avoid duplicate or unused assets. * Keep `src/assets/ministry-hero.webp` as the optimized AI OS copy (520x654, 185,156 bytes) unless Session 10 replaces it with another policy-compliant Ministry visual. * Run `bash scripts/check-asset-sizes.sh` after asset choices. ### Out of Scope * Media policy exceptions for this port. * Adding upstream media outside the audited 2.8.1 to 2.10.1 gap. * Changing AI OS package identity or graph files as part of asset work. *** ## Prerequisites * [ ] Session 01 media and asset invariants are recorded. * [ ] Upstream media gap assets are staged in `src/assets/` for final audit. * [ ] Session 09 final vendor/model list is available or asset audit can proceed independently. *** ## Deliverables 1. Verified vendor logo and Ministry visual assets matching repo conventions. 2. Asset provenance and policy notes, including source-path gap audit and hero compression details. 3. Asset-size validation results. *** ## Success Criteria * [ ] All new assets comply with `docs/media-policy.md`. * [ ] Ministry has a distinctive visual treatment without failing asset checks. * [ ] No unsafe SVG content, duplicate logo usage, or unused provider assets remain after final UI wiring. *** ## Folded Source Session Split The section below preserves the original Phase 40 session split detail for this session, including dependencies, decisions, outputs, and acceptance checks. ### Session 10: Assets And Media Compliance **Objective**: Rehome required Ministry and model-vendor visuals without violating AI OS media policy or duplicating existing assets. **Scope**: * Audit the staged upstream 2.8.1 to 2.10.1 media gap: 15 provider `src/assets/logo-*.svg` files and `src/assets/ministry-hero.webp`. * Compare imported root provider logos with existing AI OS `src/assets/logos/` equivalents before final UI wiring, then rehome or document root usage. * Validate SVG contents and avoid duplicate or unused assets. * Keep `src/assets/ministry-hero.webp` as the optimized AI OS copy (520x654, 185,156 bytes) unless Session 10 replaces it with another policy-compliant Ministry visual. * Run `bash scripts/check-asset-sizes.sh` after asset choices. **Outputs**: * Vendor logo and Ministry visual assets that match repo conventions. * Asset provenance and policy notes, including source-path gap audit and hero compression details. * Asset-size validation results. **Dependencies / Notes**: * Depends on Sessions 01 and 09 for the final vendor/model list. * Can start with an audit before Session 09 completes. * The staged gap came from the local Claude OS v2.10.1 upstream checkout compared against `claude-os-v2.8.1`; shared upstream media was unchanged and no upstream media files were removed. **Acceptance Checks**: * All new assets comply with `docs/media-policy.md`. * Ministry has a distinctive visual treatment without failing asset checks. * No unsafe SVG content, duplicate logo usage, or unused provider assets remain after final UI wiring. --- # 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://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_40/session_10_assets_and_media_compliance.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.