# Structure **Domain:** Information Systems / Software Design **Doc Type:** Canonical Concept Node **Maturity:** Foundational **Related:** [[wiki/Knowledge Representation|Knowledge Representation]], [[wiki/Software Architecture|Software Architecture]], [[wiki/Flattening and Expanding Structures|Flattening and Expanding Structures]] --- ## Definition **Structure is the arrangement of parts and relations that makes information addressable and behavior predictable.** A structure may be expressed through directories, records, trees, graphs, indexes, modules, routes, scopes, or document blocks. ## Project Context Across the projects, structure repeatedly converts expensive ambiguity into cheap operations: a folder names an account, a path becomes a route, a function name addresses a capability, a pronunciation record selects a rhyme neighborhood, and a named Markdown block becomes a transformation target. ## Key Insight **Structure is stored reasoning.** The better the representation, the less work a runtime must perform to answer the questions it was designed to support. ## See Also [[wiki/Access Geometry|Access Geometry]], [[wiki/Convention-Based Routing|Convention-Based Routing]], [[wiki/Named Target|Named Target]], [[wiki/Technical Terms|Technical Terms]]