> 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/assets/generated/phase04/readme_phase04.md).

# Phase 04 Generated Drafts

This directory stores tracked evidence for Phase 04 generated-draft planning. It does not store raw provider outputs and it does not define runtime media.

## Boundary

* Tracked files here are review evidence, safe briefs, and provenance records.
* Raw provider outputs belong only under `tmp/media-generation/phase04-session03/`, which is ignored by git.
* Drafts are non-runtime and non-release until a later promotion session approves source, rights, optimization, metadata, size, accessibility, privacy, fallback, and public-demo parity gates.
* No app component, public-demo cache entry, release artifact, or docs page may treat a draft record as approved media.

## Files

| File                             | Purpose                                                                                                |
| -------------------------------- | ------------------------------------------------------------------------------------------------------ |
| `draft-briefs.md`                | Redacted product-safe generation briefs and rejection criteria.                                        |
| `draft-generation-manifest.json` | Provenance, rights, cost, disposition, output metadata, and blockers for generated or deferred drafts. |

The repository-relative manifest path used by promotion tooling is `assets/generated/phase04/draft-generation-manifest.json`.

## Ignored Staging

Provider-backed generation writes to:

```
tmp/media-generation/phase04-session03/
```

The staging path may contain raw images, audio, provider metadata, local probe summaries, or failed partial outputs. Keep it ignored, local, and disposable. Do not copy raw staging output into tracked runtime locations during this session.

## Provider Safety

Provider credentials are local-only. Generation tools may check whether `FAL_KEY` or `ELEVENLABS_API_KEY` is present, but must not print, copy, commit, or summarize credential values, account IDs, raw request payloads, raw response payloads, or broad local paths.

Tracked briefs are intentionally redacted. They describe product need, style, event mapping, fallback expectations, and rejection criteria without copying `EXAMPLES/` media or sensitive prompt context.

## Review States

Draft records use non-release states until later gates promote them:

* `generated_reference`
* `planned`
* `conditionally_promoted`
* `deferred`
* `rejected`
* `unknown`

Every non-release draft needs explicit blockers. If a draft lacks rights, metadata review, cost approval, fallback coverage, accessible equivalents, or a concrete product use, the blocker stays in the manifest.

## Session 04 Handoff

Session 04 owns visual promotion tooling, optimization, metadata stripping, path checks, parity checks, and size budgets. A draft can move toward runtime only after that session reviews the manifest record, staged output, rights notes, cost estimate, and rejection criteria.

Until then, the durable output of Session 03 is the tracked evidence in this directory, not generated runtime media.


---

# 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/assets/generated/phase04/readme_phase04.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.