# Hierarchical / Modular **Trait Number:** 20 **Layer:** Abstract **Bit Position:** 4 (bit 20 overall) **Binary Encoding:** `00000000 00000000 00010000 00000000` **UHT Code (self-encoding):** `00 00 10 00` --- # Icon ![[Icon20.png|200]] ## Definition The entity has **internal structure composed of ordered or nested parts**, or participates in a broader hierarchy. It exhibits modularity, layering, or encapsulated relationships. --- ## When to Apply Use this trait when the entity: - Contains **subcomponents or internal modules** - Has a defined **position in a hierarchy or layered system** - Embodies **nested or encapsulated relationships** Avoid applying if the entity: - Is **atomic or indivisible** in structure - Exists **without formal or implicit hierarchy** - Is purely **flat, uniform, or featureless** --- ## Related Traits - [[00 04 00 00 Part of a larger system]]— Trait 14 is about integration; Trait 20 is about structural nesting. - [[00 00 20 00 Logical or Rule-based]] — Many logical systems use hierarchy to express scope or precedence. - [[00 00 01 00 Contextual abstraction]] — Hierarchy often emerges in context-dependent interpretations. --- ## Examples - A file directory tree - An organization chart - A UML class hierarchy - A modular hardware platform - A table of contents - A chemical molecule with atoms and bonds --- ## Commentary This trait helps identify **systems within systems** — structures that aren't merely groups, but **composed systems** with parent-child or module relationships. It supports architectural modeling, encapsulation, abstraction, and systems engineering decomposition. **Hierarchical structure is key to scalability and clarity**. Note: Hierarchy doesn't imply superiority — just **structured relation**. --- **© 2025 Steven Holland. All rights reserved.** [[Copyright Statement]]