Flight ManualGuidesReferenceOperations

Guide 04 / Information architecture

Build from signal to systems.

Every page begins by answering where the user is, what state the system is in, and what action matters next.

Operating rule

Present dramatically. Operate calmly. Reveal technical depth only after intent.

Choose a depth

Signal establishes identity and invitation. Mission supports the active task. Systems reveals diagnostics and low-frequency configuration with a visible route back.

Horizon profile and depth sequenceThree layered horizon curves connect Signal, Mission, and Systems depths.0 / SIGNAL1 / MISSION2 / SYSTEMS

Preserve the sequence

On narrow screens, keep context first, place primary work next, and move supporting material after it. Schematic lines must never cross running copy or controls.