> 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/phase06-session01-collaboration-requirements-and-safety-baseline/tasks.md). # Task Checklist **Session ID**: `phase06-session01-collaboration-requirements-and-safety-baseline` **Total Tasks**: 18 **Estimated Duration**: 3-4 hours **Created**: 2026-05-30 *** ## 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 | 3 | 3 | 0 | | **Total** | **18** | **18** | **0** | *** ## Setup (3 tasks) Initial configuration and environment preparation. ### Cross-cutting * [x] T001 \[S0601] Verify Phase 05 closeout, analyzer state, Phase 06 Session 01 prerequisites, and no active current session (`.spec_system/PRD/phase_06/session_01_collaboration_requirements_and_safety_baseline.md`) * [x] T002 \[S0601] Review Phase 05 closeout, Worker, web, protocol, local server, CLI, hook, docs, package README, and current test source inventory for the baseline (`.spec_system/PRD/phase_06/collaboration_isolation_safety_baseline.md`) * [x] T003 \[S0601] Create the safety baseline, requirement routing matrix, and mobile accessibility checklist deliverable files (`.spec_system/PRD/phase_06/collaboration_isolation_safety_baseline.md`) *** ## Foundation (5 tasks) Core structures and base implementations. ### apps/warroom, apps/web, packages/protocol * [x] T004 \[S0601] \[P] Capture Worker room lifecycle, web War Room state, protocol safe-frame, participant metadata, catch-up, sender-exclusion, blocked-field, and Phase 05 test evidence (`.spec_system/PRD/phase_06/collaboration_isolation_safety_baseline.md`) ### apps/server, apps/cli, apps/hooks * [x] T005 \[S0601] \[P] Capture local server `/warroom` stub, guarded-action unavailable behavior, orchestration diagnostics, CLI recovery, hook diagnostics, and no-executor evidence (`.spec_system/PRD/phase_06/collaboration_isolation_safety_baseline.md`) ### apps/web * [x] T006 \[S0601] \[P] Capture current mobile, responsive, accessibility, focus, reduced-motion, and no-overlap requirements and validation gaps (`.spec_system/PRD/phase_06/mobile_accessibility_acceptance_checklist.md`) ### Cross-cutting * [x] T007 \[S0601] Define optional Worker, local-only cockpit, shared-context, future hosted-service, analytics, public replay, remote execution, and trusted-erasure boundaries (`.spec_system/PRD/phase_06/collaboration_isolation_safety_baseline.md`) * [x] T008 \[S0601] Define participant authority, leader/member/observer roles, duplicate-action, stale-approval, reconnect, disconnect, leave, spoofing, and room-trust requirements (`.spec_system/PRD/phase_06/collaboration_isolation_safety_baseline.md`) *** ## Implementation (7 tasks) Main feature implementation. ### Spec system * [x] T009 \[S0601] Define collaboration redaction allowlists, catch-up bounds, sender-awareness, remote-context separation, and blocked prompt/file/command/terminal/transcript/secret/path/export/replay/scan/media/diagnostic/log/backup categories (`.spec_system/PRD/phase_06/collaboration_isolation_safety_baseline.md`) * [x] T010 \[S0601] Define isolation and sandbox threat boundaries for future file, git, terminal, Docker, remote, and hosted executors with consent, authorization, audit, rollback, diagnostics, redaction, and no-mutation expectations (`.spec_system/PRD/phase_06/collaboration_isolation_safety_baseline.md`) * [x] T011 \[S0601] Create the requirement-to-session routing matrix for authority, collaboration events, cockpit UX, isolation diagnostics, mobile hardening, validation closeout, and Phase 07/08 deferrals (`.spec_system/PRD/phase_06/phase06_requirement_routing_matrix.md`) * [x] T012 \[S0601] Create the mobile accessibility acceptance checklist for supported viewports, keyboard, pointer, screen-reader labels, focus return, reduced motion, text fit, no-overlap, and visible error states (`.spec_system/PRD/phase_06/mobile_accessibility_acceptance_checklist.md`) * [x] T013 \[S0601] Update master PRD, UX PRD, and Phase 06 PRD with baseline links, routing ownership, local-first boundaries, unavailable execution wording, and later-phase deferrals (`.spec_system/PRD/PRD.md`, `.spec_system/PRD/PRD_UX.md`, `.spec_system/PRD/phase_06/PRD_phase_06.md`) ### Stable docs * [x] T014 \[S0601] Update architecture, API, privacy/security, deployment, environments, hosted-service, release, and War Room runbook docs with optional Worker transfer, local-server separation, blocked payloads, hosted deferrals, unavailable executors, and non-erasure wording (`docs/ARCHITECTURE.md`, `docs/api/event-api-hook-contracts.md`, `docs/privacy-and-security.md`, `docs/deployment.md`, `docs/environments.md`, `docs/hosted-services.md`, `docs/release.md`, `docs/runbooks/war-room-operations.md`) ### Package docs * [x] T015 \[S0601] Update Worker, web, server, CLI, hooks, and protocol README files with Phase 06 authority, collaboration, isolation, diagnostics, mobile, accessibility, local-only fallback, and deferral guidance (`apps/warroom/README_warroom.md`, `apps/web/README_web.md`, `apps/server/README_server.md`, `apps/cli/README_cli.md`, `apps/hooks/README_hooks.md`, `packages/protocol/README_protocol.md`) *** ## Testing (3 tasks) Verification and quality assurance. ### Cross-cutting * [x] T016 \[S0601] Run a consistency scan for state names, authority vocabulary, blocked payload categories, optional Worker wording, local-server stub wording, unavailable executor wording, mobile acceptance terms, and baseline links (`.spec_system/PRD/phase_06/phase06_requirement_routing_matrix.md`) * [x] T017 \[S0601] Run whitespace, ASCII, LF, and link/path validation for all changed session, PRD, doc, and README files (`.spec_system/specs/phase06-session01-collaboration-requirements-and-safety-baseline/spec.md`) * [x] T018 \[S0601] Record command outcomes, docs review results, changed files, blockers, and next-session handoff for implementation and validation (`.spec_system/specs/phase06-session01-collaboration-requirements-and-safety-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/phase06-session01-collaboration-requirements-and-safety-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.