Skip to main content
Now generate the synthesis. Do additional research if needed — search for emerging approaches that might embody the synthesis, historical parallels where similar contradictions were resolved, or protocol/standard layers that dissolved analogous tensions.

​
The three requirements

The synthesis must:
1

CANCEL

Both original positions as complete truths (neither “A is right” nor “B is right” survives intact)
2

PRESERVE

The genuine insight in each position
3

ELEVATE

To a new concept that TRANSFORMS THE QUESTION ITSELF

​
What sublation is NOT

Watch for these failure modes — they are the most common way this phase fails:
  • ❌ “Use A for some cases and B for others” — that’s division of labor, not sublation
  • ❌ “Build something that combines the best of A and B” — that’s compromise, not sublation
  • ❌ “It depends on the context” — that’s surrender, not sublation
  • ❌ Policy recommendations (“A should open-source more”) — that’s not reconceptualization
  • ❌ “Both sides have valid points” — that’s the absence of thinking

​
What sublation IS

  • ✅ A reconceptualization of what the thing IS — potentially changing the unit of analysis itself
  • ✅ Concrete enough to act on or sketch architecturally
  • ✅ Something neither Monk A nor Monk B proposed or could have proposed from within their frame
  • ✅ Something that, once stated, makes it hard to go back to thinking in the old terms
  • ✅ Has the closure property: the synthesis can itself serve as input to the next dialectical round
If your synthesis is so abstract, so meta, or so hedged that it can’t be given to a monk to believe at full conviction and argue from — recursion will stall. A good synthesis is concrete enough to be a position, not just a commentary on positions.

​
Abduction test: Make the contradiction predictable

The synthesis is an abductive hypothesis, not a logical conclusion. You’re looking for the idea that, if true, would make the contradiction between the monks unsurprising — would explain why both positions exist and what each was partially perceiving.
Falsification test: Does this synthesis make the original contradiction a matter of course? If someone heard your synthesis first, would they predict the approximate shape of both monks’ positions? If yes, you’ve found a genuine reframing. If no, you’ve likely just compromised.

​
Assess your abduction type

Choosing from existing frameworks.Weakest — essentially a centrist position.
Aim for (c) but accept (b) if it genuinely resolves the contradiction. If you’re at (a), push harder — you haven’t left the original conceptual space.

​
Validation test: Draft expected responses

Draft what you expect the validation responses to look like — this helps check your synthesis before sending it to the agents:
“Yes, this preserves my core insight about [X], but I now see I was wrong about [Y] because I was trapped in [Z assumption]”
“Yes, this preserves my core insight about [X], but I now see I was wrong about [Y] because I was trapped in [Z assumption]”
If you can’t draft convincing versions of these, your sublation probably isn’t good enough. Revise before sending to the agents in Phase 6.

​
New contradictions: Fertility test

Identify what NEW contradictions this sublation generates. A genuine sublation is fertile, not final.
If the synthesis doesn’t generate new tensions, it’s probably just compromise dressed up.

​
Frame as model update

End with an explicit model update: 
Before this dialectic, the assumption was X.
The contradiction between A and B revealed Y.
The updated model is Z, because...

​
Save the output

Save the complete Phase 4 and Phase 5 output to files (e.g., determinate_negation.md and sublation.md). This keeps a clean record and allows you to pass file references or condensed summaries to validation agents.

​
Present to the user before validation

Before sending to the monks for validation, present the synthesis to the user.
Here’s my synthesis. Remember — this is where your judgment is most valuable. Does this ring true? Does it miss something? Is there a part that feels like hand-waving or compromise rather than genuine insight? Push back on anything that doesn’t land. I’d rather revise now than validate something that’s off.
If the user identifies issues, revise before proceeding to Phase 6. User corrections at this stage are extremely high-leverage — they prevent the validation and recursion phases from building on a flawed foundation.

​
Example: Kant’s sublation

Kant didn’t resolve the rationalism/empiricism debate by splitting the difference. He showed that experience provides content while reason provides structure — and once you see that, the original question (“does knowledge come from reason or experience?”) dissolves. It’s not that you pick a side. It’s that you can’t even think in the old terms anymore. That irreversibility is what distinguishes genuine synthesis from compromise.

​
Next: Validation

Phase 6: Validation

The monks evaluate whether they were elevated or defeated

Build docs developers (and LLMs) love

Get started for freeTalk to us