think-concept-mappinglisted

<!-- thinking-framework-skills | https://github.com/product-on-purpose/thinking-framework-skills | Apache-2.0 --> # Concept Mapping When a domain is described in prose or sketched as a diagram, the relationships between its concepts stay vague: a line is drawn between two boxes, or two ideas are called "related", and how they actually relate is never specified. Concept mapping refuses the unlabeled link. It builds a non-hierarchical semantic network in which every connection is a **directed, labeled linking phrase**, so each node-link-node triple reads as an explicit **proposition** ("free tier - increases - signup volume"), and clusters are joined by **cross-links** that connect concepts across different parts of the map. The load-bearing move is forcing every relationship to be named, which externalizes how the domain interrelates and makes gaps, missing links, and false propositions visible. The output is a **concept map** plus a list of surfaced gaps. It externalizes and inspects how concepts relate; it does not claim to improve learning, retention, or decisions. ## When to Use - A domain has many interrelated concepts and the goal is to make how they relate explicit and inspectable. - You suspect hidden gaps or misconceptions in how a space is understood and want them surfaced as checkable propositions. - Integration across sub-areas matters, so the cross-links between clusters carry the value (for example linking a pricing concept to a support-cost concept). ## When