> 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_13_static_brief_archival_and_richness.md).

# Session 13: Static Brief Archival And Richness

**Session ID**: `phase29-session13-static-brief-archival-and-richness` **Status**: Complete **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours

***

## Objective

Make the human-readable Brief more useful across runs without changing collection posture. Maps the Tier 3 run-numbering and single-artifact-richness ideas.

***

## Scope

### In Scope (MVP)

* Add optional run-numbered Brief export and a `latest` pointer so operators can diff human-readable Briefs across runs.
* Preserve current export behavior when archival is not enabled.
* Increase static Brief density using already-published fields from Sessions 02, 03, and 05.
* Keep the deliberate media-embed gap: do not inline social embeds, thumbnails, transcripts, or unreviewed media.

### Out of Scope

* Any media embed or unreviewed asset inlining.
* Changing snapshot/data history (snapshots already preserve data history).

***

## Prerequisites

* [x] Sessions 03 and 05 complete (reception and rationale fields available).

***

## Deliverables

1. Optional run-numbered Brief export plus a `latest` pointer.
2. Backwards-compatible default export when archival is off.
3. Denser static Brief using published derived fields, media-embed gap intact.
4. Unit/e2e tests for archival, default compatibility, and privacy cleanliness.

***

## Success Criteria

* [x] Run-numbered output and `latest` pointer work when enabled.
* [x] Default export remains compatible when archival is disabled.
* [x] Static Brief remains privacy-clean with no media embeds.
* [x] Payload budget and privacy scans remain green.

***

## Key Files

* `scripts/extensions/trend-finder/static-brief-export.ts`
* `scripts/extensions/trend-finder/static-brief-renderer.ts`
* `scripts/extensions/trend-finder/static-brief-qa.ts`
* `scripts/extensions/trend-finder/__tests__/static-brief-export.test.ts`
* `scripts/extensions/trend-finder/__tests__/static-brief-renderer.test.ts`
* `tests/e2e/trend-finder-static-brief.spec.ts`

***

## Comparison Notes (folded from comparison plan)

**Effort:** Low-Medium. **Boundary risk:** None. Tier 3 polish. **Depends on Sessions 03 and 05** (reception and rationale fields enrich Brief density).

**Run numbering and archival.** In TrendingAI every run creates a numbered file and `latest.html` points to the newest report. Trend Finder adoption: add an optional run-numbered static Brief export and a `latest` pointer. Snapshots already preserve data history; this is for the human-readable artifact.

**Single self-contained artifact richness.** TrendingAI ships one HTML report with inline embeds. Trend Finder adoption: keep the static Brief information-dense within compliance using already-published fields, but do not inline social embeds, thumbnails, transcripts, or unreviewed media.


---

# 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_13_static_brief_archival_and_richness.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.