Navigation

What It Models

The navigation object organizes console destinations into application sections, tools and administrative areas. Customer record placements extend that map. Rhythm HQ presents a separate list for staff, and the current address identifies the active destination.

Identity and Attributes

Sections and entries have registry keys and destinations rather than persistent menu records. Entries carry labels, icons, permission hints and build status. Filter text and section expansion belong to the current rendered menu. At the pinned source, Accounting follows Marketing; the recorded planning change requires it immediately after CRM.

Relationships

The shell contains the menu, and each menu entry targets a console address. Application entitlements determine which sections can appear. Metadata supplies the record types and custom apps that extend the built-in map.

Invariants

The invariant rows distinguish observed filtering from documented obligations. Menu visibility does not replace destination authorization. Settings entries require visible work within their area, and customer placements load independently of built-in entries. The required Accounting order is not enforced at the pinned source.

How It Is Stored and Shared

The console computes the menu from code registries and the current context. Metadata retains the underlying placement records. Its navigation answer is trusted; fallback definition lists are filtered locally. No service stores or consumes this menu as a record.

Open Design Questions

Product has not settled how customers encounter unfinished destinations. Websites is an unconditional menu link. The rule that sections need a built screen or a placement has implementation evidence but lacks an inspected confirming product record.