Flat top-level navigation mixes categories of different scope

What the limitation is
A consequence of the one-level subcategory cap: categories that are logically children of DEVELOPMENT (NEXUS, EVENT MODELING, LOGOS) must live at the top level, placing them alongside categories of entirely different scope and abstraction (APPS, CORTEX, NEIGHBORNET).

How it was discovered
Designing the category structure and observing that the top-level navigation was becoming a mixed list of implementation details alongside major system concepts.

Impact
Top-level navigation does not reflect the logical architecture of the system. A new person reading the category list cannot infer the relationships between categories. Discoverability suffers. The structure exists in documentation but not in the navigation.

Workaround
DEVELOPMENT tag applied to logically grouped categories. The Start Here wikis and README posts explain the relationships that the navigation cannot express.

Status
Workaround in place. Accepted constraint for interim platform use.

Note
This is the navigation-level consequence of Limitation #1. They share the same root cause but document different impacts — #1 is structural, this is experiential.

LOGOS Requirement
See: LOGOS → Requirements — Unlimited subcategory nesting