Motif Structure Wind Tunnel

Four Concepts, Don’t Confuse Them

• Topic: What object the information is discussing, e.g., "team discussion", "AI attention". It only defines the semantic scope.
• Motif: The same type of fundamental dilemma encountered repeatedly across different fields. It does not replace the original problem with a more abstract term, but retains the transferable relationship in plain language.
• Analogy: Two cases that seem similar, e.g., "a team is like a jury". It is only an entry point for discovery.
• Structure: The causal skeleton that remains valid after removing domain-specific nouns. It explains what relationships generate what outcomes.

Understanding Agreement

• Clear Concepts: Each core concept can be explained in plain language as "what specifically refers to here" and accompanied by a visible indicator.
• Clear Relationships: Readers can retell "under what conditions, how who influences whom, what changes occur first, and what outcome is finally achieved".
• Examples Bear Relationships: Examples are not just for creating a sense of similarity; their roles, direction of action, and outcomes must correspond to the abstract relationships.
• Judgmentable Boundaries: When conditions change, readers can predict how the relationships will change and know what observations will force them to revise their judgments.

How the Wind Tunnel Feeds into the Conclusion

• Wind Tunnel is an Internal Method: Use the same example, change one key condition, observe how the prediction changes, and find when the model fails and what signals will alter the judgment. It is no longer listed as a visible section.
• Conclusion is a Calibrated Deliverable: First present the key differences of the same example after condition changes to give readers concrete handles; then condense the differences into a transferable abstract rule and return to the original phenomenon to explain what should be observed now.

Applicable Boundaries

Workflow Routing

Workflows/FindStructure.md

Gotchas

• "Team communication" and "AI cognition" are still topics; "how to do better" is too broad and unconstrained. Motifs must retain the real relationship or tension.
• A motif is not a more abstract title. If a motif still contains two or more core terms that cannot be explained in plain language, decode them first before outputting.
• Only place one minimal example under a motif to make the relationship run for the first time; do not expand a list of cross-domain cases.
• By default, set only one example anchor that runs through the entire text. Structure cards refer back to specific moments in it, relationship diagrams connect the whole picture, and the wind tunnel changes its conditions; do not retell the same story everywhere.
• "Like the immune system" and "adopting double-blind" are just source or solution names. A structure is only valid if the causality can be clearly explained after removing the source name.
• Cross-domain search is internal skill, not a default section. Spreading out three fields item by item often only suppresses the real motif.
• By default, only keep one or two structure cards; the third must prove it cannot be merged into the first two. Each card must complete "clear concept, clear relationship, example mapping", but does not require displaying three fields.
• Examples must map roles and causality. Only saying "this is like something" creates familiarity but does not clarify the relationship.
• When there are multiple structures, first determine whether they are in series, parallel, nested,制衡（check and balance）, or feedback, then draw the diagram; do not arrange multiple structures into a chain just because you see them.
• By default, do not perform Cartesian products or calculate combination numbers. For multiple motifs, first find the structural relationships; only expand combinations when explicitly requested by the user.
• Wind tunnel is a method, not a section. It first locks the baseline prediction, then changes one condition, compares the first appearing difference, and finally points out the applicable boundary and judgment update rule; the written text only retains the most understanding-altering test.
• Conclusion is not a full-text summary. It sequentially completes "concrete test -> abstract rule -> return to phenomenon", letting the example provide handles and the abstract relationship gain transferability.
• Concrete tests and abstract rules must be progressive: the former answers "what happens when conditions change", the latter answers "what more general relationship does this indicate". If the two paragraphs are just paraphrases, delete the weaker one.
• Minimal reversible experiments are only used for action problems. Concept interpretation defaults to providing discriminative tests, not transforming every ideological problem into an action suggestion.
• Conceptual models cannot evade counterexamples by narrowing boundaries afterwards. First declare applicable conditions and distinctive predictions; cases outside the boundary only serve to draw the boundary, not as support or refutation.
• Wind tunnel does not introduce a new set of terminology. If a new concept must be invented to explain test results, go back to the structure card and re-decode.
• Evidence boundaries are only stated once at the end. Do not repeatedly insert warnings in each structure card to interrupt reasoning.
• When facts are uncertain, keep them in the internal candidate layer; if output is necessary, clearly mark them as to be verified, and do not treat remembered stories as facts.

Output Requirements

Input

Motif

Structure

Conclusion

date +%Y%m%dT%H%M%S

date "+%Y-%m-%d %a %H:%M"

~/Documents/notes/{timestamp}--structure-{topic}__structure.org

read-only

#+title: Structure: {topic}
#+date: [{readable time}]
#+identifier: {timestamp}
#+filetags: :structure:

* Input
* Motif
* Structure
* Conclusion

Examples

User: "Why does team discussion always get led astray by the first speaker? Find the structure behind it."
→ Motif asks in plain language: Why does information that appears earlier tend to become the reference for subsequent judgments?
→ Use a sentence from a meeting scene to make this relationship run once
→ Structure card explains what "reference" means, how it influences latecomers, and provides specific examples
→ Internal wind tunnel changes the speaking order or information source, comparing how predictions change
→ Conclusion first presents the concrete differences after condition changes, then extracts "information that appears first gains interpretive power"

User: "This AI is good at deep mining of local areas, but always misses anomalies that change the whole picture. Analyze it with structure wind tunnel."
→ Motif: How does limited attention balance local development and unknown exploration
→ Extract the relationship skeleton between local deep mining and peripheral patrol
→ Internally use the wind tunnel to find the minimal anomaly escalation experiment, and incorporate the test results into the conclusion

User: "Please provide the cross-domain sources of this motif and analyze how three motifs combine."
→ Only then expand sources or multi-motif processing
→ Still first judge the series, parallel, nested, check-and-balance or feedback relationships between structures and draw the diagram
→ Only calculate the combination space when the user continues to request combination mathematics