What is parent-child structures?

Parent-child structures is a concept in personal epistemology: Parent-child structures let you zoom in and out between detail and abstraction. Every hierarchy is a compression strategy — it hides detail below and exposes summary above, letting you navigate complexity by choosing your altitude.

Example: You manage a software project with 200 tasks. Listed flat, they are incomprehensible — a wall of text where 'Design database schema' sits next to 'Buy team lunch for launch day.' Organized hierarchically, those same tasks become navigable: the project contains five workstreams, each workstream contains epics, each epic contains stories, each story contains tasks. Now you can operate at whatever level the conversation demands. In a board meeting, you say 'infrastructure is on track.' In a sprint planning session, you zoom into the twelve tasks under the 'authentication' epic. In a code review, you zoom into a single task. Same information, different altitudes. The hierarchy did not add any data — it added structure that lets you move between levels of detail without losing coherence.

This concept is part of Phase 14 (Hierarchy and Nesting) in the How to Think curriculum, which builds the epistemic infrastructure for hierarchy and nesting.