Skip to main content
This is the structural analysis phase. You (the orchestrator) perform this yourself — do NOT delegate to a subagent, because you need to maintain continuity with the elenctic interview and your domain research.

​
Context management

By this point your context contains the full elenctic interview, research results, both essays, and any supplementary research. If context is getting large, summarize the research and essays into their structural essences before beginning analysis.
You need the shape of the arguments — the ontological claims, the key evidence, the failure diagnoses — not every word.
Write your Phase 4 analysis to a file (determinate_negation.md) as you go, so you can reference it cleanly in Phase 5 and pass it to validation agents later.

​
Treat monk output as testimony, not evidence

Monks pushed to full conviction will sometimes get a bit silly — overstating mechanisms, presenting uncertain claims as settled, making leaps that sound compelling but don’t hold up. This is expected and not a problem.
Your job is to work with the structure of their arguments:
  • What they’re actually claiming
  • Where the real collision is
  • What assumptions they share
Not to be persuaded by their rhetoric. If a monk asserts something that smells like confabulation, note it and don’t build your synthesis on it.

​
Before you begin: Baseline your intuition

Write down your current best guess at the synthesis in one sentence. Set it aside. Proceed with the formal analysis below. At the end of Phase 5, compare your final synthesis to this initial guess.
If they’re substantially similar, you may be pattern-matching rather than genuinely synthesizing — check whether the Boydian decomposition actually produced cross-domain material or you recombined within the same frame.

​
Analysis structure

​
4.0 Internal tensions (self-sublation)

Before comparing the monks to each other, analyze each essay in isolation.
  • Where does Monk A’s own argument, pushed to its logical extreme, undermine its own premises?
  • Where does Monk B’s internal logic generate contradictions it can’t resolve?
This is Hegel’s self-sublation — the position contains its own negation.
The deepest synthesis material often comes not from where the monks disagree with each other but from where each position disagrees with itself.
Examples:
  • A monk that argues for decentralization but keeps needing coordination mechanisms is undermining itself
  • A monk that argues for integration but keeps carving out exceptions is undermining itself
These internal fractures point toward what each position is trying to become — which is often where the synthesis lives.

​
4.1 Surface contradiction

State the apparent disagreement in its simplest form. What does each side think the argument is about?

​
4.2 Shared assumptions

Identify what BOTH agents implicitly agree on that they don’t realize they agree on. These shared assumptions are often where the real limitation lives.

Unit of analysis

Do both assume the same unit of analysis?

Central problem

Do both assume the same problem is central?

Domain model

Do both assume a particular model of how their domain works?

Constraining frame

What frame constrains both of their visions?

​
4.3 Determinate negation: The engine

For each agent, identify the SPECIFIC way it fails — not “it’s wrong” but “it fails in THIS specific way, which points toward THIS specific thing missing from its worldview.”
Determinate negation is the engine of the dialectic. It is NOT:
  • “Monk A is wrong” (abstract negation — useless)
  • “Both have merits” (compromise — useless)
It IS:
  • “Monk A fails because [SPECIFIC FAILURE], which reveals [SPECIFIC MISSING THING]”
  • “Monk B fails because [SPECIFIC FAILURE], which reveals [SPECIFIC MISSING THING]”
  • The failures are COMPLEMENTARY — each agent’s blind spot is something the other can partially see, but neither sees the whole.

​
4.4 The hidden question

Articulate the deeper question the contradiction is ACTUALLY about — the question neither agent asked because they were both too committed to their answers.
This should reframe the entire debate in a way that makes both positions legible as partial truths.

​
4.5 Boydian decomposition (destruction phase)

Before attempting synthesis, shatter both positions into their atomic parts. This step comes from Boyd’s “Destruction and Creation” — you cannot synthesize something genuinely new by recombining within the same conceptual domains.
1

Identify the generic space

The abstract relational structure both positions share. Both assume a particular unit of analysis, a particular causal model, a particular temporal frame.This shared structure is the skeleton they’re both building on, and often the thing the synthesis needs to transcend.
2

List the atomic components

Individual claims, mechanisms, evidence, assumptions, metaphors, principles — stripped of which agent said them.Don’t organize by position. Create an unstructured collection.
3

Look for surprising connections

What mechanisms from A illuminate evidence from B? What assumptions from B reframe principles from A?
4

Ask: what material from adjacent domains

What analogies, frameworks, or mechanisms from outside the original debate space could bind these parts into something neither agent could have conceived?This is where genuinely new concepts come from.
Emergent structure test: The synthesis must have organizational properties that exist in neither input — properties that can’t be traced back to either monk’s position. If every element of your synthesis is attributable to one monk or the other, you’ve recombined, not created.
Example from test run (React/Vue dialectic): Shattering both positions revealed that “legacy burden” (from the corporate lab essay) and “self-referential complexity” (from the auteur essay) were describing the same phenomenon from different angles. Liberated from their positions, they connected to form a new concept: “innovation character is predicted by legacy burden, not funding source.” This wasn’t available from within either position.

​
4.6 Sublation criteria

Before attempting synthesis, specify what it must accomplish:
  • It must preserve [specific insight from A]
  • It must preserve [specific insight from B]
  • It must dissolve [the shared assumption both are trapped in]
  • It must answer [the hidden question]
Separating criteria from synthesis is important. It prevents you from pattern-matching to a pre-formed compromise.

​
Next: Sublation (Aufhebung)

Phase 5: Sublation

Generate the synthesis that transforms the question itself

Build docs developers (and LLMs) love

Get started for freeTalk to us