> 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/sessions/phase33-session01-capture-local-demo-runs/tasks.md).

# Task Checklist

**Session ID**: `phase33-session01-capture-local-demo-runs` **Total Tasks**: 16 **Estimated Duration**: 3-4 hours **Created**: 2026-06-25

***

Legend: `[x]` completed; `[ ]` pending; `[P]` parallelizable; `[SNNMM]` session ref; `TNNN` task ID.

***

## Progress Summary

| Metric          | Value                                      |
| --------------- | ------------------------------------------ |
| Tasks Completed | 16 / 16                                    |
| Last Updated    | 2026-06-25 03:34 IDT                       |
| Current Status  | Implementation complete; ready for creview |

***

## Setup (3 tasks)

* [x] T001 \[S3301] Verify Phase 33 Session 01 prerequisites, current generated data timestamps, and local-only fixture boundary (`.spec_system/PRD/phase_33/session_01_capture_local_demo_runs.md`)
* [x] T002 \[S3301] Create the session implementation notes file with sections for commands, counts, provenance, manual review, blockers, and selected candidate status (`.spec_system/specs/phase33-session01-capture-local-demo-runs/implementation-notes.md`)
* [x] T003 \[S3301] Verify package scripts and runbook commands for Trend Finder, Dream, aggregate, and public demo separation (`package.json`)

***

## Foundation (4 tasks)

* [x] T004 \[S3301] Inspect the current Trend Finder branch counts, provenance states, and Engine Replay state without printing raw evidence bodies (`src/data/live-data.json`)
* [x] T005 \[S3301] Inspect the current Dream branch counts, generated timestamp, prescription shape, priorities, and safe impact-field coverage without printing private output bodies (`src/data/live-data.json`)
* [x] T006 \[S3301] Compare the current committed public snapshot gap for Dream, Trend Finder trace, collection health, narratives, events, and movement artifacts (`demo-website/public/demo/live-data.snapshot.json`)
* [x] T007 \[S3301] Record the source commit, capture time, generated timestamps, source-set notes, and initial local candidate decision (`.spec_system/specs/phase33-session01-capture-local-demo-runs/implementation-notes.md`)

***

## Implementation (5 tasks)

* [x] T008 \[S3301] Run or intentionally verify the Trend Finder local capture path with explicit extension enablement and timeout/failure-path notes (`docs/runbooks/trend-finder-collector-logging.md`)
* [x] T009 \[S3301] Run or intentionally verify the Dream Review local capture path with explicit Dream activation and skipped/degraded/failure-path notes (`docs/runbooks/ai-os-dream.md`)
* [x] T010 \[S3301] Refresh or intentionally verify aggregate-generated `src/data/live-data.json` after selected local runs, preserving generated private data as uncommitted local input (`scripts/aggregate.ts`)
* [x] T011 \[S3301] Manually review top Trend Finder topics, evidence links, creator angles, source provenance, and analysis provenance for demo quality and public-safety suitability (`src/data/live-data.json`)
* [x] T012 \[S3301] Manually review Dream prescriptions, next actions, priorities, tags, summaries, and impact fields for usefulness, clarity, and public-safety suitability (`src/data/live-data.json`)

***

## Testing (4 tasks)

* [x] T013 \[S3301] Verify sanitized Engine Replay trace availability and record release blocker status if trace state is missing, unsanitized, or empty (`src/data/live-data.json`)
* [x] T014 \[S3301] Verify local capture notes do not include credential values, token-shaped strings, raw prompts, provider bodies, source dumps, scheduler logs, or private local paths (`.spec_system/specs/phase33-session01-capture-local-demo-runs/implementation-notes.md`)
* [x] T015 \[S3301] Confirm public demo build scripts still consume committed fixtures only and do not invoke local capture or snapshot authoring during Pages build (`package.json`)
* [x] T016 \[S3301] Validate ASCII and LF requirements for the session artifacts (`.spec_system/specs/phase33-session01-capture-local-demo-runs`)

***

## Completion Checklist

* [x] All tasks marked `[x]`
* [x] All tests and checks passing
* [x] All files ASCII-encoded with LF line endings
* [x] implementation-notes.md updated
* [x] Ready for `creview` to continue the implement -> creview -> validate sequence

***

## Next Steps

Run the `creview` workflow step.


---

# 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/sessions/phase33-session01-capture-local-demo-runs/tasks.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.
