> 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_07.md).

# phase\_07

- [PRD Phase 07: Hosted Services and Analytics Guardrails](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_07/prd_phase_07.md)
- [Analytics Consent and Payload Controls](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_07/analytics_consent_payload_controls.md)
- [Hosted Identity and Authorization Guardrails](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_07/hosted_identity_authorization_guardrails.md)
- [Hosted Payload Privacy Blocklist](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_07/hosted_payload_privacy_blocklist.md)
- [Hosted Persistence and Public Replay Boundaries](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_07/hosted_persistence_public_replay_boundaries.md)
- [Phase 07 Hosted Services Requirements And Privacy Baseline](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_07/hosted_services_requirements_privacy_baseline.md)
- [Phase 07 Requirement Routing Matrix](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_07/phase07_requirement_routing_matrix.md)
- [Push, Remote Access, Tunnel, and Operator Diagnostics Guardrails](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_07/push_remote_access_operator_diagnostics_guardrails.md)
- [Session 01: Hosted Services Requirements and Privacy Baseline](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_07/session_01_hosted_services_requirements_and_privacy_baseline.md)
- [Session 02: Hosted Configuration and Client Exposure Boundaries](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_07/session_02_hosted_configuration_and_client_exposure_boundaries.md)
- [Session 03: Hosted Identity and Authorization Guardrails](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_07/session_03_hosted_identity_and_authorization_guardrails.md)
- [Session 04: Hosted Persistence and Public Replay Boundaries](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_07/session_04_hosted_persistence_and_public_replay_boundaries.md)
- [Session 05: Analytics Consent and Payload Controls](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_07/session_05_analytics_consent_and_payload_controls.md)
- [Session 06: Push Remote Access and Operator Diagnostics Guardrails](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_07/session_06_push_remote_access_and_operator_diagnostics_guardrails.md)
- [Session 07: Hosted Guardrails Validation and Documentation Closeout](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_07/session_07_hosted_guardrails_validation_and_documentation_closeout.md)


---

# 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_07.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.