> 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_39/session_07_real_content_expansion_path.md).

# Session 07: Real Content Expansion Path

**Session ID**: `phase39-session07-real-content-expansion-path` **Status**: Complete **Completed**: 2026-07-01 **Estimated Tasks**: 18 **Estimated Duration**: 2-4 hours

***

## Objective

Add real content one type at a time on top of the proven level authoring workflow.

***

## Scope

### In Scope (MVP)

* Add one standard enemy using existing behavior IDs and an existing audio family.
* Add the enemy frame set, save-schema parity when the kind can persist, and deterministic combat, spawn, effect, render-model, death reward, and save parse tests.
* Introduce the enemy through one level spec and one floor guarantee.
* Add a new terminal, objective, protocol, or status only after the enemy path is stable.
* Add a miniboss only after Session 06 generalizes boss handling.
* Add new music or ambience only after level encounter pacing is stable.

### Out of Scope

* Multiple new content tracks in one session.
* New boss content before the boss-spec migration is complete.
* New third-party transfers, remote loading, hosted writes, collectors, or analytics.

***

## Detailed Plan Notes

* This session starts only after a fourth reused-media floor proves the architecture and the boss-spec path is available.
* Exact content theme and pacing should be selected when this session starts, based on the fourth-floor playtest or deterministic test results.
* Add content one type at a time in this recommended order:
  1. Add one standard enemy using existing behavior IDs and an existing audio family.
  2. Add one enemy frame set and derive its asset validation from the enemy spec.
  3. Introduce that enemy through one level spec and one floor guarantee.
  4. Add a new terminal, objective, protocol, or status only after the enemy path is stable.
  5. Add a miniboss only after the boss-spec migration is complete.
  6. Add new music or ambience after the level's encounter pacing is stable.
* Content additions should be catalog work plus focused simulation, save, render, asset, and audio tests.
* Browser proof is required when visual presentation, controls, audio unlock, or route-visible UI changes.

***

## Prerequisites

* [x] Sessions 04-06 are complete.
* [x] Fourth-floor playtest or test evidence informs the exact content choice.

***

## Deliverables

1. A validated example of real content expansion through catalogs and level specs.
2. Focused simulation, save, render, asset, and audio tests for the new content.
3. Updated content evidence showing the workflow avoids broad runtime archaeology.

***

## Success Criteria

* [x] New content is added through catalog/spec work plus focused tests.
* [x] New persisted IDs have save-schema parity.
* [x] Browser proof exists when presentation, controls, audio unlock, or route-visible UI changes.
* [x] New levels no longer require broad runtime archaeology.


---

# 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_39/session_07_real_content_expansion_path.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.