> 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/phase01-session07-runtime-contract-documentation/tasks.md). # Task Checklist **Session ID**: `phase01-session07-runtime-contract-documentation` **Total Tasks**: 16 **Estimated Duration**: 2-3 hours **Created**: 2026-05-29 *** ## 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 | 4 | 4 | 0 | | Implementation | 6 | 6 | 0 | | Testing | 3 | 3 | 0 | | **Total** | **16** | **16** | **0** | *** ## Setup (3 tasks) Initial documentation context and verification planning. * [x] T001 \[S0107] Verify Sessions 01-06 completion, validation summaries, and Phase 01 tracker state (`.spec_system/PRD/phase_01/PRD_phase_01.md`) * [x] T002 \[S0107] Map stale runtime-doc claims and Phase 01 traceability requirements into implementation notes (`.spec_system/specs/phase01-session07-runtime-contract-documentation/implementation-notes.md`) * [x] T003 \[S0107] Identify focused documentation verification commands before edits (`.spec_system/specs/phase01-session07-runtime-contract-documentation/implementation-notes.md`) *** ## Foundation (4 tasks) Canonical runtime contract and source-intake ownership. ### docs * [x] T004 \[S0107] Update architecture docs for final Phase 01 optional service, security boundary, and current-gap status (`docs/ARCHITECTURE.md`) * [x] T005 \[S0107] Update legacy consolidation with Phase 01 session outcomes, direct `EXAMPLES/` source coverage, and remaining dependencies (`docs/legacy-consolidation.md`) * [x] T006 \[S0107] Update release/development docs for final Phase 01 gates, local state, provider-transfer, and decommission boundaries (`docs/release.md`, `docs/development.md`) * [x] T007 \[S0107] Update privacy docs to remove Phase 01-completed open-risk wording while preserving retained release risks (`docs/privacy-and-security.md`) *** ## Implementation (6 tasks) Stable user-facing and package docs. ### root and package READMEs * [x] T008 \[S0107] Update root README shipped capabilities and known gaps after Sessions 04-06 (`README.md`) * [x] T009 \[S0107] Update CLI README with final Phase 01 lifecycle and unsupported integration boundary wording (`apps/cli/README_cli.md`) * [x] T010 \[S0107] Update hooks README with final Phase 01 ingest/listener safety and first-class event mapping wording (`apps/hooks/README_hooks.md`) * [x] T011 \[S0107] Update server and protocol READMEs with final Phase 01 route, WebSocket, export/archive, LLM, and protocol ownership status (`apps/server/README_server.md`, `packages/protocol/README_protocol.md`) ### API docs * [x] T012 \[S0107] Update concise and detailed API docs to remove stale Phase 01 hardening language and confirm runtime status vocabulary (`docs/api/README_api.md`, `docs/api/event-api-hook-contracts.md`) * [x] T013 \[S0107] Cross-link stable docs so `EXAMPLES/` is traceability evidence, not user-facing implementation guidance (`README.md`, `docs/README_docs.md`, `docs/legacy-consolidation.md`) *** ## Testing (3 tasks) Documentation verification and closeout. * [x] T014 \[S0107] Run stale-claim grep checks, markdown path spot checks, ASCII/LF checks, and `git diff --check` (`.spec_system/specs/phase01-session07-runtime-contract-documentation/implementation-notes.md`) * [x] T015 \[S0107] Run practical repo gates affected by version/doc changes and record results (`.spec_system/specs/phase01-session07-runtime-contract-documentation/implementation-notes.md`) * [x] T016 \[S0107] Create validation and security reports for the documentation-only session (`.spec_system/specs/phase01-session07-runtime-contract-documentation/validation.md`, `.spec_system/specs/phase01-session07-runtime-contract-documentation/security-compliance.md`) *** ## Completion Checklist Before marking session complete: * [x] All tasks marked `[x]` * [x] All verification commands passing * [x] All files ASCII-encoded * [x] implementation-notes.md updated * [x] Ready for updateprd *** ## Next Steps Run the implement 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/phase01-session07-runtime-contract-documentation/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.