Revision 7T · Full Tutorial Edition · Updated 1 September 2026
PWR-132 · SELF GUIDED full tutorial
Combine selected authorised features and test the emergent function
Conceptual blending selectively combines elements and relations from two inputs so the result has an emergent feature. It is not hiding copied material inside a mixture. This lesson blends a generic bookmark and luggage tag for a reading-retrieval problem. The learner records lineage, selects relevant features, resolves contradictions, states what emerges only in the blend and tests coherence against the brief.
What you will produceThe learner creates two traceable blends whose emergent function, input lineage, contradictions and feasibility can be independently checked.
Blend generic, owned, licensed or public-domain inputs for benign fictional tasks.
Reject a blend that is surprising but incoherent.
Qualified help is required for
Regulated, medical, safety-critical or consequential design.
Use of protected characters, living-artist style, proprietary form or culturally governed motif.
Never do this from the page alone
Strip attribution or treat obscured copying as originality.
Build powered, structural or hazardous blends under this lesson.
2 · Get ready
Gather what you need and check the starting conditions
What you need
Generic bookmark and luggage-tag input cards with source-status fields.
Feature–relation–lineage table, contradiction checklist and benign reading brief.
Paper and card for an optional non-functional sketch or mock-up.
Before you start
Verify each input is generic, owned, licensed or public domain.
State the target: retrieve both page location and reason for marking.
Keep attribution beside every selected feature.
3 · The method
Follow these steps in order
Decompose each input
List parts, relations, functions and constraints of the bookmark and tag separately.
Why: Decomposition prevents the blend from becoming two objects merely stuck together.
Check: Each input has at least three features and one relation.
Select relevant features
Choose only features that address the target and record their input lineage.
Why: Selective projection keeps the blend coherent and traceable.
Check: Every chosen feature has a target reason and source.
Cross-map compatible roles
Align page marker with location function and tag panel with identification or note function.
Why: Compatible roles create a meaningful connection between inputs.
Check: The cross-map is expressed as a functional relation.
Generate rival blends
Create at least two selective combinations that use different feature sets, such as a removable note tab and a coded tab linked to a separate note card.
Why: Multiple blends reveal whether the first combination was merely the most obvious.
Check: Both rivals preserve lineage and solve the same target through meaningfully different relations.
Generate the emergent feature
Describe what becomes possible only in combination, such as retrieving both place and reading purpose.
Why: Emergence distinguishes a blend from a list of parts.
Check: The claim is absent from each input alone and relevant to the target.
Compare with unblended baselines
Apply the target walkthrough to the bookmark alone and tag alone before scoring the blends. Record which target need each input already solves and which remains unmet.
Why: A blend is emergent only if the claimed added function exceeds what either input already supplies under the same test.
Check: The chosen blend demonstrates one target-relevant capability absent from both baseline inputs, or the emergence claim is withdrawn.
Walk through a use sequence
For each rival, describe insertion, page closing, later retrieval, note reading and removal. Mark any point where a source feature conflicts with the actual sequence.
Why: A concrete sequence tests coherence better than an attractive static description.
Check: One rival is retained or revised using a named failure from the same five-action walkthrough.
Test contradictions
Check thickness, page damage, note privacy, attachment and removability; revise or reject conflicting features.
Why: A clever concept can fail through incompatible constraints.
Check: Every contradiction has a repair, test or rejection.
Preserve lineage and transfer
Make a paper sketch with lineage labels, then after 48 hours blend two different authorised inputs for a new benign problem.
Why: Lineage supports rights and reconstruction; a new task tests method transfer.
Check: A reviewer can trace features and identify the new emergent function.
4 · Worked example
See the whole method used once
Scenario
A reader wants a page marker that also recalls why the page mattered.
Walkthrough
Bo lists bookmark features: thin, stays in a book, marks location; tag features: visible tab, writable identity, attachment loop.
He selects thin marker, visible removable tab and small writable panel, keeping both source labels.
He cross-maps page location with item identity.
The emergent function is retrieving location and reading purpose together.
He flags thickness and note privacy, then revises to a removable folded tab with the note facing inward.
Result
Bo has a coherent traceable concept with a real emergent function and recorded trade-offs. It is not evidence of market value or a protected product right.
5 · Right and wrong
Compare correct or safer execution with the common wrong version
Right and wrong comparison
Moment
Right / safer
Wrong / riskier
Why it matters
Inputs
Use authorised generic features with lineage.
Blend recognisable protected characters or product forms.
Mixture does not erase rights or attribution.
Selection
Project only target-relevant features.
Include every feature from both inputs.
Unselective combination creates clutter and contradiction.
Emergence
Name a function possible only in the blend.
Call two attached objects an emergent concept.
Physical juxtaposition alone is not conceptual integration.
Evaluation
Test coherence and trade-offs.
Reward surprise even when the brief fails.
Novelty without function is not a successful blend here.
6 · Common mistakes
Spot the error and apply the correction
Common mistakes and corrections
Mistake
Fix
One input dominates completely.
Require one meaningful relation or constraint from each input.
Lineage disappears in the sketch.
Tag each feature with input A, input B or emergent.
Emergence restates a source function.
Ask what the combined structure newly enables.
Contradictions are treated as future details.
Resolve, test or explicitly reject each before scoring coherence.
7 · Practice
Turn the steps into a usable skill
First session
Decompose two authorised inputs.
Select and trace features.
Cross-map roles.
State one emergent function.
Run contradiction and rights checks.
Repeat plan
Create one blend weekly for four weeks using different benign input pairs. Delay the transfer blend by at least 48 hours and have a reviewer identify lineage without prompting.
Progress when
Both inputs contribute a meaningful relation.
The emergent feature is clear to an independent reviewer.
Lineage and contradictions remain visible.
Do not progress when
Inputs lack rights, attribution or cultural permission.
The blend is hazardous, regulated or consequential.
Surprise is being used to excuse incoherence.
8 · Check the result
Measure what changed
Independent ratings of lineage, coherence and emergent function.
How: A reviewer scores correct feature lineage, contribution from both inputs, target relevance, emergent function, contradiction handling and feasibility on a six-part rubric.
Good result: A reviewer can trace both inputs, identify the target-relevant emergent function and reproduce how contradictions were repaired on two new blends; unresolved rights or hard-safety issues stop the blend. Reviewer disagreement remains visible rather than being forced through a five-of-six pass rule.
This does not prove: It does not establish objective originality, real invention, user demand or legal permission beyond the declared inputs.
Self-check
Which feature came from each input?
What relation is cross-mapped?
What exists only in the blend?
Which contradiction could make it fail?
9 · Stop, adapt or get help
Keep the safety boundary practical
Stop and get help
Stop if input ownership, licence or cultural authority is unclear.
Stop if the concept becomes medical, powered, load-bearing, transport or otherwise hazardous.
Seek rights, domain and affected-user review before real development.
Accessibility and adaptations
Use a text lineage table and verbal concept description.
Allow tactile paper parts or large-print cards.
Offer one input at a time, then a structured cross-map prompt.
10 · Evidence and limits
Why these instructions are here
primary research
The Fusion Innovation Test provides a paradigm for studying real-world creative problem solving but is measurement evidence, not a proven general training route.
Progress is saved only in this browser on this device.
Step-by-step learner mode
Each activity includes its success check, a nearby accessible alternative and an “I’m stuck” correction path. Alternatives preserve the target where possible; when they change the task, Titan labels them as related rather than equivalent.
01
Decompose each input
List parts, relations, functions and constraints of the bookmark and tag separately.
Why this step exists
Decomposition prevents the blend from becoming two objects merely stuck together.
Success check
Each input has at least three features and one relation.
I’m stuck on this step
Reset: Re-read this authored instruction — “List parts, relations, functions and constraints of the bookmark and tag separately.” — and its success check, then attempt only this step.
Possible snag: One input dominates completely.
Correction: Require one meaningful relation or constraint from each input.
Stop / get help: Stop if input ownership, licence or cultural authority is unclear.
02
Select relevant features
Choose only features that address the target and record their input lineage.
Why this step exists
Selective projection keeps the blend coherent and traceable.
Success check
Every chosen feature has a target reason and source.
I’m stuck on this step
Reset: Re-read this authored instruction — “Choose only features that address the target and record their input lineage.” — and its success check, then attempt only this step.
Possible snag: The result from “Choose only features that address the target and record their input lineage.” does not yet meet this declared check: Every chosen feature has a target reason and source.
Correction: Return to the start of “Select relevant features”, reduce complexity or pace, and repeat only the part needed to satisfy: “Every chosen feature has a target reason and source.”
Stop / get help: Stop if input ownership, licence or cultural authority is unclear.
03
Cross-map compatible roles
Align page marker with location function and tag panel with identification or note function.
Why this step exists
Compatible roles create a meaningful connection between inputs.
Success check
The cross-map is expressed as a functional relation.
I’m stuck on this step
Reset: Re-read this authored instruction — “Align page marker with location function and tag panel with identification or note function.” — and its success check, then attempt only this step.
Possible snag: Emergence restates a source function.
Correction: Ask what the combined structure newly enables.
Stop / get help: Stop if input ownership, licence or cultural authority is unclear.
04
Generate rival blends
Create at least two selective combinations that use different feature sets, such as a removable note tab and a coded tab linked to a separate note card.
Why this step exists
Multiple blends reveal whether the first combination was merely the most obvious.
Success check
Both rivals preserve lineage and solve the same target through meaningfully different relations.
I’m stuck on this step
Reset: Re-read this authored instruction — “Create at least two selective combinations that use different feature sets, such as a removable note tab and a coded tab linked to a separate note card.” — and its success check, then attempt only this step.
Possible snag: The result from “Create at least two selective combinations that use different feature sets, such as a removable note tab and a coded tab linked to a separate note card.” does not yet meet this declared check: Both rivals preserve lineage and solve the same target through meaningfully different relations.
Correction: Return to the start of “Generate rival blends”, reduce complexity or pace, and repeat only the part needed to satisfy: “Both rivals preserve lineage and solve the same target through meaningfully different relations.”
Stop / get help: Stop if input ownership, licence or cultural authority is unclear.
05
Generate the emergent feature
Describe what becomes possible only in combination, such as retrieving both place and reading purpose.
Why this step exists
Emergence distinguishes a blend from a list of parts.
Success check
The claim is absent from each input alone and relevant to the target.
I’m stuck on this step
Reset: Re-read this authored instruction — “Describe what becomes possible only in combination, such as retrieving both place and reading purpose.” — and its success check, then attempt only this step.
Possible snag: The result from “Describe what becomes possible only in combination, such as retrieving both place and reading purpose.” does not yet meet this declared check: The claim is absent from each input alone and relevant to the target.
Correction: Return to the start of “Generate the emergent feature”, reduce complexity or pace, and repeat only the part needed to satisfy: “The claim is absent from each input alone and relevant to the target.”
Stop / get help: Stop if input ownership, licence or cultural authority is unclear.
06
Compare with unblended baselines
Apply the target walkthrough to the bookmark alone and tag alone before scoring the blends. Record which target need each input already solves and which remains unmet.
Why this step exists
A blend is emergent only if the claimed added function exceeds what either input already supplies under the same test.
Success check
The chosen blend demonstrates one target-relevant capability absent from both baseline inputs, or the emergence claim is withdrawn.
I’m stuck on this step
Reset: Re-read this authored instruction — “Apply the target walkthrough to the bookmark alone and tag alone before scoring the blends. Record which target need each input already solves and which remains unmet.” — and its success check, then attempt only this step.
Possible snag: Lineage disappears in the sketch.
Correction: Tag each feature with input A, input B or emergent.
Possible snag: Contradictions are treated as future details.
Correction: Resolve, test or explicitly reject each before scoring coherence.
Stop / get help: Stop if input ownership, licence or cultural authority is unclear.
07
Walk through a use sequence
For each rival, describe insertion, page closing, later retrieval, note reading and removal. Mark any point where a source feature conflicts with the actual sequence.
Why this step exists
A concrete sequence tests coherence better than an attractive static description.
Success check
One rival is retained or revised using a named failure from the same five-action walkthrough.
I’m stuck on this step
Reset: Re-read this authored instruction — “For each rival, describe insertion, page closing, later retrieval, note reading and removal. Mark any point where a source feature conflicts with the actual sequence.” — and its success check, then attempt only this step.
Possible snag: The result from “For each rival, describe insertion, page closing, later retrieval, note reading and removal. Mark any point where a source feature conflicts with the actual sequence.” does not yet meet this declared check: One rival is retained or revised using a named failure from the same five-action walkthrough.
Correction: Return to the start of “Walk through a use sequence”, reduce complexity or pace, and repeat only the part needed to satisfy: “One rival is retained or revised using a named failure from the same five-action walkthrough.”
Stop / get help: Stop if input ownership, licence or cultural authority is unclear.
08
Test contradictions
Check thickness, page damage, note privacy, attachment and removability; revise or reject conflicting features.
Why this step exists
A clever concept can fail through incompatible constraints.
Success check
Every contradiction has a repair, test or rejection.
I’m stuck on this step
Reset: Re-read this authored instruction — “Check thickness, page damage, note privacy, attachment and removability; revise or reject conflicting features.” — and its success check, then attempt only this step.
Possible snag: The result from “Check thickness, page damage, note privacy, attachment and removability; revise or reject conflicting features.” does not yet meet this declared check: Every contradiction has a repair, test or rejection.
Correction: Return to the start of “Test contradictions”, reduce complexity or pace, and repeat only the part needed to satisfy: “Every contradiction has a repair, test or rejection.”
Stop / get help: Stop if input ownership, licence or cultural authority is unclear.
09
Preserve lineage and transfer
Make a paper sketch with lineage labels, then after 48 hours blend two different authorised inputs for a new benign problem.
Why this step exists
Lineage supports rights and reconstruction; a new task tests method transfer.
Success check
A reviewer can trace features and identify the new emergent function.
I’m stuck on this step
Reset: Re-read this authored instruction — “Make a paper sketch with lineage labels, then after 48 hours blend two different authorised inputs for a new benign problem.” — and its success check, then attempt only this step.
Possible snag: The result from “Make a paper sketch with lineage labels, then after 48 hours blend two different authorised inputs for a new benign problem.” does not yet meet this declared check: A reviewer can trace features and identify the new emergent function.
Correction: Return to the start of “Preserve lineage and transfer”, reduce complexity or pace, and repeat only the part needed to satisfy: “A reviewer can trace features and identify the new emergent function.”
Stop / get help: Stop if input ownership, licence or cultural authority is unclear.
Correct versus incorrect execution
These accessible process diagrams are built from the tutorial’s own right/wrong teaching. They are not anatomical illustrations and do not add technique beyond the canonical tutorial.
Inputs — Mixture does not erase rights or attribution.
Correct / safer
Use authorised generic features with lineage.
Wrong / riskier
Blend recognisable protected characters or product forms.
Selection — Unselective combination creates clutter and contradiction.
Correct / safer
Project only target-relevant features.
Wrong / riskier
Include every feature from both inputs.
Emergence — Physical juxtaposition alone is not conceptual integration.
Correct / safer
Name a function possible only in the blend.
Wrong / riskier
Call two attached objects an emergent concept.
Evaluation — Novelty without function is not a successful blend here.
Correct / safer
Test coherence and trade-offs.
Wrong / riskier
Reward surprise even when the brief fails.
Method-structure checklist
10 of 10 structural checks present
✓ Ordered, Power-specific instructions — present
✓ Every activity has a success check — present
✓ Materials or supplied records are declared — present
✓ Measurement or assessment rule is present — present
✓ Tutorial-specific troubleshooting is present — present
✓ Stopping or escalation boundary is present — present
✓ Every activity has an adjacent alternative — present
✓ Correct-versus-incorrect comparison is present — present
✓ Evidence context is bound to the Power record — present
✓ Planning metadata is present — present
The method-readiness band and presence checklist assess tutorial presentation and are separate from evidence quality for the underlying Power. They are automated editorial aids, not human approval.
Manual editorial sign-off: Pending. This tutorial must not display a human-approved state until an identified editor signs the exact content hash.