Hierarchy Atlas

ADMINISTRATOR Companion to the Master List. Defines the L1 (Primary) → L2 (Secondary) → L3 (Tertiary) grouping that drives:

• Component card breadcrumbs (since v2.31.0.32)
• The missing-component picker
• Navigation
• Atlas-driven L3 dept lookup in the Master validator (v2.31.0.33)

Source file

UCS_Hierarchy_Atlas_v1.xlsx at:

C:\Users\<user>\OneDrive - TSM\00_INFO\11. PMS Templates\00. UCS\00. System Description, Rules\

How it gets into the system

The v2.31.0.23 task adds hierarchy_atlas as the sixth file kind in ucs_foundation_files (alongside manifest, master_full, master_slim, l4, source). The Foundation import flow ingests it on activation.

POST /api/admin/recompute-atlas-tree (v2.31.0.33) re-derives the materialized atlas tree from the imported file.

Why it matters

L3 carries department semantics. When the Master List dept column is missing or ambiguous, the validator resolves dept by walking up to the L3 row in the Atlas. This decoupling means a single Master row can move between depts by changing only its L3 mapping in the Atlas — no Master rewrite needed.