> 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/phase12-session02-release-closeout-and-rollout-readiness/privacy-security-release-review.md). # Privacy And Security Release Review **Session ID**: `phase12-session02-release-closeout-and-rollout-readiness` **Package**: Cross-cutting **Date**: 2026-05-31 **Status**: Complete *** ## Review Rule This review is boundary-specific. A passing secret scan is not enough to claim privacy or security readiness for every surface. Each boundary below must keep its own release claim narrow and source-backed. Tracked evidence may use labels, counts, status values, command names, and relative source refs only. Do not paste raw hook payloads, prompt bodies, patch bodies, command output, terminal output, transcripts, MCP argument bodies, tokens, credentials, local temp paths, broad local paths, or hook config bodies. *** ## Source Baseline | Source | Use | | ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | | `docs/privacy-and-security.md` | Product privacy posture, Codex boundary, no-erasure-overclaim wording, hosted no-claims. | | `docs/development.md` | Local hook workflow, focused checks, sensitive-evidence rules. | | `docs/deployment.md` | Hosted smoke rules and production-hosted no-claim boundaries. | | `docs/environments.md` | Environment variable ownership and reserved/future boundaries. | | `apps/cli/README_cli.md` | CLI install, status, doctor, uninstall, and local erasure wording. | | `apps/hooks/README_hooks.md` | Hook runtime, trust review, redaction, timeout, diagnostics, and plugin reuse boundaries. | | `docs/api/event-api-hook-contracts.md` | Local ingest, Codex lifecycle, unsupported route families, redaction contract. | | `.spec_system/specs/phase11-session03-end-to-end-validation-and-integration-fixes/codex-e2e-validation-record.md` | Prior isolated Codex validation and privacy evidence. | | `.spec_system/specs/phase12-session01-codex-plugin-packaging/codex-plugin-packaging-decision.md` | Plugin deferral and no-overclaim fields. | *** ## Boundary Matrix | Boundary | Release status | Current claim | Evidence source | Residual risk | | --------------------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------ | ---------------------------------------------- | ---------------------------------------------------------------------------------- | | Direct install | Pass | `factionos init --cli codex` installs user-level hooks and FactionOS local state only. | Phase 11 prior evidence; T011 isolated smoke. | Live `/hooks` trust remains user-owned. | | Hook map | Pass | `apps/hooks/hooks.codex.json` is the source template consumed by the CLI. | T010 focused test; hook README. | Multiple Codex hook sources may run concurrently; no ordering guarantee. | | Hook handlers | Prior evidence plus focused test pass | Handlers are timeout-bounded, local-first, and redaction-aware. | Phase 11 prior evidence; T010 focused test. | Runtime still depends on local server availability; spool fallback is local state. | | Server ingest | Prior evidence | Codex lifecycle and compact aliases are accepted through local `/event`. | Phase 11 fixture replay; API docs. | No hosted ingestion or provider transfer claim. | | Web display | Prior evidence | Codex labels, search/filter, mission detail, replay panel, and visible privacy guards passed fixture replay. | Phase 11 browser evidence. | Browser replay remains local-fragment only, not hosted sharing. | | Replay and export adjacency | Prior evidence | Replay/export-adjacent surfaces use redacted local fragments and visible no-hosted wording. | Phase 11 browser evidence; privacy docs. | Public replay hosting remains no-claim. | | Logs and diagnostics | Pass | CLI and hook diagnostics use compact labels, counts, and statuses only. | CLI and hooks READMEs; T011 smoke. | Operators must not paste raw logs into release notes. | | Backups | Pass | Codex first-run hook backup protects user-owned hook config; it is not exportable release evidence. | CLI README; Phase 11 evidence; T011 smoke. | Backup contains user hook config and must stay local. | | Uninstall | Pass | Codex uninstall restores backup or removes only FactionOS-managed hooks. | Phase 11 prior evidence; T011 smoke. | Uninstall is not trusted erasure and does not delete FactionOS state. | | Hosted smoke | Pass for no-network; live unavailable | No-network mode records unavailable/no-claim states without credentials. | T013 no-network hosted smoke; deployment docs. | Live deployed validation requires safe credentials and targets. | | Plugin package | No-claim | No `.codex-plugin/`, marketplace, plugin cache, or plugin uninstall is shipped. | Session 01 decision; artifact absence check. | Plugin may be reopened only by future distribution need. | | Hosted telemetry | No-claim | Codex hook support does not add hosted telemetry. | Privacy docs; Session 01 decision. | Future analytics must remain consent-gated and disabled by default. | | Remote execution | No-claim | Codex hook support is observational; no remote executor is active. | API docs; privacy docs. | Future executors need separate threat model. | | Trusted erasure | No-claim | CLI uninstall edits hook configuration only. | Privacy docs; CLI README. | Broad trusted erasure remains outside this release claim. | *** ## Sensitive Category Checklist | Category | Boundary result | Notes | | ------------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------- | | Raw prompts | Blocked | Never copy into release artifacts, diagnostics, logs, exports, replay-share payloads, or docs examples. | | Raw patch bodies and diffs | Blocked | Codex `apply_patch` is summarized as file/tool metadata only. | | Command output and terminal output | Blocked | Hook result payloads keep compact status and count metadata. | | Transcript paths and contents | Blocked | Treated as sensitive local state; not tracked. | | MCP argument bodies | Blocked | Reduced to safe tool labels, ids, statuses, and counts. | | Token-like values and credentials | Blocked | Secret scan and manual review must catch tracked evidence leaks. | | Broad local paths | Blocked | Diagnostics and release artifacts use labels and relative repo paths only. | | Hook config bodies | Blocked | Hook posture is reported through counts, ownership labels, backup state, and JSON validity. | | Hosted URLs with credentials, query, or fragments | Blocked | Hosted smoke rejects unsafe targets and no-network mode avoids public fetches. | *** ## Security Boundary Checklist | Check | Status | Notes | | --------------------------------- | ---------------------- | -------------------------------------------------------------------------------------------------------------- | | User-owned hook preservation | Pass | Prior evidence says preserved; T011 rollout smoke rechecked one unmanaged hook and unknown state. | | Backup-first hook management | Pass | Prior evidence says first raw hooks file is backed up when present; T011 rechecked backup state after install. | | Malformed Codex config handling | Prior evidence | Phase 10 and Phase 11 covered malformed config behavior. | | Duplicate managed hook prevention | Pass | Focused installer tests cover idempotent reinstall. | | Trust boundary enforcement | Manual review required | `/hooks` remains user-owned and cannot be automated safely. | | Error information boundaries | Pass | T011 status/doctor scan found no private hook-command, user hook, or hook file labels. | | External dependency resilience | Prior evidence | Hook handlers use bounded POST and sanitized local spool fallback. | | Cleanup scope | Pass | T011 uninstall removed managed hooks and preserved unmanaged state; no erasure claim added. | *** ## No-Claim Review The release must not claim: * Codex plugin packaging, plugin install, plugin cache refresh, plugin trust review, or plugin uninstall. * Hook trust bypass or automatic permission approval. * Project-local trusted `.codex` setup. * Hosted telemetry, hosted identity, hosted storage, public replay hosting, production-hosted validation, push delivery, Cloudflare Tunnel, remote access, or remote execution. * Broad trusted unified erasure. *** ## Findings No release-blocking privacy or security findings were identified. *** ## Final Review Outcome | Area | Outcome | | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | Install | Pass - isolated smoke and prior evidence show user-level Codex install, backup-first merge, unmanaged hook preservation, and compact output. | | Hooks | Pass - focused tests and prior evidence show source-map readiness, timeout-bounded handlers, and redaction boundaries. | | Server | Pass by prior evidence - local ingest supports Codex fixture replay without hosted ingestion claims. | | Web/replay/export adjacency | Pass by prior evidence - browser replay and export-adjacent copy remained redacted and local-first. | | Diagnostics/logs | Pass - status and doctor stay compact; hook logs remain local diagnostic state. | | Backups | Pass - backups are local user-protection state and are not copied into release evidence. | | Uninstall | Pass - managed-hook cleanup only, no trusted-erasure claim. | | Plugin | No-claim - plugin packaging is deferred and no plugin validation is represented as passed. | | Hosted/production | No-claim - no-network smoke passed only as unavailable/no-claim evidence; live hosted validation is unavailable here. | | Remote execution | No-claim - this release adds no executor. | | Trusted erasure | No-claim - uninstall is narrower hook-config cleanup. | --- # 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/phase12-session02-release-closeout-and-rollout-readiness/privacy-security-release-review.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.