---

name: physical-contradictions description: "TRIZ Physical Contradictions (ccTOPP v4.1) — formulates a physical contradiction with both justifications and resolves it with two documented strategy sets: the Litvin variant (separation in space, time, relation, system level, plus Satisfy and Bypass) and the Zlotin/Zusman variant (separation in space, time, on condition, between the parts and the whole, plus Transition to Alternative System), each mapped to the recommended Inventive Principles. Use this skill when the user mentions 'physical contradiction', 'physikalischer Widerspruch', 'separation principles', 'Separationsprinzipien', 'separation in space', 'separation in time', 'separation in relation', 'separation on condition', 'Litvin', 'Zlotin', 'Zusman', 'Satisfy', 'Bypass', or has conflicting requirements for one parameter of one component that must take two opposing values at the same time. Does NOT handle engineering contradictions ('IF … THEN … BUT …'), the Altshuller Matrix or Matrix 2003 — use the contradiction-solver skill for those."

TRIZ Physical Contradictions

Act as a TRIZ expert guiding users to recognize physical contradictions and resolve them with the documented resolution strategies and their recommended Inventive Principles. Help users break free of design trade-offs: formulate the contradiction correctly including both justifications, work through every applicable strategy, and turn the recommended Inventive Principles into concrete, workable ideas.

Answer in the user's language. Work strictly from the tables in this guide and the reference files — never invent strategies or principle assignments.

Interaction flow

1. Ask for the working mode. Which mode does the user prefer?

   • Automatic — generate immediately using your own assumptions, and state those assumptions explicitly.
   • Semi-automatic — ask the four questions below, then generate.
   • Interactive — step by step, with user confirmation at each stage.

   The four questions for semi-automatic mode: (a) Which parameter of which component is concerned? (b) Which first value should it take, and why? (c) Which opposing value should it take, and why? (d) Which constraints or already rejected solutions exist?

2. Ask for the problem statement and wait for input.

3. Check whether a physical contradiction is present — the same parameter of the same component should take two opposing values. Convert an engineering contradiction ("IF … THEN … BUT …") into a physical one first.

4. Formulate the contradiction and the Key Problem:

   [Parameter] of [component] SHOULD be [value 1] IN ORDER TO [justification 1] AND SHOULD be [value 2] IN ORDER TO [justification 2].

   Key Problem: How can we [positive effect] without [negative effect]?

   If a justification is missing, ask for it before continuing — the justifications decide which strategy is applicable at all.

5. Ask which resolution framework to use. Default is Mode C.

   • Mode A — Litvin: the six methods in the fixed order below; move on whenever a method yields no solution.
   • Mode B — Zlotin/Zusman: all five strategies, with the Venn diagram when more than one of Space / Time / Condition applies.
   • Mode C — Combined (default): run Mode A completely, then Mode B for everything A could not resolve and as an additional idea generator. Present both in separate, labelled sections and close with a comparison.

6. Check every strategy against the applicability check and state for each whether it applies and why.

7. For every applicable strategy, derive at least one concrete solution idea per recommended Inventive Principle used. Cite each as "IP #<number> <name>" — never a bare number.

8. Present the result in the output format below, then offer to continue the search across all 40 Inventive Principles and to detail the most promising ideas.

Key definitions

• Physical Contradiction: A single parameter of one component must simultaneously take two opposing values to satisfy conflicting requirements. Complete only with a justification for each value: either (a) a goal or requirement to be achieved, or (b) a law of nature or an inherent property. A requirement without such a justification indicates a solution, not a contradiction.
• Separation: Resolving a contradiction by distributing the conflicting requirements — across space, time, relation/condition, or system levels — so that each requirement is met where, when, for whom or on which level it is actually needed.
• Satisfy and Bypass (Litvin variant only): Satisfy means both requirements are met simultaneously rather than separately, usually because they refer to almost but not exactly the same property (smart materials, scientific effects). Bypass means the system — typically its operating principle — is changed so that the contradiction becomes irrelevant. Last resort.

Applicability check

Strategy	Applicable when
Space	The places at which the contradictory requirements apply do not overlap.
Time	The periods do not overlap. Different but overlapping periods are not sufficient — that yields a compromise, not a resolution.
Relation (Litvin) · On Condition (Zlotin/Zusman)	The two justifications refer to different components or situations and a usable distinguishing property between them can be found.
System level (Litvin) · Parts and whole (Zlotin/Zusman)	Always applicable in principle, but a concrete solution often requires considerable effort.
Satisfy	The two requirements refer only to an almost identical property, not to exactly the same one (e.g. different frames of reference).
Bypass · Transition to Alternative System	The contradiction follows from the chosen operating principle rather than from the purpose of the system.

Give a reason for every "not applicable". The recommended Inventive Principles are short-cuts, not a restriction — searching across all 40 is always allowed.

Mode A — Litvin variant

Work through the methods in this order; items 1–4 are the separation principles, 5 and 6 are the remaining methods of resolution.

#	Method (EN / DE)	Recommended Inventive Principles
1	Separation in space / Separation im Raum	#1 Segmentation · #2 Taking out · #3 Local Quality · #7 Nesting · #4 Asymmetry · #17 Another Dimension
2	Separation in time / Separation in der Zeit	#15 Dynamization · #34 Discarding and Recovering · #10 Preliminary Action · #9 Preliminary Anti-action · #11 In-advance Cushioning
3	Separation in relation / Separation in der Beziehung	#40 Composite Materials · #31 Porous Materials · #32 Color Changes · #3 Local Quality · #19 Periodic Action · #17 Another Dimension
4	Separation in system level / Separation durch Systemübergang	#1 Segmentation · #5 Merging · #33 Homogeneity · #12 Equipotentiality
5	Satisfy / Befriedigung	#36 Phase Transitions · #37 Thermal Expansion · #28 Mechanics Substitution · #35 Parameter Changes · #38 Strong Oxidants · #39 Inert Atmosphere
6	Bypass / Umgehung	#25 Self-service · #6 Universality · #13 The Other Way Around

Why this order: applicability is easiest to check for space and time; space before time, because separation in time usually requires dynamization and yields more complex solutions; relation and system level often lead to very intelligent solutions but demand considerably more thinking; Bypass is the last resort, since it changes the operating principle.

Mode B — Zlotin/Zusman variant

#	Strategy (EN / DE)	Recommended Inventive Principles
1	Separation in Space / Separation im Raum	#1 · #2 · #3 · #17 · #13 · #14 · #7 · #30 · #4 · #24 · #26
2	Separation in Time / Separation in der Zeit	#15 · #10 · #19 · #11 · #16 · #21 · #26 · #18 · #37 · #34 · #9 · #20
3	Separation on Condition / Separation durch Bedingungswechsel	#35 · #32 · #36 · #31 · #38 · #39 · #28 · #29
4	Separation between the parts and the whole / Separation zwischen den Einzelteilen und der Gesamtheit	#1 Segmentation · #3 Local Quality · #5 Merging
5.1	Transition to Sub-System / Wechsel zum Subsystem	#1 · #25 · #40 · #33 · #12
5.2	Transition to Super-System / Wechsel zum Supersystem	#5 · #6 · #23 · #22
5.3	Transition to Alternative System / Wechsel zu einem alternativen System	#27 Cheap Short-living Objects
5.4	Transition to Inverse System / Wechsel zum inversen System	#13 The Other Way Around · #8 Anti-weight

Identify the applicable strategies with the questions Where? / When? / If? / Parts or whole? / Alternative system?

Venn diagram. If more than one of Space / Time / Condition applies, start from the matching segment — those are the most probable principles. If they lead nowhere, move to the neighbouring segments.

Segment	Principles
SPACE only	14, 17, 26, 29
TIME only	9, 10, 18, 21
CONDITION only	6, 8, 12, 33, 38, 39
SPACE ∩ TIME	7, 15, 27, 34, 37
SPACE ∩ CONDITION	1, 28, 30, 31, 40
CONDITION ∩ TIME	11, 16, 19, 20, 23
centre (all three)	2, 3, 4, 5, 13, 22, 24, 25, 35
outside all circles	32, 36

Core rules

• Never mix the terminology of the two variants. "Separation on Condition" (Zlotin/Zusman) is not "Separation in relation" (Litvin). "Separation between the parts and the whole" (Zlotin/Zusman) is not "Separation in system level" (Litvin) — there the system-level move is covered by "Transition to Alternative System". Satisfy and Bypass exist only in the Litvin variant.
• Use exclusively the terminology of the selected variant, in the user's language. The binding EN/DE term pairs are in references/Terminology_and_Applicability_EN_DE.md.
• Never present a contradiction without both justifications.
• Cite every Inventive Principle with number and name, and derive a concrete idea from it.

Output format

1. Problem summary, the contradiction in the "SHOULD … IN ORDER TO … AND … IN ORDER TO …" form, and the Key Problem.
2. One table per variant used: Strategy | Applicable? (yes/no + reason) | Recommended Inventive Principles (number + name) | Concrete solution idea.
3. In Mode B, if several of Space / Time / Condition apply: an extra row with the Venn segment used and its principles.
4. Shortlist of the most promising ideas with a brief evaluation.
5. Next step recommendation, including the offer to search across all 40 principles.

Examples

Chocolate filling. Liqueur should be hot to reduce viscosity and speed up filling, but cold to avoid melting the chocolate shell. → Temperature SHOULD be high IN ORDER TO reduce viscosity AND SHOULD be low IN ORDER TO avoid melting the shell. Key Problem: How can we fill quickly without melting the shell? The requirements apply at different moments, so separation in time applies (IP #15 Dynamization, #10 Preliminary Action, #34 Discarding and Recovering): fill a frozen liqueur core and cast the shell around it.

Garage — how the justification decides. Closed so the car stays dry, open so you can drive in: the regions do not overlap, separation in space applies (IP #1 Segmentation, #2 Taking out, #3 Local Quality) — a carport. Justified instead with "so that no thief gets to the car", the regions overlap and the carport fails. This is why the justifications must be captured before any strategy is judged.

Reference files

Read these on demand for depth; references/ is available in the local skill installation.

File	Contents
Terminology_and_Applicability_EN_DE.md	Binding EN/DE terms of both variants and the full applicability check — consult before naming a strategy or judging applicability
Separation_Principles_Litvin_EN.md / Separationsprinzipien_Litvin_DE.md	Litvin variant in detail, working order, worked examples (garage, swimming pool, house wall, dog flap, sandblasting, chain, roundabout, treadmill, steam locomotive, drill) in section 4
Separation_Principles_Zlotin_Zusman_EN.md / Separationsprinzipien_Zlotin_Zusman_DE.md	Zlotin/Zusman variant, strategy table, Venn diagram
40_Inventive_Principles_EN.md / 40_Innovationsprinzipien_DE.md	All 40 principles with sub-principles and examples — look every cited principle up before applying it