> 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/phases/phase_11/session_01_documentation_and_privacy_sync.md).

# Session 01: Documentation And Privacy Sync

**Session ID**: `phase11-session01-documentation-and-privacy-sync` **Status**: Not Started **Estimated Tasks**: \~14-22 **Estimated Duration**: 2-4 hours

***

## Objective

Synchronize stable documentation and privacy guidance so Claude Code and Codex CLI are both documented as supported local hook targets.

***

## Scope

### In Scope (MVP)

* Update root README, onboarding, development, environments, privacy/security, API contract, CLI README, hooks README, and docs index.
* Add troubleshooting for Codex `/hooks`, project trust, and disabled hook features.
* Keep Claude docs intact.
* Document user-level Codex hook install as the default path.

### Documentation Targets

* `README.md`: Quick Start shows both Claude and Codex hook install paths.
* `docs/onboarding.md`: add `Codex CLI local session` setup.
* `docs/development.md`: list Codex hook install/test workflow and local state under `~/.codex`.
* `docs/environments.md`: document `CODEX_HOME` as optional and `FACTIONOS_CLI=codex-cli` as installer-managed for hook commands.
* `docs/privacy-and-security.md`: add Codex hook trust, transcript, MCP, and `apply_patch` privacy notes.
* `docs/api/event-api-hook-contracts.md`: split Claude-only hook contract language into provider-specific Claude and Codex subsections.
* `apps/hooks/README_hooks.md`: describe shared hook runtime plus provider maps.
* `apps/cli/README_cli.md`: document `--cli claude|codex|all`.
* `docs/README_docs.md`: mention Codex support while integration is active.
* `package.json` keywords and package descriptions: add Codex only after source support is implemented.

Docs must say users review Codex hooks in `/hooks` after install. Do not recommend `--dangerously-bypass-hook-trust` except as an advanced automation escape hatch outside normal local setup.

### Out of Scope

* Marketing copy or release notes.
* Plugin packaging docs beyond a clear deferral note.
* Hosted auth, hosted storage, analytics, or remote execution claims.

***

## Prerequisites

* [ ] Phase 10 complete.
* [ ] Current stable docs and package READMEs reviewed.
* [ ] Codex setup and trust behavior validated or fixture-backed.

***

## Deliverables

1. Updated docs presenting Claude and Codex as supported local hook targets.
2. Codex troubleshooting guidance for `/hooks`, trust, and hook visibility.
3. Privacy/security language for Codex payload minimization.
4. Docs index and API contract references updated.
5. Package metadata updates only after implementation support exists.

***

## Success Criteria

* [ ] Docs consistently present Claude and Codex as supported local hook targets.
* [ ] No docs recommend bypassing Codex hook trust as the normal path.
* [ ] Claude setup documentation remains intact.


---

# 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/phases/phase_11/session_01_documentation_and_privacy_sync.md?ask=<question>&goal=<endgoal>
```

`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.