On this page Origin Core premise IFR Four phenomena The AND/OR test Principles On the map Limits Research
01
Where CDSA came from

Origin

CDSA did not begin as a framework. It emerged as the next question once a structural gap became visible.

When 47 design and product methodologies are placed on a single coordinate system, a pattern appears: the field has no reliable way to distinguish between contradictions that should be resolved and those that should not. Every methodology treats contradiction as an obstacle.

TRIZ introduced the key insight: unsolvable problems contain contradictions, and contradictions have structure. That structure can be found. CDSA extends this principle — asking not only whether a contradiction can be resolved, but whether resolving it would be correct.

The framework makes two key moves. Contradiction-driven: the contradiction is not a symptom — it is the primary analytical object. Positional: the same situation looks different depending on the position of the observer. Changing the position changes what is visible.

02
The shift in logic

Core premise

Productive contradictions drive systems. Resolving them can collapse the engine.

Standard methodology assumes: a contradiction is a problem; a problem has a solution; the goal is to find it. This works at the surface levels of the system — interface, behaviour, workflow. Methods built on this assumption perform well there.

At the architectural level, the assumption breaks down. Some contradictions are not obstacles to the system's functioning — they are the mechanism of that functioning. The tension between two requirements that cannot both be fully satisfied is exactly what creates the pressure that drives the system forward.

The field still lacks a reliable way to distinguish contradictions that should be resolved from those that should be maintained. CDSA is an attempt to build that diagnostic.

03
Before classification

IFR — the zero step

Before classifying a contradiction, define where the system should go. Classification without direction produces accurate diagnosis of the wrong object.

The Ideal Final Result (after Altshuller) is the state in which the function is performed and the carrier disappears. It is not a destination — it is a direction. A compass, not a map.

IFR precedes the AND/OR test because the test result only becomes meaningful in the context of a direction. Whether to hold a productive contradiction, resolve a dissipative one, or choose at a real fork — all of these depend on what the system is moving toward.

IFR-navigation: when the IFR is defined, it generates a trajectory of structurally inevitable steps. The question is not what will happen — it is what conditions make the next step possible sooner.

Use IFR to choose Which contradictions to create, which to dissolve, which to preserve. The IFR is the criterion, not the answer.
IFR ≠ goal A goal is a state to reach. IFR is a structural attractor — the direction in which well-functioning systems tend to evolve. It constrains the space of valid interventions.
When IFR is absent Classification still works — but intervention direction becomes arbitrary. Without IFR, a productive contradiction cannot be stimulated correctly: transgression without direction is disruption, not development.
04
What lives at Level 7

Four phenomena

The architectural zone of the map appears as a single region. The field treats it as one problem type. It is not. Four structurally different phenomena live there — and they require four different interventions. Confusing them produces four different kinds of failure.

Phenomenon 01
Real fork

An irreversible choice. One path closes permanently. After this point the system loses a degree of freedom — not by intention, but structurally.

Intervention Make the choice consciously. Map what disappears. Do not attempt to reverse.
Phenomenon 02
False fork

The system presents a choice as either/or. But AND is structurally possible — it is simply invisible from the current position. The apparent fork is not a property of the system. It is a property of the observer's position.

Intervention Do not choose. Find the position from which AND becomes visible.
Phenomenon 03
Productive contradiction

Two requirements that cannot both be fully satisfied — and should not be. The tension between them drives the system. Resolving it can collapse the engine that makes the system work.

Intervention Do not resolve. Diagnose type. Maintain and stimulate the tension.
Diagnostic Productive holding generates new solutions and system movement. Avoidance generates explanations for why movement is impossible.
Response vector
Transformation

A dissipative or destructive contradiction that can become productive through a change of configuration — not resolution, but reorientation. The tension remains; its direction changes.

Intervention Do not eliminate. Change the configuration so the same tension drives the system instead of draining it. The carrier shifts; the contradiction persists — now as engine.
Signal A dissipative pattern that has remained stable across multiple intervention cycles — the energy is real, the direction is wrong.

These four look identical from a distance. A team facing any of them experiences the same symptom: standard tools stop working, the situation resists resolution, stakes are high. The difference only becomes visible when you ask what kind of thing you are actually dealing with.

05
The diagnostic

The AND/OR test

Before any intervention at the architectural level, one question determines which of the three phenomena you are facing — and whether transformation is the appropriate response vector. It does not complete the diagnosis — it determines which branch of analysis to enter.

The test prevents the most common error: treating a false fork as a real one and making an irreversible choice that was never actually required.

Pre-diagnostic test
01 The system presents a choice as either/or.
↓ Ask:
02 What if AND? Is holding both sides structurally possible?
A — AND is impossible

Real fork. Choose consciously. Map what each path closes permanently.

B — AND is possible but invisible

False fork or productive contradiction. Do not choose yet. Diagnose position and contradiction type first.

A false fork and a productive contradiction both survive the AND test — they require further distinction. Transformation applies when a dissipative contradiction has persisted across multiple intervention cycles: the energy is present but the direction is wrong. The test prevents the most expensive error at the architectural level: the irreversible choice that was never required.

06
How CDSA operates

Operating principles

CDSA is not a process with steps. It is a set of diagnostic moves that change what becomes visible when a system is under structural pressure.

Contradiction first The contradiction is not a symptom of the real problem. It is the primary analytical object. Start there, not at the solution.
Type before intervention Applying a method before diagnosing the type of contradiction produces structurally different failures depending on the mismatch. Diagnosis precedes action.
Position is a variable A false fork is not a property of the system. It is a property of the observer's position. Changing position changes what is structurally visible.
Hold, don't resolve Productive contradictions should be maintained, not eliminated. The task is to stimulate the tension — not to find a compromise that removes it.
IFR as navigation The Ideal Final Result defines the trajectory, not the next step. Each step follows from the logic of the IFR — the question is what conditions make the next step possible faster.
07
Position in the system

Where CDSA lives on the map

StratoAtlas maps methodologies across two axes: system level (from User Perception to Architecture) and action type (from Diagnosis to Optimisation).

CDSA operates at Level 7 — Architecture & Forks. Its primary action type is Resolution — the column that is nearly empty across the entire methodology landscape. This is not a coincidence. It is the zone where the field has not yet developed stable practices.
L7
Architecture

The empty zones on the map are not gaps in the catalogue. They are gaps in the discipline. CDSA is an attempt to build stable practice in the region where it is most absent.

Most methods that reach Level 7 treat it as a single zone. CDSA's first contribution is distinguishing three phenomena that currently occupy the same cell — and introducing transformation as a fourth response vector for contradictions that resist elimination.

08
Where CDSA does not operate

Limits of applicability

StratoAtlas maps every methodology against an illusion zone and a harm zone. CDSA is not exempt from its own logic. Three structural conditions where CDSA does not operate as intended.

Low psychological safety CDSA requires the observer to exit their current position and see it as a position. In organisations where this exit is structurally unsafe, the problem is not method — it is the conditions. CDSA cannot substitute for them.
Conflicts of interest CDSA works with contradictions as analytical objects. When an architectural tension is actually a conflict between specific people's interests, the required work is political, not diagnostic. Applying CDSA here produces accurate analysis of the wrong object.
Acute time deficit CDSA trades speed for diagnostic precision. In acute crisis conditions where the cost of delay exceeds the cost of misdiagnosis, the framework slows action without improving outcomes.
09
Live investigation

Research program

CDSA is not a finished framework. It is an active research program. The materials below document the investigation as it develops — from initial observations to live cases.

Observation 002 Level 7 is not uniform — three phenomena the field treats as one → The foundational observation behind the three-phenomenon distinction.
Observation 003 Trialogue as phenomenon → How the human + AI + AI configuration gives operational access to the positional level.
Observation 006 Multilogue — when asymmetry is the structure → Position is the unit of analysis — not model identity. The structural extension of trialogue.
Observation 007 Orchestration as methodology — the isomorphism → CDSA and the StratoAtlas multilogue share the same operational schema.
Observation 008 The epistemological stack — memory architecture as research design → Methodology, infrastructure, and memory converge when they share the same operational schema.
Case A-INT-2026-001 Write-access as architectural constraint in multi-agent research workflows → A live case: CDSA applied to the infrastructure of its own development.

Working with a structural contradiction?
Bring a case to the research program.

View research log → Explore the map →