> 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_02/session_02_cockpit_shell_and_navigation_cohesion.md).

# Session 02: Cockpit Shell and Navigation Cohesion

**Session ID**: `phase02-session02-cockpit-shell-and-navigation-cohesion` **Package**: apps/web **Status**: Not Started **Estimated Tasks**: \~16-22 **Estimated Duration**: 2-4 hours

***

## Objective

Make the primary cockpit shell, navigation, global commands, and empty states feel like one coherent operational surface.

***

## Scope

### In Scope (MVP)

* Review `Layout`, `TitleBar`, `CommandPalette`, `KeyboardShortcutsModal`, `FactionPicker`, and primary rail composition.
* Improve first-run, no-faction, no-server, disconnected, and empty-data states.
* Align visible navigation, keyboard shortcuts, command palette entries, and settings entry points.
* Prevent text overlap or truncation in supported desktop and tablet-sized cockpit layouts.
* Add focused component tests for shell state and command accessibility.

### Out of Scope

* Full mobile redesign.
* War Room Worker federation.
* New analytics or hosted account flows.

***

## Prerequisites

* [ ] Session 01 requirements are complete.
* [ ] Existing app shell tests are passing.

***

## Deliverables

1. Cohesive cockpit shell behavior and navigation affordances.
2. Improved empty and disconnected product states.
3. Tests for global command and shell accessibility behavior.
4. Documentation notes for supported shell behavior.

***

## Success Criteria

* [ ] A user can understand and navigate the cockpit without hidden-only controls.
* [ ] Keyboard and command palette actions match visible surface behavior.
* [ ] Empty and disconnected states are explicit and non-blocking.
* [ ] Supported viewports avoid incoherent overlap.


---

# 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_02/session_02_cockpit_shell_and_navigation_cohesion.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.