What is purpose-driven abstraction?

Purpose-driven abstraction is a concept in personal epistemology: Too detailed is as unhelpful as too abstract — match the level to your current need.

Example: A senior engineer is debugging a production outage. She does not need the system architecture diagram that shows twelve microservices and their relationships — that is too abstract. She does not need the raw assembly instructions executing on the server CPU — that is too detailed. She needs the application logs from the specific service that is failing, the recent deployment diff, and the error stack trace. Her purpose — diagnosing a specific failure — determines the exact level of detail that will be useful. An hour later, when she writes the post-mortem for leadership, she shifts to the architecture diagram because her purpose has changed. Same system, same person, different purpose, different level.

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.