> 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/phases/phase_04/session_04_visual_promotion_tooling_and_budgets.md).

# Session 04: Visual Promotion Tooling and Budgets

**Session ID**: `phase04-session04-visual-promotion-tooling-and-budgets` **Status**: Not Started **Estimated Tasks**: \~16-22 **Estimated Duration**: 2-4 hours

***

## Objective

Create repeatable visual media promotion tooling that validates inventory, optimization, metadata, runtime paths, parity, and byte budgets.

***

## Scope

### In Scope (MVP)

* Add or extend repository media scripts for catalog validation, image probing, byte-budget checks, metadata inspection or stripping, and docs path checks.
* Consume Session 03 draft-generation manifests or explicitly documented deferrals when visual assets need first-draft references.
* Preserve the existing battlefield parity gate while making future visual assets easier to register and validate.
* Define output conventions for approved references, optimized app runtime copies, public demo copies, and prototype-only artifacts.
* Add tests or fixture checks for missing files, unsupported formats, unexpected dimensions, stale docs references, and cache-list drift.
* Document local tooling prerequisites and failure remediation in stable docs or package READMEs.

### Out of Scope

* Generating or regenerating provider-backed visual assets beyond small corrective drafts.
* Adding a sprite atlas unless Session 01 proves standalone files are insufficient.
* Changing battlefield interaction behavior unrelated to media promotion checks.

***

## Prerequisites

* [ ] Session 02 catalog contracts and fixtures exist.
* [ ] Session 03 draft generation outputs, manifests, or explicit no-new-asset deferrals exist.
* [ ] Current media tooling baseline has been verified with `npm run media:check`.

***

## Deliverables

1. Visual media validation and promotion scripts.
2. Budget and metadata checks for cataloged visual assets.
3. Updated battlefield or app/demo parity checks where visual media scope expands.
4. Stable docs for visual media promotion and failure handling.

***

## Success Criteria

* [ ] Visual assets have automated checks for existence, format, size, dimensions, metadata, and catalog consistency.
* [ ] App and public demo copies stay aligned when visual media is shared across surfaces.
* [ ] Quarantined or prototype-only files cannot pass release promotion checks as runtime assets.


---

# 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/phases/phase_04/session_04_visual_promotion_tooling_and_budgets.md?ask=<question>&goal=<endgoal>
```

`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.