> 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/docs/adr/0002-cloudflare-worker-war-room.md).

# 0002. Cloudflare Worker War Room Backend

**Status:** Accepted **Date:** 2026-05-28

## Context

FactionOS needs optional room federation without making the local server responsible for remote participant state. The current repo includes `apps/warroom`, a Cloudflare Worker and Durable Object backend with room creation, join, approval, participant sockets, and bounded catch-up.

## Options Considered

1. Use the local server as the room relay.
2. Use a Cloudflare Worker and Durable Object backend.
3. Keep War Room as a UI-only concept.

## Decision

Use `apps/warroom` as the room relay backend. Keep it optional for local development and wire the web panel to it in Phase 05.

## Consequences

* Core local observability does not need Cloudflare credentials.
* Room state can be bounded and isolated per room code.
* The web client must clearly show Worker outage, reconnect, catch-up, and approval states once wired.
* The current web panel remains a stub until Phase 05 completes the integration.


---

# 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/docs/adr/0002-cloudflare-worker-war-room.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.