> 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/docs/adr/0004-quarantined-media-intake.md).

# 0004. Quarantined Media Intake

**Status:** Accepted **Date:** 2026-05-28 **Amended:** 2026-05-28

## Context

The repository has tracked showcase/runtime assets and a gitignored `EXAMPLES/` directory containing legacy media and copied build output. The copied media does not currently have a reliable provenance, license, attribution, optimization, or size manifest.

## Options Considered

1. Keep `EXAMPLES/` quarantined as reference-only material and generate owned replacements from written standards and gap briefs.
2. Keep `EXAMPLES/` quarantined until manifest-driven direct promotion is complete.
3. Promote useful-looking assets directly into runtime paths.
4. Delete all legacy media before inventory.

## Decision

Keep `EXAMPLES/` quarantined and reference-only. Inventory it by path, hash, reference value, inferred standard, implementation gap, and disposition, but do not import, copy, transform, use as a direct generation input, or ship files from it. Product media should be owned or generated from written briefs, then tracked through manifests or typed catalogs that record provider, prompt/brief, rights, attribution, optimization, metadata, size, and product use.

## Consequences

* Current tracked assets remain intentional and limited.
* Media planning uses `EXAMPLES/` to derive standards and implementation gaps, not product source files.
* Unknown provider rights, unclear attribution, oversized raw assets, and unstripped metadata remain release blockers.
* Runtime code should not import directly from `EXAMPLES/`.
* The default media toolchain is the npm-pinned and host-verified baseline checked by `npm run media:check`.


---

# 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/docs/adr/0004-quarantined-media-intake.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.