> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase08-session07-legacy-evidence-decommission-and-media-release-gate/tasks.md). # Task Checklist **Session ID**: `phase08-session07-legacy-evidence-decommission-and-media-release-gate` **Total Tasks**: 21 **Estimated Duration**: 3-4 hours **Created**: 2026-05-31 *** ## 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 | 9 | 9 | 0 | | Testing | 4 | 4 | 0 | | **Total** | **21** | **21** | **0** | *** ## Setup (3 tasks) Initial configuration and environment preparation. ### Cross-cutting * [x] T001 \[S0807] Verify analyzer state, completed Sessions 01-06 prerequisites, Phase 08 S0807 routing, and cross-cutting package context before implementation (`.spec_system/PRD/phase_08/session_07_legacy_evidence_decommission_and_media_release_gate.md`) * [x] T002 \[S0807] Review the decommission matrix, release risk matrix, media gate docs, legacy consolidation docs, public-demo validation docs, and current candidate paths without copying raw sensitive evidence (`.spec_system/PRD/phase_08/decommission_approval_matrix.md`) * [x] T003 \[S0807] Create implementation notes with the cleanup guardrails, no-deletion-before-preservation rule, unavailable ignored-path handling, and no sensitive historical content copying (`.spec_system/specs/phase08-session07-legacy-evidence-decommission-and-media-release-gate/implementation-notes.md`) *** ## Foundation (5 tasks) Core structures and base implementations. ### .spec\_system * [x] T004 \[S0807] Create the Session 07 legacy decommission and media release gate action record with final disposition columns, stable-doc replacement map, gate command slots, rollback notes, and residual-risk handoff (`.spec_system/PRD/phase_08/legacy_decommission_media_release_gate.md`) * [x] T005 \[S0807] Update the decommission approval matrix status from candidate-only baseline to Session 07 final-review tracking with explicit retain, archive, reduce, delete, blocked, or unavailable outcomes (`.spec_system/PRD/phase_08/decommission_approval_matrix.md`) * [x] T006 \[S0807] Update Phase 08 routing and risk artifacts for S0807 media/decommission ownership, P08-R016 through P08-R018 evidence expectations, and Session 08 handoff (`.spec_system/PRD/phase_08/phase08_requirement_routing_matrix.md`) ### docs * [x] T007 \[S0807] \[P] Map historical findings, reports, copied bundles, sensitive evidence, and `docs/PROGRESS.md` retained value to stable docs with blocked-cleanup gaps called out (`docs/legacy-consolidation.md`) * [x] T008 \[S0807] \[P] Map approved, conditional, planned, generated, draft, unknown, and quarantined media records to release blockers and gate evidence without broad media promotion (`docs/media-assets.md`) *** ## Implementation (9 tasks) Main feature implementation. ### .spec\_system * [x] T009 \[S0807] Finalize candidate-by-candidate dispositions with stable replacement references, owner, affected paths, evidence source, rollback note, and fail-closed blocked status where preservation is incomplete (`.spec_system/PRD/phase_08/legacy_decommission_media_release_gate.md`) * [x] T010 \[S0807] Update P08-RISK-009, P08-RISK-010, and P08-RISK-011 residual wording for media readiness, legacy decommission, and sensitive evidence output based on the Session 07 action record (`.spec_system/PRD/phase_08/phase08_release_risk_matrix.md`) ### docs * [x] T011 \[S0807] Preserve or refresh API, event, hook, architecture, package-boundary, and unsupported-route conclusions before reducing historical findings (`docs/api/event-api-hook-contracts.md`) * [x] T012 \[S0807] Update release guide decommission gates, media gate commands, approved cleanup rules, no-overclaim wording, and Session 08 handoff (`docs/release.md`) * [x] T013 \[S0807] Update privacy, hosted-service, and environment docs for sensitive-output preservation, reserved credential handling, hosted no-claim wording, and historical evidence reduction outcomes (`docs/privacy-and-security.md`) * [x] T014 \[S0807] Update public-demo validation and web runtime docs for media/cache gate outcomes, conditional media blockers, service-worker cache decisions, and no quarantined-media promotion (`public-demo/docs_public-demo/validation.md`) * [x] T015 \[S0807] Update top-level and web package README guidance if final retained or removed evidence changes release-facing status, media limitations, or legacy evidence references (`README.md`) ### legacy evidence * [x] T016 \[S0807] Apply approved retain, archive, reduce, delete, blocked, or unavailable decisions for historical findings and reports only after stable replacements and gate notes exist (`EXAMPLES/findings/`) * [x] T017 \[S0807] Apply approved retain, archive, reduce, delete, blocked, or unavailable decisions for copied first-pass artifacts, ignored media intake, generated drafts, sensitive service-discovery evidence, and `docs/PROGRESS.md` only after stable replacements and gate notes exist (`EXAMPLES/1st-pass-artifacts/`) *** ## Testing (4 tasks) Verification and quality assurance. ### Media and release gates * [x] T018 \[S0807] Run media release gates for catalog, visual promotion, public-demo media, draft manifest, battlefield assets, cache policy, and sensitive-output checks, then record exact commands and outcomes (`.spec_system/PRD/phase_08/legacy_decommission_media_release_gate.md`) * [x] T019 \[S0807] Run secret scan, docs no-overclaim review, whitespace, ASCII, LF, and `git diff --check` validation over changed docs, PRD artifacts, public-demo cache files, and cleanup paths (`.spec_system/specs/phase08-session07-legacy-evidence-decommission-and-media-release-gate/implementation-notes.md`) * [x] T020 \[S0807] Run focused tests or focused Biome checks for any changed scripts, tests, media config, public-demo cache logic, package docs, or runtime paths and record blockers with exact command scope (`.spec_system/specs/phase08-session07-legacy-evidence-decommission-and-media-release-gate/implementation-notes.md`) * [x] T021 \[S0807] Record final command outcomes, disposition summary, residual blockers, retained unavailable paths, cleanup actions, rollback notes, and Session 08 handoff in implementation notes and the action record (`.spec_system/specs/phase08-session07-legacy-evidence-decommission-and-media-release-gate/implementation-notes.md`) *** ## Completion Checklist Before marking session complete: * [x] All tasks marked `[x]` * [x] All tests passing or blockers recorded with exact commands * [x] All files ASCII-encoded * [x] implementation-notes.md updated * [x] Ready for the validate workflow step *** ## Next Steps Run the implement workflow step to begin AI-led implementation. --- # 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://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase08-session07-legacy-evidence-decommission-and-media-release-gate/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.