> 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-session01-release-requirements-and-risk-baseline/tasks.md). # Task Checklist **Session ID**: `phase08-session01-release-requirements-and-risk-baseline` **Total Tasks**: 19 **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 | 7 | 7 | 0 | | Testing | 4 | 4 | 0 | | **Total** | **19** | **19** | **0** | *** ## Setup (3 tasks) Initial configuration and environment preparation. ### Cross-cutting * [x] T001 \[S0801] Verify analyzer state, Phase 08 Session 01 prerequisites, Phase 07 closeout availability, and active current-session context (`.spec_system/PRD/phase_08/session_01_release_requirements_and_risk_baseline.md`) * [x] T002 \[S0801] Review PRD, UX PRD, Phase 08 stubs, considerations, security posture, release docs, deployment docs, hosted-service docs, privacy docs, architecture docs, environment docs, legacy docs, and package boundaries for release baseline inputs (`.spec_system/PRD/phase_08/release_requirements_risk_baseline.md`) * [x] T003 \[S0801] Create the release baseline, requirement routing matrix, release risk matrix, and decommission approval matrix deliverable files (`.spec_system/PRD/phase_08/release_requirements_risk_baseline.md`) *** ## Foundation (5 tasks) Core structures and base implementations. ### Cross-cutting release baseline * [x] T004 \[S0801] \[P] Inventory release claim surfaces for local-first operation, optional Worker federation, hosted identity, hosted storage, analytics, public replay, push, remote access, trusted erasure, certification, production-hosted validation, media readiness, and legacy deletion (`.spec_system/PRD/phase_08/release_requirements_risk_baseline.md`) * [x] T005 \[S0801] \[P] Route Sessions 02-08 requirements, prerequisites, evidence owners, and explicit later deferrals from Phase 08 stubs and PRD requirements (`.spec_system/PRD/phase_08/phase08_requirement_routing_matrix.md`) * [x] T006 \[S0801] \[P] Map open hosted identity, trusted erasure, production-hosted validation, media readiness, and decommission risks to owners, evidence, closeout criteria, and residual-risk wording (`.spec_system/PRD/phase_08/phase08_release_risk_matrix.md`) * [x] T007 \[S0801] \[P] Inventory decommission candidates, retained value, required replacement docs, disposition options, and blocked deletion conditions for legacy evidence and media intake (`.spec_system/PRD/phase_08/decommission_approval_matrix.md`) * [x] T008 \[S0801] Define release claim gate vocabulary, evidence standards, no-overclaim rules, and sanitized-output requirements for Phase 08 artifacts (`.spec_system/PRD/phase_08/release_requirements_risk_baseline.md`) *** ## Implementation (7 tasks) Main feature implementation. ### Spec system artifacts * [x] T009 \[S0801] Create the Phase 08 release requirements and risk baseline with source evidence, local-first constraints, claim gates, evidence standards, and Phase 08 ownership (`.spec_system/PRD/phase_08/release_requirements_risk_baseline.md`) * [x] T010 \[S0801] Create the Phase 08 requirement-to-session routing matrix for erasure, hosted identity, production validation, mobile/accessibility evidence, media gates, decommission, docs, and final closeout (`.spec_system/PRD/phase_08/phase08_requirement_routing_matrix.md`) * [x] T011 \[S0801] Create the Phase 08 release risk matrix for open security findings, release blockers, owner sessions, required evidence, closeout criteria, and residual-risk wording (`.spec_system/PRD/phase_08/phase08_release_risk_matrix.md`) * [x] T012 \[S0801] Create the initial decommission approval matrix for `EXAMPLES/`, findings, reports, ignored media intake, copied historical bundles, and `docs/PROGRESS.md` without approving deletion (`.spec_system/PRD/phase_08/decommission_approval_matrix.md`) * [x] T013 \[S0801] Update master PRD, UX PRD, and Phase 08 PRD links and wording for Session 01 artifacts, routing ownership, claim gates, and no-overclaim Phase 08 boundaries if stale (`.spec_system/PRD/PRD.md`, `.spec_system/PRD/PRD_UX.md`, `.spec_system/PRD/phase_08/PRD_phase_08.md`) ### Stable docs * [x] T014 \[S0801] Update release, deployment, hosted-service, privacy/security, architecture, environment, and legacy docs with Phase 08 claim gates, evidence requirements, risk ownership, and candidate-only decommission wording if stale (`docs/release.md`, `docs/deployment.md`, `docs/hosted-services.md`, `docs/privacy-and-security.md`, `docs/ARCHITECTURE.md`, `docs/environments.md`, `docs/legacy-consolidation.md`) * [x] T015 \[S0801] Update affected package README files only where stale wording implies hosted identity, trusted erasure, production-hosted validation, certification, media readiness, or decommission completion (`apps/server/README_server.md`, `apps/web/README_web.md`, `apps/warroom/README_warroom.md`, `apps/cli/README_cli.md`, `apps/hooks/README_hooks.md`, `apps/adapters/README_adapters.md`, `packages/protocol/README_protocol.md`) *** ## Testing (4 tasks) Verification and quality assurance. ### Cross-cutting * [x] T016 \[S0801] Run a consistency scan for release claim gates, requirement ownership, no-overclaim wording, local-first boundaries, open finding ownership, evidence standards, and Phase 08 deferrals (`.spec_system/PRD/phase_08/phase08_requirement_routing_matrix.md`) * [x] T017 \[S0801] Run docs link/path review and verify decommission entries remain candidates rather than approvals (`.spec_system/PRD/phase_08/decommission_approval_matrix.md`) * [x] T018 \[S0801] Validate whitespace, ASCII encoding, LF line endings, and `git diff --check` for session outputs and touched docs (`.spec_system/specs/phase08-session01-release-requirements-and-risk-baseline/spec.md`) * [x] T019 \[S0801] Record command outcomes, docs review results, changed files, residual risks, and handoff to Session 02 for implementation and validation (`.spec_system/specs/phase08-session01-release-requirements-and-risk-baseline/implementation-notes.md`) *** ## Completion Checklist Before marking session complete: * [x] All tasks marked `[x]` * [x] All tests passing or scoped non-code deferrals documented * [x] All files ASCII-encoded * [x] Unix LF line endings * [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://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase08-session01-release-requirements-and-risk-baseline/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.