> 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/phase29-session16-podcast-compliance-package/tasks.md).

# Task Checklist

**Session ID**: `phase29-session16-podcast-compliance-package` **Total Tasks**: 18 **Estimated Duration**: 3-4 hours **Created**: 2026-06-21

***

## 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          | 3      | 3      | 0         |
| Foundation     | 5      | 5      | 0         |
| Implementation | 6      | 6      | 0         |
| Testing        | 4      | 4      | 0         |
| **Total**      | **18** | **18** | **0**     |

***

## Setup (3 tasks)

Initial configuration and environment preparation.

* [x] T001 \[S2916] Verify existing source compliance, media policy, and Phase 29 podcast stubs are available (`docs/sources/source-compliance-youtube.md`)
* [x] T002 \[S2916] Inspect source onboarding, Apify, and Trend Finder source docs for current source-gate conventions (`docs/sources/apify-source-onboarding.md`)
* [x] T003 \[S2916] Record decision inputs, reviewed docs, and validation commands for the compliance package (`.spec_system/specs/phase29-session16-podcast-compliance-package/implementation-notes.md`)

***

## Foundation (5 tasks)

Core structures and base implementations.

* [x] T004 \[S2916] \[P] Create the podcast/audio source compliance document skeleton using existing source-doc sections (`docs/sources/source-compliance-podcasts.md`)
* [x] T005 \[S2916] Add source/provider candidate review matrix with terms, authentication, rate, quota, and spend considerations (`docs/sources/source-compliance-podcasts.md`)
* [x] T006 \[S2916] Classify transcript bodies, speaker names, comments, thumbnails, media URLs, raw audio/video, episode URLs, show names, and summaries as allowed or blocked (`docs/sources/source-compliance-podcasts.md`)
* [x] T007 \[S2916] Define retention, deletion, private cache, attribution, and spend-label policy for any approved podcast path (`docs/sources/source-compliance-podcasts.md`)
* [x] T008 \[S2916] Define explicit approve/defer/reject criteria and the exact Session 17 handoff rules (`docs/sources/source-compliance-podcasts.md`)

***

## Implementation (6 tasks)

Main feature implementation.

* [x] T009 \[S2916] Record the final approve/defer/reject decision with rationale and unresolved follow-up conditions (`docs/sources/source-compliance-podcasts.md`)
* [x] T010 \[S2916] Update Trend Finder source documentation with podcast status while avoiding implemented-behavior claims (`docs/extensions/trend-finder-sources.md`)
* [x] T011 \[S2916] Update media policy only if the decision approves audio, transcript, thumbnail, or media handling; otherwise document no-change rationale (`docs/media-policy.md`)
* [x] T012 \[S2916] Update source-onboarding provider language only if a provider path is approved; otherwise keep provider onboarding deferred (`docs/sources/apify-source-onboarding.md`)
* [x] T013 \[S2916] Update Phase 29 Session 16 and Session 17 stubs to reflect the decision and blocked/unblocked/deferred status (`.spec_system/PRD/phase_29/session_17_podcast_themes_enrichment.md`)
* [x] T014 \[S2916] Update Phase 29 tracker and folded comparison notes without marking planned podcast behavior as implemented (`.spec_system/PRD/phase_29/PRD_phase_29.md`)

***

## Testing (4 tasks)

Verification and quality assurance.

* [x] T015 \[S2916] \[P] Run focused Markdown formatting check for all touched documentation (`docs/sources/source-compliance-podcasts.md`)
* [x] T016 \[S2916] \[P] Scan touched docs for prohibited raw transcript, media, credential, private-cache, and planned-as-implemented claims (`docs/sources/source-compliance-podcasts.md`)
* [x] T017 \[S2916] Verify Session 17 handoff matches the decision and no collector, adapter, dependency, or source declaration was added (`.spec_system/PRD/phase_29/session_17_podcast_themes_enrichment.md`)
* [x] T018 \[S2916] Validate ASCII encoding and record validation evidence for docs-only compliance closeout (`.spec_system/specs/phase29-session16-podcast-compliance-package/validation.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/phase29-session16-podcast-compliance-package/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.
