> 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_03/session_05_web_orchestration_cockpit_controls.md).

# Session 05: Web Orchestration Cockpit Controls

**Session ID**: `phase03-session05-web-orchestration-cockpit-controls` **Packages**: apps/web, apps/server, packages/protocol **Status**: Not Started **Estimated Tasks**: \~16-24 **Estimated Duration**: 2-4 hours

***

## Objective

Expose local orchestration state and guarded actions in the web cockpit without implying hosted collaboration or remote control.

***

## Scope

### In Scope (MVP)

* Add cockpit surfaces for task queues, agent templates, subagent lineage, and guarded action decisions.
* Show pending, accepted, rejected, expired, unavailable, and failed states with accessible controls.
* Keep selected hero, mission, queue, and lineage context synchronized.
* Preserve replay, export, notification, and settings privacy boundaries when orchestration events appear.
* Add component, store, and browser validation coverage for the new controls.

### Out of Scope

* War Room web-to-Worker federation.
* Multi-user presence, hosted accounts, hosted persistence, analytics dashboards, or public replay hosting.
* Public demo orchestration features unless Session 01 explicitly approves limited synthetic copy updates.

***

## Prerequisites

* [ ] Session 02 queue/template contracts are implemented.
* [ ] Session 03 lineage runtime is implemented.
* [ ] Session 04 guarded-action contracts are implemented.
* [ ] Phase 02 shell, overlay, accessibility, and reduced-motion expectations remain current.

***

## Deliverables

1. Web cockpit controls for queues, templates, lineage, and guarded action decisions.
2. Store and WebSocket handling for Phase 03 orchestration frames.
3. Accessible empty, loading, disconnected, unavailable, and error states.
4. Focused unit and browser validation coverage.

***

## Success Criteria

* [ ] Users can inspect local orchestration state and decide guarded actions from the cockpit.
* [ ] The UI never presents deferred hosted, War Room, inbound chat, or remote execution capabilities as shipped.
* [ ] Controls remain reachable and readable on supported desktop and mobile browser widths.


---

# 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_03/session_05_web_orchestration_cockpit_controls.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.