> 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-session03-subagent-lineage-and-mission-graph-runtime/security-compliance.md).

# Security Compliance

**Session ID**: `phase03-session03-subagent-lineage-and-mission-graph-runtime` **Last Updated**: 2026-05-29 13:35

***

## Scope

Session 03 adds local-only subagent lineage and mission graph runtime state across protocol, hooks, and server code.

## Initial Posture

* No hosted service credentials are required.
* Lineage state must remain local, in-memory, bounded, and non-executing.
* Hook payloads must not expose transcript paths, raw prompts, command bodies, terminal output, token-like values, or broad absolute paths.
* Archive, export, replay, WebSocket, and diagnostics boundaries must preserve existing redaction behavior for new lineage fields.

## Findings

* No hosted service, credential, database, or external-transfer dependency was added.
* Subagent hook payloads no longer send raw task prompts or transcript paths.
* Subagent IDs are sanitized and bounded in hooks and revalidated at server ingest.
* Archive and export redaction now covers `subagentId`, `parentSubagentId`, nested graph payloads, and `transcriptPath` fields.
* Typed lineage emits local graph state only. It does not spawn, stop, resume, fork, or remote-control subagents.

## Validation

* `npm --workspace packages/protocol run typecheck` - pass.
* `npm --workspace apps/server run typecheck` - pass.
* Focused Vitest coverage for protocol lineage, ingest vocabulary, hook payloads, server ingest, and export privacy - pass.
* Existing WebSocket test suite - pass.
* Biome check for touched TypeScript and JavaScript files - pass.
* ASCII, LF, and `git diff --check` hygiene - 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-session03-subagent-lineage-and-mission-graph-runtime/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.