> 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_27/session_12_documentation_validation_and_release.md). # Session 12: Documentation Validation And Release **Session ID**: `phase27-session12-documentation-validation-and-release` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours *** ## Objective Update the Trend Finder manuals for every Phase 27 behavior change, run the full validation and security review, record the deferred source candidates and non-goals as durable decisions, and delete `docs/ongoing-projects/alpha-radar.md` after confirming complete coverage. *** ## Context This phase folded the complete Alpha Radar improvement map into the phase PRD and session stubs (the P23 "backlog migration into phase PRD" pattern: source anchors plus explicit no-action decisions enable safe file deletion without losing audit history). This session closes the loop: documentation matches shipped behavior, the deferred items live in durable docs, and the ongoing-projects file is removed. Durable decisions to carry into docs (from `PRD_phase_27.md`): * **Deferred source candidates** (compliance-first): Semantic Scholar citations, Bluesky mentions, Replicate run deltas, newsletter feeds as reviewed `rss-ai-news` targets, X/Twitter (non-goal: no compliant path), Digg (skip: low marginal value). See the "Deferred: Source Coverage Candidates" table in `PRD_phase_27.md`. * **Non-goals**: `tbts` / `peak_estimate_days` point estimates (invented precision), hotlinked thumbnails (compliance-gated; asset manifest/bridge path exists when approved), landing-page media, single-creator hardcoding. * **Do-not-regress areas**: baseline math, provenance, validation, compliance, spend accounting, Engine Replay, retro rigor (see the "Where Trend Finder Is Already Ahead" table in `PRD_phase_27.md`). *** ## Scope ### In Scope (MVP) * Update the manuals that Engine Replay Reference mode renders (committed Markdown stays the source of truth): * `docs/extensions/trend-finder-scoring.md` (saturation, gem score, consensus ratio, builder signal, risk flags, acceleration, significance, burst, caps) * `docs/extensions/trend-finder-history.md` (daily series, dated predictions, target-date retros, Story Log, calibration metrics) * `docs/extensions/trend-finder-ui-surfaces.md` (movement-grouped Brief, today's pick, data-driven radar, watching state, outlier preset, sparklines, convergence timeline, Story Log, demand panel, themes) * `docs/extensions/trend-finder-creator-lens.md` (competitor list field) * `docs/extensions/trend-finder-pipeline.md` (new pipeline stages, state locations, implementation map rows) * `docs/extensions/trend-finder-runtime-and-provenance.md` (new analyst fields, fallback behavior, derived-label provenance) * `docs/extensions/trend-finder-sources.md` (deferred candidates pointer, HF delta behavior) * `docs/extensions/trend-finder-concepts.md` (new core objects: lifecycle stage, convergence, demand cluster, theme, watching state) * `docs/extensions/README_docs-extensions.md` (current behavior list) * Reference-doc registry check (`src/extensions/trend-finder/reference-docs.ts`) so Reference mode renders updated manuals * Full validation: `bun run typecheck`, `bun run typecheck:scripts`, `bun run test`, `bun run format:check`, `bun run test:e2e`, plus the focused Trend Finder runtime certification set from `docs/extensions/README_docs-extensions.md` * Static Brief export validation including its privacy scan over new sections * Security review of changed bridge surfaces (lens bridge) and new schema branches; update `.spec_system/SECURITY-COMPLIANCE.md` * Payload budget check against the shared 1 MB extension limit with all new bounded arrays populated * Delete `docs/ongoing-projects/alpha-radar.md` after a coverage diff confirms every mapping item lives in this phase's artifacts * Carryforward notes for `.spec_system/CONSIDERATIONS.md` ### Out of Scope * New features or scope additions discovered during validation (file as follow-ups) * The deferred source adapters (future phase) *** ## Prerequisites * [ ] Sessions 01-11 completed and individually validated *** ## Deliverables 1. Updated Trend Finder manuals matching shipped behavior 2. Passing full validation suite and e2e runs 3. Security review notes and updated compliance ledger 4. Durable record of deferred candidates and non-goals in docs 5. Deletion of `docs/ongoing-projects/alpha-radar.md` *** ## Success Criteria * [ ] Docs document actual behavior only (no planned-feature drift) * [ ] Engine Replay Reference mode renders the updated manuals * [ ] Full suite, e2e, format, and typechecks pass * [ ] Security review finds no browser-safe boundary regressions * [ ] `docs/ongoing-projects/alpha-radar.md` is deleted with zero information loss (verified against phase artifacts) --- # 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_27/session_12_documentation_validation_and_release.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.