> 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_05_polish_public_demo_ui_states.md). # Session 05: Polish Public Demo UI States **Session ID**: `phase33-session05-polish-public-demo-ui-states` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Make the static hosted demo read as a frozen real product demo rather than a broken local runtime or generic fixture. *** ## Scope ### In Scope (MVP) * Update Trend Finder provenance labels, runtime-disabled states, route copy, and empty states as needed. * Update Trend Finder data provenance labels and empty states where needed. * Update Dream Review provenance labels, run-button behavior, and empty states for public demo mode. * Update Dream Review data provenance labels and empty states where needed. * Disable or relabel local-only collector, scheduler, source setup, Dream run, asset generation, upload, and mutation controls. * Disable or relabel local-only actions such as collector runs, source setup writes, Dream runs, scheduler actions, asset generation, and mutation controls. * Verify Trend Finder Trends, Engine Replay, Hidden Gems, Sources, Workbench, Watchlist, and Brief routes in public demo mode. * Ensure Brief, Sources, Watchlist, Hidden Gems, and Engine Replay explain frozen snapshot status without over-explaining implementation. * Verify the home dashboard presents Dream Review as a frozen real local snapshot when public demo data is present. * Verify route navigation and sidebar behavior in public demo mode. * Check `src/extensions/trend-finder/views/trends-view.tsx`, `engine-replay-view.tsx`, `hidden-gems-view.tsx`, `sources-view.tsx`, `watchlist-view.tsx`, and `brief-view.tsx` for labels that still imply live hosted work. * Check `src/components/home/dream-hero.tsx`, `src/components/dream-run-button.tsx`, and `src/lib/use-dream-run.ts` for public demo copy. * If Dream data is unexpectedly empty in public demo mode, say the frozen Dream snapshot is unavailable rather than telling hosted users to run local commands. * Keep browser-local controls honest without implying they update committed fixtures. * Keep Creator Lens drafts, Signal Workbench triage notes, visibility settings, and AI Rogue progress honest as browser-local surfaces that do not update committed fixtures. ### Out of Scope * Running local capture or fixture regeneration. * Adding new hosted mutation endpoints. * Reworking the application navigation outside public demo states. *** ## Prerequisites * [ ] Sessions 02 through 04 established the public fixture shape and labels. * [ ] Public demo mode remains controlled by `VITE_AI_OS_PUBLIC_DEMO`. * [ ] Empty Dream data in public demo mode is treated as frozen snapshot unavailable, not as a prompt to run local commands. * [ ] Public demo copy stays concise and product-facing. * [ ] Preferred labels are available where appropriate: `Frozen snapshot`, `Frozen real Trend Finder snapshot`, `Frozen real Dream Review snapshot`, `Reviewed public-source snapshot`, and `AI runtime disabled on hosted demo`. * [ ] Route copy must not claim live collection, live hosted AI analysis, hosted Dream runtime, source setup writes, scheduler actions, uploads, or committed fixture mutation. *** ## Deliverables 1. Updated Trend Finder public demo UI state and copy. 2. Updated Dream Review dashboard and run-control public demo state. 3. Focused tests or smoke assertions for public demo disabled-runtime behavior where existing harnesses support them. *** ## Success Criteria * [ ] Public users can tell the data is frozen while still evaluating realistic product output. * [ ] Public users understand the data is frozen and real enough for product evaluation. * [ ] Dream Review appears intentionally populated when snapshot data exists. * [ ] Dream Review looks intentionally populated in the demo rather than absent or broken. * [ ] No visible hosted control implies a collector, Dream job, scheduler, upload, source mutation, or asset bridge action will run. * [ ] No visible control implies a hosted job will run when the Pages demo is static. * [ ] Public demo routes do not request `/__*` bridge or mutation endpoints. * [ ] No route attempts to call `/__*` local bridge endpoints in public demo mode. --- # 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_05_polish_public_demo_ui_states.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.