Applied History — The Council Chamber
The Council Chamber is where history meets the present. This wing does not ask "what happened?" — the thematic wings handle that. It asks: "what does history teach?" and "how can historical reasoning improve decisions made today?" Applied history is the most powerful and most dangerous wing of Wan Shi Tong's library. Powerful because historical patterns genuinely recur. Dangerous because misapplied analogies have led to catastrophic decisions (Munich, Vietnam, Iraq).
The Council Chamber's core discipline: every analogy has limits. The skill is knowing where the analogy holds and where it breaks.
Child Skills
| Skill |
Type |
Path |
Handles |
historical-pattern-recognition |
knowledge |
historical-pattern-recognition/SKILL.md |
Identifying and evaluating recurring patterns: overstretch, traps, manias, cycles |
history-and-decision-making |
knowledge |
history-and-decision-making/SKILL.md |
Neustadt and May's "Thinking in Time," scenario planning, intelligence analysis |
timeline-builder |
action |
timeline-builder/SKILL.md |
Annotated visual timelines with causal connections |
debate-simulator |
action |
debate-simulator/SKILL.md |
Argue both sides of contested historical questions |
nexus-event-analyzer |
action |
nexus-event-analyzer/SKILL.md |
Multi-wing synthesis for events spanning all domains |
Routing Table
| User Signal |
Route To |
Rationale |
| "Is this like," "does history repeat," "what pattern," "has this happened before" |
historical-pattern-recognition |
Pattern identification and evaluation |
| "What should we learn from," "what's the lesson," "how does history help us decide" |
history-and-decision-making |
Applied reasoning for decisions |
| "Give me a timeline of," "what's the sequence," "show me the chronology" |
timeline-builder |
Structured chronological output |
| "Argue both sides," "what would X say vs Y," "debate this" |
debate-simulator |
Structured multi-perspective argumentation |
| "How did the Industrial Revolution affect everything," "all dimensions of X" |
nexus-event-analyzer |
Multi-wing synthesis |
Multi-Skill Questions
| Scenario |
Load Order |
Why |
| "Is the current US-China rivalry like the Thucydides Trap?" |
historical-pattern-recognition → history-and-decision-making |
First identify the pattern and its limits, then apply it to decision-making |
| "What can the 2008 financial crisis teach us about today?" |
historical-pattern-recognition → (bridge to investing/archon) |
Pattern recognition first, then cross-domain application |
| "Give me a comprehensive view of how decolonization reshaped the world" |
nexus-event-analyzer → timeline-builder |
Multi-wing synthesis first, then structured chronological output |
Curriculum Order
historical-pattern-recognition (foundation) — Learn to see patterns AND their limits before applying themhistory-and-decision-making (application) — Apply patterns to present decisions using structured frameworkstimeline-builder (tool) — Structure historical knowledge visuallydebate-simulator (advanced) — Test understanding by arguing multiple positionsnexus-event-analyzer (synthesis) — The most complex skill; requires familiarity with all thematic wings
Level Progression
- Foundational: historical-pattern-recognition
- Intermediate: history-and-decision-making, timeline-builder
- Advanced: debate-simulator, nexus-event-analyzer
Conflict Resolution
| Conflict |
Resolution |
Reason |
| Pattern suggests X but specific case differs |
Specific case wins |
Patterns are heuristics; case evidence trumps general patterns |
| Two patterns apply but suggest different outcomes |
Present both with confidence levels |
Applied history is probabilistic, not deterministic |
| Historical analogy conflicts with domain-specific analysis |
Defer to domain expert with historical context |
History provides context, not overrides |
General rule: Analogies always have limits. Always name the limits alongside the analogy.
Scope Boundaries
This director handles: Questions about what history teaches, how to use historical reasoning for present decisions, and structured historical analysis outputs.
Escalate to wan-shi-tong when:
- The question is about a specific historical event (route to thematic wing)
- The question is about historical methods (route to historiography)
- The question requires deep regional context (route to regional-atlas)
1---2name: applied-history3description: Route questions about using history as a practical tool for understanding the present and making decisions. Activate when users seek historical analogies, recurring patterns, lessons for current situations, or want to build timelines and argue both sides of historical debates.4---56# Applied History — The Council Chamber78The Council Chamber is where history meets the present. This wing does not ask "what happened?" — the thematic wings handle that. It asks: "what does history *teach*?" and "how can historical reasoning improve decisions made today?" Applied history is the most powerful and most dangerous wing of Wan Shi Tong's library. Powerful because historical patterns genuinely recur. Dangerous because misapplied analogies have led to catastrophic decisions (Munich, Vietnam, Iraq).910The Council Chamber's core discipline: every analogy has *limits*. The skill is knowing where the analogy holds and where it breaks.1112## Child Skills1314| Skill | Type | Path | Handles |15|---|---|---|---|16| `historical-pattern-recognition` | knowledge | `historical-pattern-recognition/SKILL.md` | Identifying and evaluating recurring patterns: overstretch, traps, manias, cycles |17| `history-and-decision-making` | knowledge | `history-and-decision-making/SKILL.md` | Neustadt and May's "Thinking in Time," scenario planning, intelligence analysis |18| `timeline-builder` | action | `timeline-builder/SKILL.md` | Annotated visual timelines with causal connections |19| `debate-simulator` | action | `debate-simulator/SKILL.md` | Argue both sides of contested historical questions |20| `nexus-event-analyzer` | action | `nexus-event-analyzer/SKILL.md` | Multi-wing synthesis for events spanning all domains |2122## Routing Table2324| User Signal | Route To | Rationale |25|---|---|---|26| "Is this like," "does history repeat," "what pattern," "has this happened before" | `historical-pattern-recognition` | Pattern identification and evaluation |27| "What should we learn from," "what's the lesson," "how does history help us decide" | `history-and-decision-making` | Applied reasoning for decisions |28| "Give me a timeline of," "what's the sequence," "show me the chronology" | `timeline-builder` | Structured chronological output |29| "Argue both sides," "what would X say vs Y," "debate this" | `debate-simulator` | Structured multi-perspective argumentation |30| "How did the Industrial Revolution affect everything," "all dimensions of X" | `nexus-event-analyzer` | Multi-wing synthesis |3132### Multi-Skill Questions3334| Scenario | Load Order | Why |35|---|---|---|36| "Is the current US-China rivalry like the Thucydides Trap?" | historical-pattern-recognition → history-and-decision-making | First identify the pattern and its limits, then apply it to decision-making |37| "What can the 2008 financial crisis teach us about today?" | historical-pattern-recognition → (bridge to investing/archon) | Pattern recognition first, then cross-domain application |38| "Give me a comprehensive view of how decolonization reshaped the world" | nexus-event-analyzer → timeline-builder | Multi-wing synthesis first, then structured chronological output |3940## Curriculum Order41421. **`historical-pattern-recognition`** (foundation) — Learn to see patterns AND their limits before applying them432. **`history-and-decision-making`** (application) — Apply patterns to present decisions using structured frameworks443. **`timeline-builder`** (tool) — Structure historical knowledge visually454. **`debate-simulator`** (advanced) — Test understanding by arguing multiple positions465. **`nexus-event-analyzer`** (synthesis) — The most complex skill; requires familiarity with all thematic wings4748### Level Progression49- **Foundational**: historical-pattern-recognition50- **Intermediate**: history-and-decision-making, timeline-builder51- **Advanced**: debate-simulator, nexus-event-analyzer5253## Conflict Resolution5455| Conflict | Resolution | Reason |56|---|---|---|57| Pattern suggests X but specific case differs | Specific case wins | Patterns are heuristics; case evidence trumps general patterns |58| Two patterns apply but suggest different outcomes | Present both with confidence levels | Applied history is probabilistic, not deterministic |59| Historical analogy conflicts with domain-specific analysis | Defer to domain expert with historical context | History provides context, not overrides |6061**General rule**: Analogies always have limits. Always name the limits alongside the analogy.6263## Scope Boundaries6465**This director handles**: Questions about what history teaches, how to use historical reasoning for present decisions, and structured historical analysis outputs.6667**Escalate to wan-shi-tong when**:68- The question is about a specific historical event (route to thematic wing)69- The question is about historical methods (route to historiography)70- The question requires deep regional context (route to regional-atlas)
npbuilds