> 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/phase03-session01-orchestration-requirements-and-safety-baseline/security-compliance.md).

# Security And Privacy Baseline

**Session ID**: `phase03-session01-orchestration-requirements-and-safety-baseline` **Date**: 2026-05-29 **Status**: Baseline Recorded

***

## Scope

This session is documentation and planning only. It does not add runtime routes, WebSocket frames, hook handlers, CLI commands, browser controls, external transfers, dependencies, persisted state, production databases, or hosted services.

## Initial Baseline

* Core orchestration must remain local-first until later sessions deliberately implement scoped runtime behavior.
* Prompts, paths, commands, terminal output, transcripts, local state, replay buffers, exports, adapter payloads, and future external transfers remain sensitive developer data.
* Historical material under `EXAMPLES/` remains evidence only. Stable docs may cite conclusions and paths but must not copy raw prompts, command bodies, token-like values, OAuth IDs, probe output, sensitive paths, bundled code, or media.
* War Room Worker federation, hosted collaboration, inbound chat commands, public sharing, analytics, Docker isolation, and broad remote execution stay deferred or excluded unless a later approved session changes scope.

## Findings

None identified at session start.

## Baseline Result

No new security findings were introduced by this documentation-only session. Later Phase 03 implementation sessions must re-audit any new queue, template, lineage, guarded-action, web-control, CLI-diagnostic, adapter, replay, export, or external-transfer data path before marking shipped behavior complete.

## Validation

* Focused docs path review passed.
* Privacy-sensitive copy review passed; matches were policy wording or placeholder examples only.
* ASCII, LF, and `git diff --check` validation passed.
* Repository test suite passed after fixing the stale scan-status node in the web settings drawer.
* No blockers remain for the `validate` workflow step.


---

# 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/phase03-session01-orchestration-requirements-and-safety-baseline/security-compliance.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.