> 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/docs/extensions/ai-rogue/progression-depth-notes.md).

# AI Rogue Progression Depth Notes

Session: `phase30-session08-progression-depth` Date: 2026-06-22

## Worker Decision

Worker simulation remains deferred.

Evidence:

* Pure simulation tests cover deterministic class, relic, resource, objective, achievement, enemy, pickup, hazard, win, loss, and terminal no-op behavior.
* Focused Playwright runtime tests passed for canvas paint, keyboard input, movement pixels, pause gating, save, load, win/loss completion, route exit cleanup, Loadout selection, refresh persistence, and scoped reset.
* No focused test showed input blockage, render starvation, or save/load jank that requires a worker protocol in this session.

Decision:

* Keep simulation on the existing route-scoped runtime path.
* Do not add a worker, message protocol, transferable snapshot format, or worker lifecycle ownership until profiling shows measurable main-thread pressure.

## Bounded Inputs

Progression derives only from browser-safe LiveData fields:

* `skills.active` labels and usage counts.
* `localAgents.skillSources` kind, label, status, and count.
* `modelUsage` model labels, messages, tokens, and priced spend fields.

The progression helper validates the input subset with Zod and emits safe fallback states when malformed or unavailable data is encountered. Labels are bounded and private-looking text is replaced before it can reach runtime, persistence, or UI output.

Persisted progression data is limited to:

* Class, relic, objective, resource, and achievement IDs.
* Bounded display labels.
* Resource values and caps.
* Run depth, turns, shard deltas, and timestamps.
* Short provenance labels and warnings.

## Content Follow-ups

Deferred to later sessions:

* Mobile and pointer-first layout polish.
* Audio and presentation polish.
* Additional generated art or content packs.
* Seed sharing.
* Worker simulation protocol.

Session 09 can use the current catalogs and HUD descriptors for polish without changing the LiveData derivation boundary.


---

# 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/docs/extensions/ai-rogue/progression-depth-notes.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.