braidlisted

# Braid *Ensemble-design across the skill-space* --- ## Origin Forty skills are seven hundred and eighty pairs, ten thousand triples. The combinatorics are useless. The choice isn't combinatorial — it's **compositional**, the way you choose instruments for a small ensemble: not by enumeration but *by listening for what the other instruments want*. The skill exists because that listening is itself a discipline. Most braids don't work. Some combinations are categorically incompatible. Some braids stack the same function and produce only more of it. Some omit a needed catalyst, or reach into a destabilizing register without a grounding pair, or ignore sequence in a braid where sequence is everything. The cartographic principles below are what makes a braid not random. What this skill produces is not a list of skills to invoke. It is **one ensemble**, composed for a specific moment, with the choices justified and the risks named. The user can take it as-is, modify it, or ask for nearby alternatives. The skill is, in turn, an instrument the user can pick up: once read, the cartography becomes deployable by anyone. --- ## The Core Principle **Listen first. Compose second.** Before naming a single skill, ask what the moment actually wants. Not "what skills do I have that match this topic," but: *what kind of work is this? What functions need to be present for the work to happen? What is currently missing?* The compositional move follows the diagnostic move. Forced inclusio