> 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/phase27-session05-velocity-dynamics-upgrade/tasks.md). # Task Checklist **Session ID**: `phase27-session05-velocity-dynamics-upgrade` **Total Tasks**: 20 **Estimated Duration**: 3-4 hours **Created**: 2026-06-12 *** ## Legend * `[x]` = Completed * `[ ]` = Pending * `[P]` = Parallelizable (can run with other \[P] tasks) * `[SNNMM]` = Session reference (NN=phase number, MM=session number) * `TNNN` = Task ID *** ## Progress Summary | Category | Total | Done | Remaining | | -------------- | ------ | ------ | --------- | | Setup | 2 | 2 | 0 | | Foundation | 6 | 6 | 0 | | Implementation | 8 | 8 | 0 | | Testing | 4 | 4 | 0 | | **Total** | **20** | **20** | **0** | *** ## Setup (2 tasks) Initial verification and source orientation. * [x] T001 \[S2705] Verify analyzer state, Session 04 completion, and Session 05 PRD scope (`.spec_system/specs/phase27-session05-velocity-dynamics-upgrade/implementation-notes.md`) * [x] T002 \[S2705] Inspect scoring, historical context, trend-series, collector, schema, score-breakdown, and Engine Replay baselines (`.spec_system/specs/phase27-session05-velocity-dynamics-upgrade/implementation-notes.md`) *** ## Foundation (6 tasks) Core contracts and pure dynamics structures. * [x] T003 \[S2705] \[P] Create pure velocity dynamics helper with acceleration, significance, burst, caps, and explicit unavailable states (`scripts/lib/ai-runtime/velocity-dynamics.ts`) * [x] T004 \[S2705] Extend historical topic context with bounded evidence-count and delta history from dated snapshots with deterministic ordering (`scripts/lib/ai-runtime/historical-context.ts`) * [x] T005 \[S2705] Extend scoring input and topic output types for velocity dynamics and historical sparkline context with types matching declared contract; exhaustive enum handling (`scripts/lib/ai-runtime/scoring.ts`) * [x] T006 \[S2705] Add bounded velocity dynamics schemas and additive defaults with schema-validated input and explicit error mapping (`src/extensions/trend-finder/schema.ts`) * [x] T007 \[S2705] Add velocity dynamics view-model labels, tones, descriptions, and accessibility text with exhaustive state handling (`src/extensions/trend-finder/view-model.ts`) * [x] T008 \[S2705] \[P] Add available and unavailable velocity dynamics fixture states for browser and UI coverage (`src/extensions/trend-finder/fixtures.ts`) *** ## Implementation (8 tasks) Runtime wiring, score support, and UI rendering. * [x] T009 \[S2705] Derive acceleration from consecutive evidence-count deltas in scoring with explicit low-sample and missing-history states (`scripts/lib/ai-runtime/scoring.ts`) * [x] T010 \[S2705] Derive significance against historical delta variance in scoring with minimum-sample and zero-variance guards (`scripts/lib/ai-runtime/scoring.ts`) * [x] T011 \[S2705] Derive burst from 14-day series and apply capped momentum support with idempotency protection for repeated scoring calls (`scripts/lib/ai-runtime/scoring.ts`) * [x] T012 \[S2705] Pass historical sparkline context into scoring and log aggregate dynamics counters without private paths (`scripts/extensions/trend-finder/collector.ts`) * [x] T013 \[S2705] Preserve sanitized Engine Replay scoring labels and counters for velocity dynamics and capped burst support (`scripts/extensions/trend-finder/engine-trace.ts`) * [x] T014 \[S2705] Render acceleration, significance, and burst rows in score breakdown with explicit unavailable, empty, and error states (`src/extensions/trend-finder/components/score-breakdown.tsx`) * [x] T015 \[S2705] Pass topic velocity dynamics into trend card score breakdown with platform-appropriate accessibility labels, focus management, and input support (`src/extensions/trend-finder/components/trend-card.tsx`) * [x] T016 \[S2705] Update Engine Replay scoring proof view model to describe capped burst support and unavailable dynamics context (`src/extensions/trend-finder/engine-replay-model.ts`) *** ## Testing (4 tasks) Verification and quality assurance. * [x] T017 \[S2705] \[P] Write hand-computed helper tests for acceleration, significance, burst, caps, and unavailable states (`scripts/lib/ai-runtime/__tests__/velocity-dynamics.test.ts`) * [x] T018 \[S2705] Extend historical-context and scoring regression tests for low-sample, new-topic, missing-history, and capped burst behavior (`scripts/lib/ai-runtime/__tests__/scoring.test.ts`) * [x] T019 \[S2705] \[P] Add schema, view-model, component, and Engine Replay tests for dynamics defaults, labels, rows, and legacy payloads (`src/lib/__tests__/trend-finder-schema.test.ts`) * [x] T020 \[S2705] Run focused validation, ASCII checks, and record implementation results (`.spec_system/specs/phase27-session05-velocity-dynamics-upgrade/implementation-notes.md`) *** ## Completion Checklist Before marking session complete: * [x] All tasks marked `[x]` * [x] All tests passing * [x] All files ASCII-encoded * [x] `implementation-notes.md` updated * [x] Ready for the validate workflow step *** ## Next Steps Run the validate workflow step to verify session completeness. --- # 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/phase27-session05-velocity-dynamics-upgrade/tasks.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.