> 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_33/session_02_freeze_public_fixtures.md). # Session 02: Freeze Public Fixtures **Session ID**: `phase33-session02-freeze-public-fixtures` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Convert the reviewed local product output into deterministic committed public demo fixtures. *** ## Scope ### In Scope (MVP) * Run `bun run demo:snapshot` against the selected `src/data/live-data.json`. * Run `bun run demo:snapshot --dry-run` against the selected local input before writing final fixtures. * Review `demo-website/public/demo/live-data.snapshot.json` for populated Trend Finder and Dream Review branches. * Review the exported Trend Finder branch in `demo-website/public/demo/live-data.snapshot.json`. * Review the exported `dream` branch in `demo-website/public/demo/live-data.snapshot.json`. * Compare input and output counts for Trend Finder topics, evidence, sources, watchlist rows, predictions, retros, story-log rows, trace data, and advanced artifacts. * Compare input and output counts for Trend Finder topics, evidence, sources, watchlist, predictions, retros, story log, engine trace decisions, engine trace artifacts, demand clusters, industry events, run narratives, movement analyses, and hidden gems. * Compare input and output counts for Dream prescriptions, evidence lines, impact fields, tags, and generated timestamps. * Compare input and output counts for Dream prescriptions, evidence lines, impact fields, tags, and generated timestamp. * Update `demo-website/public/demo/snapshot-metadata.json` for frozen real demo data after redaction. * Update snapshot metadata so it clearly records that Trend Finder and Dream Review data are frozen real demo captures after redaction. * Keep the app contract centered on `live-data.snapshot.json`. * Use the existing `demo-website/snapshot-manifest.json` as the review manifest and add Dream field policy plus count summaries there. * Keep Cloudflare Pages consumption centered on committed static fixtures only. ### Out of Scope * Changing projection policy beyond minimal metadata alignment. * Running Cloudflare Pages deployment. * Adding non-static hosted runtime behavior. *** ## Prerequisites * [ ] Session 01 produced and reviewed the selected local input. * [ ] `bun run demo:snapshot --dry-run` passes before final fixture writes. * [ ] Public-demo fixture review uses committed static fixture paths. * [ ] Fixture regeneration remains an explicit local operator action. * [ ] Cloudflare Pages builds consume committed fixtures only and must not run `demo:snapshot`. * [ ] If reviewers need side-by-side diffs, produce them as temporary local review output, not as new public fixture files. * [ ] Do not create separate committed Trend Finder-only or Dream-only manifests for this pass. *** ## Deliverables 1. Updated `demo-website/public/demo/live-data.snapshot.json`. 2. Updated `demo-website/public/demo/snapshot-metadata.json`. 3. Optional local-only count-delta notes for reviewer comparison. *** ## Success Criteria * [ ] Public snapshot includes realistic Trend Finder topics, evidence, source health, watchlist, Brief support, and Engine Replay state. * [ ] Public snapshot includes non-null Dream Review prescriptions. * [ ] Frozen-demo and runtime-disabled labels are present and not misleading. * [ ] Rebuilding the Pages site does not recollect, rerun, or mutate demo data. * [ ] The committed Pages fixture includes real Trend Finder topics and evidence, not blank or generic placeholder topics. * [ ] The committed Pages fixture includes real Dream Review prescriptions, not `null`, blank, or generic placeholder prescriptions. * [ ] Exported Trend Finder `engineTrace.state` is not `missing` when the selected input run has a sanitized trace. * [ ] Exported Trend Finder labels say frozen/public/demo, while runtime labels say hosted runtime disabled. * [ ] Snapshot metadata identifies the data as a frozen public demo snapshot. * [ ] The fixture is deterministic: rebuilding the Pages site does not refresh or mutate the data. --- # 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_33/session_02_freeze_public_fixtures.md?ask=&goal= ``` `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.