Reusable cognitive primitives
Modularity
Build a complex whole from separable, reusable parts with clean interfaces, so each can be understood, changed or replaced on its own.
Where it appears
Dependencies & synergies
Derived from the graph’s real structure — 12 concepts across 9 disciplines carry this pattern. Every figure is a count, not a score.
How many concepts carrying this pattern are seen through each discipline.
Other thinking patterns that recur on the same concepts — the more shared concepts, the more often they co-occur.
What kinds of relationships the carrying concepts form — the relational signature of the pattern.
Concepts where this pattern does the most cross-disciplinary work — each reaches disciplines beyond its own.
- Plasma membranereachesBiochemistryBiophysicsChemistryEnvironmental EngineeringEnvironmental SciencePhysicsSociologyStatistical Physics
- Additive synthesisreachesAcousticsMusic TheoryPhysicsSignal Processing
- Digital audio workstationreachesSignal Processing
- Subtractive synthesisreachesSignal Processing
- SynthesizerreachesSignal Processing
Carrying concepts that others in the same pattern build on (they depend on or follow from these).
- Subroutine — 1 other concept build on it
Examples across disciplines
Software split into modules that talk through defined interfaces.
Organs and organelles each do one job behind a membrane.
The division of labour splits production into specialised tasks.
How this pattern travels
Interpreted from where the pattern recurs in the atlas — structural transfer and coverage, not a claim it is universally the "best" model.
Recurs across 9 disciplines over 12 carrier concepts — a broadly transferable pattern.
structural · Structural recurrence in the atlas — a pattern is a reasoning lens, not a law.
2 of its 12 carrier concepts are themselves cross-disciplinary connectors.
structural · Structural recurrence in the atlas — a pattern is a reasoning lens, not a law.
Explicit "where it breaks" notes exist for 7 of 12 annotated assignments.
curated · Curated boundary annotations — absence is a representation gap, not evidence the model has no limits.
Currently dark in the atlas: no origin recorded · no assignment cites a source.
atlas representation · Describes the current Thinking OS representation, not the model itself.
Coverage matrix
How these concepts distribute across domains and concept families — real counts, not a score.
The statistical fingerprint
How the 12 concepts that exercise this pattern distribute — from the graph, not a ranking.
Disciplinary fingerprint
Carrier concepts under each illuminating lens.
How settled its carriers are
Epistemic status of the concepts that exercise this pattern.
Where the model breaks
This pattern is a reasoning lens, not a law. Here is where it stops helping:
- Application programming interface: An API modularises only what its contract covers; leaky, versioned or under-specified interfaces turn "independent" modules into a tightly coupled system.
- Division of labour: Specialisation raises output only while coordination and communication costs stay below the gains — past that, more division reduces total productivity.
- Functional group: Functional groups give predictable reactivity, but neighbouring groups and the whole molecule’s electronics modulate it — they are not context-free modules.
- Modular programming: Splitting into modules helps until coordination cost across interfaces exceeds the benefit of isolation — over-modularisation is its own failure mode.
- Object-oriented programming: Modularity pays off only with well-chosen interfaces; hidden shared state, deep inheritance and cross-cutting concerns quietly re-couple the modules.
- Organelle: Biological "modules" are not swappable like engineered parts — they co-evolved and are deeply interdependent; the analogy captures separation, not interchangeability.
- Plasma membrane: The membrane compartmentalises, but it is a selective, active boundary in constant exchange — not an encapsulation that hides its internals.
✕ More modules is always better. Poorly-placed seams create more coupling and overhead than they remove.
You have seen this model in one place. Where else could it apply — and where would the analogy break?
Additive synthesis →Look for the seams: where can you cut the system so the pieces barely depend on each other's insides? Good seams make change cheap.
- Recurs across 9 disciplines.
- 23 concepts exercise this thinking pattern.
- 7 of them explicitly note where the model breaks down.
Derived from the graph — a pattern is a reasoning lens, not a law.
Where are the seams — the places you could cut this system so each piece barely depends on the others' internals?
Keep this question handy when you meet something new — it helps you notice the pattern, not just name it.