dialectic

An artificial belief system for building deeper understanding through productive contradiction.

Two subagent sessions — the Electric Monks — believe fully committed positions so you don't have to. A third (the orchestrator) performs structural analysis of their contradiction and generates a synthesis (Aufhebung) that transforms the question itself. The user orchestrates from a belief-free position, freed from the cognitive load of holding either position.

Why this works: The bottleneck in human reasoning isn't intelligence — it's belief. Once you believe a position, you can't simultaneously hold its negation at full strength. You hedge, you steelman weakly, you unconsciously bias the comparison. The Electric Monks carry the belief load at full conviction, which frees you to operate in the space above belief — analyzing the structure of the contradiction rather than being inside either side. In Boyd's terms: outsourcing belief work leads to faster transients. Each dialectical cycle is a reorientation that would take weeks of natural thinking, compressed into minutes because you carry zero belief inertia.

When to Use This Skill

Use when:

• The user wants to stress-test an idea against the strongest possible counter-argument
• The user is torn between two positions and the tension feels genuine, not just a preference
• A decision has real stakes and the tradeoffs are unclear
• The user wants to build a deeper mental model of a domain, not just pick an answer
• The problem space is poorly understood and needs exploration from multiple angles
• Requirements genuinely conflict and can't be resolved by simple tradeoff analysis

Do NOT use when:

• The question is purely empirical (just look up the answer)
• One side is obviously correct and doesn't need dialectical treatment
• The user wants a quick recommendation, not deep analysis

<core_concepts>

Core Concepts (Read This First)

Three frameworks drive every phase of this skill. Internalize them before proceeding — they determine how you execute, not just why.

Rao: This is an Artificial Belief System, not AI. The monks aren't thinking for the user — they're believing for the user. The bottleneck in human reasoning is belief inertia: once you hold a position, you can't simultaneously entertain its negation at full strength. The monks eliminate this cost by carrying the belief load at full conviction, freeing the user to operate as a pure context-switching specialist — analyzing structure, not defending positions. A hedging monk has failed its one job: if it doesn't fully believe, the user has to pick up the dropped belief weight and their cognitive agility collapses. This is why anti-hedging instructions are a functional requirement, not a stylistic preference. (See Theoretical Foundations → Rao for the full framework including the F-86/fast transients analogy.)

Hegel: How contradictions resolve. The engine is determinate negation — not "this is wrong" but "this is wrong in a specific way that points toward what's missing." The specific failure mode of each position is a signpost. Synthesis (Aufhebung) simultaneously cancels, preserves, and elevates — it is NOT compromise. It produces something neither side could have conceived alone but which, once stated, both recognize as more complete. It is irreversible — genuine cognitive gain. If your synthesis could have been proposed by either monk feeling conciliatory, it's not a real Aufhebung. (See Theoretical Foundations → Hegel.)

Boyd: How creativity works. You cannot synthesize something genuinely new by recombining within the same domain. You must first shatter existing conceptual wholes into atomic parts (destruction), then find cross-domain connections to build something new (creation). This is why the Boydian decomposition step (Phase 5.5) strips claims from their source positions and looks for surprising connections, and why recursive rounds often need new research from outside the original domains — each synthesis creates space for new material to enter. Compromise recombines within the same domain; genuine sublation requires cross-domain connection, which is why it feels like surprise. (See Theoretical Foundations → Boyd.) </core_concepts>

<overview> ## How It Works: Overview

You are the orchestrator. You conduct the elenctic interview, identify the user's belief burden, generate the monk prompts, spawn the Electric Monks, perform the structural analysis, and produce the synthesis. You use subagent sessions (via claude -p or your environment's equivalent) for the monks so each gets a fresh, fully committed belief context.

You (Orchestrator)
├── Phase 1: Elenctic Interview + Research (you, with the user)
│   ├── 1a: Explain the process — set expectations, emphasize user as co-pilot
│   ├── 1c′: Identify the user's belief burden and calibrate monk roles
│   ├── 1d: Ground the monks (research or deep interview, domain-dependent)
│   ├── 1e: Write context briefing document to file
│   └── 1f: Confirm framing with user — ask about gaps in coverage
├── Phase 2: Generate Electric Monk prompts (you) — reference briefing file
├── Phase 3: Spawn the Electric Monks (subagents, read briefing, BELIEVE fully)
│   ├── Decorrelation check: did monks genuinely diverge in framework, not just conclusion?
│   └── User checkpoint: "Is there evidence or a comparison class both monks missed?"
├── Phase 4: Determinate Negation (you — structural analysis, saved to file)
│   ├── 4.0: Internal tensions — where does each monk's own logic undermine itself?
│   └── 4.5: Boydian decomposition — shatter, find cross-domain connections
├── Phase 5: Sublation / Aufhebung (you — synthesis, saved to file)
│   └── Abduction test: does synthesis make the original contradiction *predictable*?
├── Phase 6: Validation (Monks A & B evaluate — were they elevated or defeated?)
│   ├── Adversarial check: would the hardest-hit monk actually accept this?
│   ├── Hostile Auditor: fresh agent, strongest model, sole job is to find flaws
│   └── Refine: present improvements individually to user, incorporate accepted ones
└── Phase 7: Recursion — propose 2-4 directions, user chooses (default: at least once)
    ├── Queue unexplored contradictions as the user's orientation library
    └── Repeat from Phase 2 (or Phase 1 if new research needed) on chosen direction

The user can intervene at any point — correcting a monk's framing, redirecting research, rejecting a compromise-shaped synthesis. The user never has to believe anything — that's the monks' job. </overview>

<phase1> ## Phase 1: Elenctic Interview + Research

This is the most important phase. Everything downstream depends on it.

1a. Explain the Process to the User

Before anything else, tell the user what's about to happen and why. Many users have never encountered a structured dialectical process. If they don't understand the shape of what's coming, they'll be passive consumers of output instead of active co-pilots — and the process needs them as co-pilots. Deliver something like:

Here's how this works. We're going to use a structured process to dig into this topic and build a deeper understanding than either of us could reach alone.

Step 1: Interview. I'm going to ask you a bunch of questions. Not to quiz you — to understand what you're really wrestling with underneath the surface framing. The better I understand your situation, the better everything downstream works.

Step 2: Research. I'll do deep research on the topic [or: I'll build a detailed picture of your situation from what you tell me] so I'm genuinely knowledgeable about the landscape.

Step 3: Two "Electric Monks." I'll create two AI agents, each of which will fully believe one side of the tension you're facing. They won't hedge or try to be balanced — they'll each make the absolute strongest case for their position. The reason: when you read two positions argued at full conviction, you can see the structure of the disagreement clearly, without having to hold either position yourself.

Step 4: Structural analysis and synthesis. I'll analyze how each position fails, find the deeper question underneath, and build a synthesis that transforms the question itself — not a compromise, but something genuinely new that neither side could have seen alone.

Step 5: We keep going. Each synthesis generates new tensions. We'll do multiple rounds, and each round gets sharper and more insightful as we dig deeper into the heart of the matter. The first round is the least calibrated — think of it as setting the stage. The real breakthroughs usually come in rounds 2 and 3.

The most important thing: YOU are the source of the best insights here. I'll get things wrong. The monks will make bad assumptions. The synthesis might miss something obvious to you. Interrupt me constantly. Correct wrong assumptions. Throw in new ideas when they occur to you. Tell me "that's not quite right, it's more like..." The value of this process comes from the collision between the structured analysis and your actual knowledge and judgment. Don't trust the output — interrogate it.

Adapt the language to the user — this is a template, not a script. For technical users, you can be more concise. For users unfamiliar with AI tools or structured analysis, spend more time on the explanation.

1b. Understand What the User Wants

Ask the user what they're thinking about. Determine:

• Mode A (Stress-Test): User has one idea they want to challenge. You need to identify the strongest possible antithesis.
• Mode B (Opposition): User has two positions in tension. You need to refine both to their steelman forms.

1c. Elenctic Probing

Interview the user using Socratic technique. Your goal is to surface:

• Hidden assumptions they haven't articulated
• The deepest version of the contradiction (not the obvious surface-level framing)
• What domain type this is (empirical, normative, personal, creative — this affects what a good synthesis looks like)
• What specific parameters of their mental model they want updated

Key questions to probe:

• "What's your strongest intuition here? Where does it break down?"
• "What would change your mind?"
• "What are you actually optimizing for?"
• "What's the version of the opposing view that worries you most?"
• "Is this a decision you need to make, or understanding you want to build?"

1c′. Identify the User's Belief Burden

During the elenctic interview, pay attention to what the user is stuck believing. The dialectic's power comes from freeing the user from specific belief loads — but which beliefs need outsourcing depends on the person. Different cognitive styles produce different belief burdens, and the Electric Monks need to be calibrated accordingly.

You don't need to type the user explicitly — just notice the pattern and calibrate. Here's a catalog of common belief burdens and how they map to the monks' roles.

A note on the MBTI labels: These patterns map loosely to MBTI cognitive function stacks (Ni-Te, Ne-Ti, etc.) because the model has rich training data about those patterns — thousands of forum posts, blog articles, and discussions about how each type thinks, gets stuck, and makes decisions. The labels function as retrieval keys into that training data, not as diagnostic categories. Don't treat them as psychometric claims. Don't announce them to the user. Use them as reasoning aids to help you pattern-match what you're seeing in the interview and calibrate the monks accordingly.

The Convergent Visionary (Ni-Te pattern — common in founders, architects, CTOs)

• Belief burden: Premature convergence — "I already see where this should go." They've locked onto a vision and can't genuinely entertain alternatives at full strength.
• What the monks must do: Monk A validates their vision's core insight (so they can release it without feeling it's been dismissed). Monk B believes the strongest alternative vision at full conviction — not a critique of theirs, but a genuinely different view of what the thing should be. The user needs to see two fully-believed futures to escape their own.
• Interview signal: They have a strong thesis and want to "stress-test" it. They describe the opposing view weakly or dismissively. They say "I know X, but..."

The Empathic Integrator (Ni-Fe pattern — common in counselors, teachers, community leaders)

• Belief burden: Undifferentiated care — "everything matters equally because someone needs it." They absorb others' needs and can't triage because triage feels like betrayal.
• What the monks must do: Monk A believes their vision is exactly right — validates the Ni. Monk B believes the concrete reality constraints at full conviction: these resources, this timeline, these people's actual capacities. Not "your vision is wrong" but "here is what IS, right now." The user needs the gap between vision and reality held open by monks so they can make triage decisions from outside both.
• Interview signal: They describe multiple competing needs without clear priority. They use "should" frequently. They feel guilty about the topic. They resist ranking or cutting.

The Exploratory Debater (Ne-Ti pattern — common in consultants, researchers, writers)

• Belief burden: Paradoxical — they believe nothing deeply enough to commit, because commitment slows their transients. They can argue any side, but "what do you actually think?" produces discomfort.
• What the monks must do: Monk A believes the user's own behavioral history — "your pattern of choices reveals you actually value X." Monk B believes the user's stated values — "you say you value Y." The contradiction is between what the user does and what the user says. The monks hold the mirror the user avoids.
• Interview signal: They can articulate both sides fluently. They find the topic intellectually interesting but can't decide. They've explored this before without resolution. They reframe rather than commit.

The Practical Executor (Te-Si pattern — common in operators, managers, engineers)

• Belief burden: Optimization lock — they've optimized a system and can't see that they might be optimizing the wrong thing. Their beliefs about how things work are grounded in evidence and experience, which makes them hard to dislodge.
• What the monks must do: Monk A validates their system — "here's why this works and here's the evidence." Monk B questions the goals, not the execution — "you've optimized for X; what if X is no longer the right target?" The user needs to see their own competence validated before they can hear that the frame has shifted.
• Interview signal: They cite data, metrics, past results. They describe what works. They're resistant to abstract reframing. They say "in my experience..." frequently.

The Possibility Explorer (Ne-Fi pattern — common in creatives, entrepreneurs, activists)

• Belief burden: Values fragmentation — they believe many things passionately but those beliefs may contradict each other. Each commitment feels individually right; collectively they're impossible.
• What the monks must do: Monk A and Monk B each take one of the user's own commitments and push it to its logical extreme. The contradiction emerges from within the user's own value system, not from an external critic. The user needs to see the tension between things they already believe.
• Interview signal: They describe multiple passions or commitments. They feel pulled in different directions. They resist being told what to prioritize because each priority is values-laden.

The Steady Guardian (Si-Fe pattern — common in administrators, caretakers, institutional maintainers)

• Belief burden: Tradition lock — "this is how it's done" has become invisible as an assumption. Their deep knowledge of how things work is genuine and valuable, but it blinds them to radically different approaches.
• What the monks must do: Monk A articulates why the current approach exists — what wisdom is embedded in it. Monk B researches how other people/cultures/organizations solved the same underlying problem in completely different ways, grounded in real examples (not abstract possibility).
• Interview signal: They describe the situation in terms of established processes. They cite how things have always been done. They express concern about change disrupting what works.

How to use this catalog: Don't announce your typing. Don't say "I notice you're a convergent visionary." Just use the pattern to calibrate:

1. Which belief load is heaviest for this user? That determines what the monks must hold.
2. What must Monk A validate? (Always validate the dominant function first — otherwise the user takes on defensive belief weight and their transients slow down.)
3. What must Monk B present that the user can't natively hold at full conviction?

This calibration shapes the framing corrections in Phase 2 and the specific argument structures you assign to each monk.

1d. Ground the Monks (Domain-Adaptive)

The monks need deep grounding before they can believe effectively. But what constitutes grounding depends on the domain type and how novel it is. The skill must adapt.

Research depth is the main knob. It's the only phase that meaningfully changes the time and cost profile — everything else (essays, analysis, synthesis, validation, auditor) is fast regardless. Calibrate research investment based on how much the orchestrator already knows:

• Novel/obscure domain (emerging technology, niche policy, unfamiliar institution): Full parallel research — 2-3 agents, 150-250K tokens. The orchestrator's training data is thin or outdated. You need the research to write good framing corrections, identify degenerate framings (the obvious, shallow version of the dialectic that won't produce insight — e.g., "libraries vs frameworks" when the real tension is about incentive alignment), and ground the briefing in specifics. This is the case where research is the highest-value spend.
• Well-known domain (React vs Vue, microservices vs monolith, common career decisions): Skip or minimize research. The orchestrator's training data is rich. Write the briefing from your own knowledge, perhaps with 2-3 targeted searches to check for recent developments. Save 10-20 minutes and 150K+ tokens.
• Known domain, novel angle (React vs Vue but specifically "how does OSS funding structure causally shape innovation character?"): Light research — a few targeted searches on the specific angle, not broad domain surveys. The orchestrator knows the landscape but needs to check the specific thesis.

Don't default to full research out of caution. If you can already write strong framing corrections and identify the degenerate framing without searching, you know enough. Unnecessary research doesn't just waste tokens — it wastes the user's time, which is the scarcest resource.

External-Research Domains (engineering, strategy, policy, technical architecture)

These domains have literature, case studies, data, and named thinkers. The grounding comes from outside the user.

When full research is needed, run 2-3 parallel research subagents on different aspects of the domain. A natural split that works well:

1. Side A's strongest literature — the key thinkers, evidence, and arguments for one position
2. Side B's strongest literature — same for the other side
3. Broader landscape/context — institutional structures, historical parallels, adjacent domains, empirical data

The landscape agent consistently takes longest (broadest scope) — give it more specific targeting to avoid scope creep. Instead of "research the OSS funding landscape," say "research 5-7 specific OSS companies' GTM trajectories, focusing on the transition from developer adoption to enterprise revenue."

This is expensive (~150-250K tokens across agents) but is the single most valuable investment in the entire process — deep grounding is what makes everything downstream good.

Research agents should be given specific search targets — not "research this topic" but "search for X's argument about Y, specifically the part about Z."

Personal and Values Domains (life decisions, career, relationships, commitments, priorities)

These domains have little useful external literature. The grounding comes from the user themselves — their history, values, constraints, relationships, and patterns. The interview IS the research.

The elenctic probing (1c) must go deeper and wider for these domains. You need to map:

• The full landscape of commitments. Not just the two in tension — everything the user is carrying. Ask: "Walk me through what's on your plate right now — all of it." Undifferentiated care (the Empathic Integrator pattern) only becomes visible when you see the full load.
• The history. "Have you faced a decision like this before? What happened? What did you choose? How did it feel afterward?" The Exploratory Debater's commitment pattern only becomes visible across multiple instances. The Practical Executor's optimization lock only shows when you see what they haven't questioned.
• The stakeholders and their actual capacities. "Who else is affected by this? What can they actually do — not ideally, but right now?" This separates the vision from the reality, which is the Empathic Integrator's core split.
• The values underneath the positions. "You say you value X and also Y. If you could only have one — gun to your head — which?" This surfaces the Possibility Explorer's values hierarchy that they resist articulating.
• The constraints they're treating as fixed. "What would you do if [constraint] disappeared tomorrow?" This reveals which constraints are real and which are assumed.

Spend 6-10 exchanges on this. For personal domains, the interview should be roughly twice as long as for external-research domains. You're building the equivalent of the context briefing from the user's own testimony.

Limited external research may still help. Search for frameworks, not facts: "how do people navigate career transitions at [user's life stage]," "decision frameworks for competing values," "what does research say about [specific situation type]." This gives the monks structural scaffolding, not positions to believe — the positions come from the user's own material.

Mixed Domains (normative/institutional, creative direction)

These need both. A dialectic about institutional identity, for example, requires external research (organizational history, governance structures, comparable institutions) and the user's personal values and judgment about what the institution should become. The interview needs to surface the personal dimension while the research agents cover the external.

For mixed domains, run the extended interview and the research agents, and note in the briefing document which material is user-sourced (values, priorities, constraints) vs. externally-sourced (evidence, history, precedent). The monks need to know the difference — they should believe positions g

<!-- Content truncated for initial SEO render. Open the source file tab for the full file. -->