What problem does it solve? Developers working on the SKY-KING air traffic control system need the correct architectural context for the flight controller (CTRL) workstation before making changes, otherwise they risk breaking shared components used by the tower (TWR) position or violating domain constraints. ## Core Features & Use Cases - Context Loading: Provides the full operational picture of the CTRL workstation, including its four views (Map, Table, Vertical, Classic), main UI layout, and unique features like Flight Zones Mode, Block Spaces, and OCR handwriting recognition. - API and State Reference: Lists the key REST routes (strips, block-spaces, map-zones, serials) and the relevant App.tsx state (strips, transfers, session, filterQuery, viewMode) for the controller position. - Change Safety Guidance: Documents what is shared with TWR versus CTRL-only, with explicit warnings about query filtering, table_modes, and relevantSectors. - Use Case: Before modifying the StripCard component or map display logic, load this context to know whether the change affects both CTRL and TWR positions and whether a /qa run is mandatory. ## Quick Start Load the ctrl-view context before working on the flight controller workstation screen in SKY-KING.