Question · Seed idea · last reconsidered August 17, 2026
What did the abstraction remove?
A question about what a simplifying layer takes away along with what it simplifies.
Open question — no answer required
- Territories
- Tools
- Kind of question
- Engineering · Diagnostic
About the details, cases, and difficulties that a useful abstraction necessarily hides — and what happens when one of them turns out to matter after all.
Why it matters
An abstraction is judged by what it lets you ignore, and it is only ever tested on the cases where ignoring that was safe. What it removed stays invisible until a case arrives that depended on it, by which point the people who knew the removed part have usually moved on.
Tensions
- The abstraction is worth having precisely because of what it removes; the cost and the benefit are the same act.
- The removal is only detectable from below, by someone who still knows the layer underneath — a population the abstraction is designed to stop producing.
Positions taken
has response
- Legibility costs local knowledgeClaim
It gives the question a political answer: what was removed was somebody's competence.
Questions this opens
questions
- Which institutions encode forgotten failures?Question
Much of what an abstraction removed is sitting in a rule nobody can explain any more.
Connected ideas
questions
Paths through this question
appears in
- What a Map Cannot CarryPath
Back to the working version of the question, now with teeth.
Explore this question in the map
Continue exploring
- ClaimLegibility costs local knowledgeScott's claim that a scheme can only administer what it has first simplified, and pays for the simplification.
- ConceptAbstractionA simplifying layer that hides detail in order to make something easier to use or reason about.
- QuestionWhich institutions encode forgotten failures?A question about institutional rules whose original justification, a past failure, is no longer remembered.