> 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_29/session_11_industry_events_rollup.md).

# Session 11: Industry-Events Rollup

**Session ID**: `phase29-session11-industry-events-rollup` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours

***

## Objective

Add a "what happened in the industry this cycle" lens using current news adapters only. Maps comparison item 2.2, industry-news extraction in a lighter current-source version.

***

## Scope

### In Scope (MVP)

* Add a deterministic-plus-AI `industry-events` rollup over `rss-ai-news` and `google-ai-news` evidence.
* Cluster news evidence into bounded event rows.
* Require at least two independent publishers, reusing Session 04 corroboration.
* Deterministic fallback clusters on shared entity/title tokens.
* Add schema defaults, surface bounded rows with cited evidence IDs, and confirm payload safety.

### Out of Scope

* Podcast transcripts or cross-show references (Sessions 16-17).
* Adding any new source beyond existing news adapters.

***

## Prerequisites

* [ ] Session 04 complete (reuses the corroboration / two-publisher logic).

***

## Deliverables

1. `industry-events` rollup over existing news adapters with bounded event rows.
2. Two-independent-publisher requirement reusing corroboration.
3. Deterministic shared-token fallback clustering.
4. Unit tests for single-publisher suppression and two-publisher publication.

***

## Success Criteria

* [ ] Single-publisher event fixtures are suppressed.
* [ ] Events with two independent publishers publish bounded rows with cited evidence IDs.
* [ ] Deterministic fallback clusters without the AI runtime.
* [ ] Payload budget and privacy scans remain green.

***

## Key Files

* `scripts/extensions/trend-finder/demand-clusters.ts`
* `scripts/extensions/trend-finder/sources/rss-adapter.ts`
* `scripts/extensions/trend-finder/sources/google-news-adapter.ts`
* `scripts/lib/ai-runtime/trend-analyst.ts`
* `src/extensions/trend-finder/schema.ts`
* `src/extensions/trend-finder/view-model.ts`
* `scripts/extensions/trend-finder/static-brief-renderer.ts`

***

## Comparison Notes (folded from comparison plan)

**Effort:** Medium. **Boundary risk:** Low-Medium. **Depends on Session 04** (reuses the corroboration / two-publisher logic).

**2.2 Industry-news extraction cross-referenced to discourse.** TrendingAI extracts substantive AI-industry events from transcripts, de-dups them against confirmed features, and keeps events covered by at least two shows. Trend Finder can adopt the useful part without transcripts: cluster `rss-ai-news` and `google-ai-news` evidence into `industry-events`, require at least two independent publishers, and publish bounded event rows. Deterministic fallback clusters on shared entity/title tokens; no podcast transcripts or cross-show references are required.

**TrendingAI source pointers.** `src/industry-news.ts`, `prompts/industry-news.md`, `prompts/industry-news-merger.md`.


---

# 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_29/session_11_industry_events_rollup.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.