In your class, the teacher tells the kids what to do, and the principal tells the teacher what to do. That is a hierarchy: people or things stacked in ranked levels, where the ones on top have a different kind of say than the ones below. Folders inside folders on a computer work the same way.
Ranked Levels
A hierarchy is when stuff is put in order from higher to lower. A coach is above the team captain, who is above the players. A folder on your computer can hold other folders, which hold files. The big idea is the order only goes one way. The coach tells the captain what to do, not the other way around. Whether it's people, folders, or ideas, hierarchy means levels and one-way relationships between them.
Levels With Asymmetric Order
A hierarchy organizes things into ranked levels, with the relationship between levels being one-directional. A general commands colonels, who command captains. A class of animals contains species. A folder contains files. What matters is the asymmetry: information, control, or containment flows differently going up versus down. Hierarchies can emerge naturally (ecosystems, evolved organizations) or be designed deliberately (the army, file systems, class hierarchies in programming). They are useful because they let you reason at one level without tracking every detail of the others.
Hierarchy is an organization of elements into ranked levels in which adjacent levels stand in an asymmetric relation, typically of containment, authority, or abstraction. Four components specify any hierarchy: the units being ordered (people, files, concepts), the ordering relation (contains, commands, generalizes), the level structure with its asymmetric inter-level relations, and the cross-level interactions through which information, control, or influence flow. Hierarchies can be emergent (arising from evolution, selection, or self-organization, as in biological systems) or imposed (designed, as in bureaucracies or class inheritance in software). They contrast with heterarchies, where elements may have multiple parents and no single apex. Herbert Simon's parable of the watchmakers Hora and Tempus argued that hierarchical, modular designs are dramatically more robust than flat ones, because partial assemblies survive interruption while flat ones must restart.
Hierarchy is not Order because order is the ranking principle with asymmetric transitive relations on a flat set, while hierarchy is the level-based structure where elements occupy levels and relationships flow across levels; an ordering is relational structure on a flat set, hierarchy is multi-level containment or authority structure.
Hierarchy is not Emergence because emergence is the claim that higher-level properties are irreducible to lower-level facts, while hierarchy specifies the structural organization into ranked levels; hierarchy is architectural structure, emergence is a claim about explanatory sufficiency; hierarchical systems may or may not be emergent.
Hierarchy is not Layering because layering emphasizes abstraction boundaries and unidirectional dependencies with each layer hiding implementation details, while hierarchy emphasizes asymmetric ranking relations that can flow bidirectionally in terms of control and information; layering is about abstraction interfaces, hierarchy is about level structure.