# Navigation and Settings Rules

Navigation and settings structure for Assembly Hangar.

## Navigation rules
- The main menu must be stable and predictable.
- Main modules must be easy to understand.
- Do not add random navigation items.
- Do not create multiple competing navigation systems.
- A user should know where they are within seconds.

## Suggested main modules
Dashboard, Projects, Intake, Analysis, Documentation, Tasks, Agents, Workflows,
Reviews, Deployments, Versions, Settings.

Do not create all modules blindly. First inspect what already exists and improve
it where possible.

## Settings rules
Settings need a clear central entry point and must not be hidden in random places
or scattered across pages.

Settings can be grouped into:
- Organization settings
- Project settings
- User settings
- Agent settings
- AI model settings
- Prompt settings
- Integration settings
- Deployment settings
- Versioning settings
- Notification settings
- Permission settings

Placement rules:
- Global settings belong in global settings.
- Project settings belong in project settings.
- User-specific settings belong in user settings.
- Agent behavior settings belong in agent settings.
- Integration settings belong in integrations/settings.
- Do not hide configuration in dashboard cards.
- Do not duplicate the same setting in multiple places.
- Do not mix operational workflow actions with configuration settings unless clearly separated.

## Acceptance criteria
- Settings are easy to find.
- Settings are grouped logically.
- No important setting is hidden in unrelated UI.
- No duplicate setting screens exist.
- Navigation supports the pyramid and real workflows.