> 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-session02-task-queue-and-agent-template-contracts/security-compliance.md).

# Security Compliance

**Session ID**: `phase03-session02-task-queue-and-agent-template-contracts` **Reviewed**: 2026-05-29 **Status**: Complete

***

## Scope

This session adds local-only task queue and agent template contracts across `packages/protocol` and `apps/server`. Queue entries and template suggestions remain in memory, bounded, and non-executing.

***

## Security Posture

| Area                     | Status   | Notes                                                                                                                                                                         |
| ------------------------ | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Local-only state         | Verified | Queue and template managers keep state in process memory and add no hosted persistence.                                                                                       |
| Input validation         | Verified | Queue and template routes validate body, query, IDs, enums, limits, revisions, and references before manager calls.                                                           |
| Sensitive data redaction | Verified | Validation errors omit raw request values; queue WebSocket frames omit raw titles, summaries, prompts, paths, commands, tokens, terminal output, transcripts, and raw bodies. |
| Unsupported boundaries   | Verified | Unapproved queue-adjacent paths retain deterministic 501 `task-queue` planned responses.                                                                                      |
| Auth and rate limits     | Verified | Orchestration routes are registered after existing auth, CORS, rate-limit, and body-size middleware without changing defaults.                                                |

***

## Validation

* `npm --workspace packages/protocol run typecheck` passed.
* `npm --workspace apps/server run typecheck` passed.
* `npx vitest run packages/protocol/tests/orchestration.test.ts apps/server/tests/orchestration.test.ts apps/server/tests/websocket.test.ts` passed with 16 tests.
* Focused Biome lint passed.
* Changed-file ASCII scan passed.
* Changed-file LF scan passed.
* `git diff --check` passed.

***

## Findings

* No new security findings.
* Residual later-phase risk: unified erasure for local orchestration state remains outside Session 02 scope and should be handled by the planned recovery or release-hardening sessions.

***


---

# 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-session02-task-queue-and-agent-template-contracts/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.