> 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-session05-web-orchestration-cockpit-controls/security-compliance.md).

# Security Compliance

**Session ID**: `phase03-session05-web-orchestration-cockpit-controls` **Package**: Cross-cutting (`apps/web`, `apps/server`, `packages/protocol`) **Started**: 2026-05-29 13:20 **Last Updated**: 2026-05-29 14:55

***

## Scope

This session adds local web cockpit controls for Phase 03 orchestration state. The reviewed boundaries are local task queue state, local agent templates, subagent lineage and mission graph metadata, guarded-action proposal decisions, WebSocket hydration frames, REST helper behavior, broad UI copy, replay-adjacent state, export-adjacent state, and documentation claims.

## Security Posture

* Local-first posture is preserved.
* Hosted queues, Worker federation, inbound commands, analytics, public replay hosting, remote execution, Docker isolation, and hidden terminal execution remain out of scope.
* Broad UI and WebSocket hydration must not expose raw prompts, command bodies, terminal output, file contents, tokens, transcript paths, or broad absolute paths.

## Findings

* No new hosted service, analytics, public sharing, Worker federation, inbound command, remote execution, Docker/container, or external transfer path was added.
* Server WebSocket hydration uses compact event frames for queue, templates, mission graph, and guarded actions. Hydration excludes raw queue titles, proposal rationale, command bodies, terminal output, file contents, tokens, transcript paths, transcript contents, and broad absolute paths.
* WebSocket parsing allowlists known orchestration frame fields before store application and replay-buffer capture.
* Broad UI copy flows through redaction helpers for paths, URLs, bearer tokens, secret-like values, and transcript/path-like subagent identifiers.
* Guarded-action decisions use expected revisions, idempotency keys, and store-level in-flight guards to prevent duplicate local decisions.
* Existing local auth, CORS, Origin, rate-limit, and body-size middleware setup remains unchanged.

## Verification

* `npm --workspace apps/server run typecheck` - pass.
* `npm --workspace apps/web run typecheck` - pass.
* Focused Vitest suite - pass, 31 tests.
* Biome lint on touched TypeScript files - pass.
* `git diff --check` - pass.
* ASCII and LF checks on touched text files - pass.
* Desktop and mobile Playwright smoke validation - pass.


---

# 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-session05-web-orchestration-cockpit-controls/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.