Section 313 of 440
Complete canonical tutorial. This reader section contains the same teaching body as PWR-131 · Analogical transfer. Open the Power dossier.
PWR-131 · SELF GUIDED full tutorial
Map shared relations from two analogues and state where transfer fails
Analogical transfer uses a source situation to expose a relationship that may help a target. Surface resemblance is not enough. This lesson compares two authorised generic mechanisms—a retractable badge reel and a window blind—to the cable-reach problem. The learner maps roles and relations, extracts the common principle, names mismatches, transfers only the supported relation and tests a misleading near match.
1 · Permission and limits
Know exactly what you may do
2 · Get ready
Gather what you need and check the starting conditions
What you need
- Source cards for a generic retractable badge reel and window blind, written without brands or copied drawings.
- Cable target brief, role–relation mapping table and mismatch sheet.
- A misleading surface-similar source card and delayed new target.
Before you start
- Verify source status and preserve attribution.
- Write the target function and hard constraints.
- Agree that the analogy may suggest a test but cannot approve a design.
3 · The method
Follow these steps in order
- Describe sources structurally
For each source, list goal, parts, relations, change over time and user action without product-specific decoration.
Why: Structural descriptions reduce surface fixation.
Check: Each source has roles and relations, not just nouns.
- Align corresponding roles
Map loose object, anchor, stored slack, restoring force and user action across both sources.
Why: Role alignment exposes the common mechanism.
Check: Every mapped pair serves the same relational function.
- Extract the shared principle
Write one abstract sentence that is true of both sources, such as store slack and return a loose end using bounded restoring force.
Why: An explicit schema is easier to transfer than an example image.
Check: The principle contains relations and constraints.
- Map to the target
Assign target components to each role and generate at least two cable concepts.
Why: Target mapping turns a principle into testable possibilities.
Check: Each concept shows all required roles.
- Predict target behaviour
Before any mock-up, state what each mapped relation predicts under a simple paper-cable pull and what observation would contradict the analogy.
Why: A prediction turns structural resemblance into a target-specific claim that can fail.
Check: Every concept has one predicted behaviour and one disconfirming result written in advance.
- List mismatches and hazards
Write at least three differences in scale, force, electrical safety, surfaces or failure consequences.
Why: Negative transfer occurs when source rules are copied across important differences.
Check: Every mismatch has a test or rejection implication.
- Reverse-map the target
Starting with each proposed cable component, trace backward to the source role and shared principle. Mark any component that has no source relation or any source relation that lacks a target counterpart.
Why: Reverse mapping exposes forced correspondences and decorative features added after the analogy.
Check: Every retained target feature either maps cleanly or is labelled a separate non-analogical design hypothesis.
- Compare a rival analogy
Map a second source that suggests a different mechanism, such as a loose storage pocket, and compare which target relations each captures or misses.
Why: A rival prevents the first coherent analogy from monopolising the explanation.
Check: The chosen schema wins on declared target relations, or both remain as distinct hypotheses rather than being blended silently.
- Challenge and transfer later
Compare a misleading surface-similar source, reject it by relation, then after 48 hours apply the schema to storing headphone-cable slack.
Why: A foil and delayed target test relational rather than surface transfer.
Check: The learner explains both rejection and new mapping.
4 · Worked example
See the whole method used once
Scenario
The target is keeping a charging-cable end reachable without changing the electrical device.
Walkthrough
- Mei maps stored slack and return force in both the badge reel and blind.
- She writes the shared principle: store excess line and return the free end with a bounded restoring force.
- She maps anchor to desk, stored slack to a passive spool and free end to the connector.
- She lists cable thickness, connector strain and desk attachment as mismatches requiring tests.
- She rejects a decorative coiled cable as a near match because it lacks controlled storage and later maps the principle to headphones.
Result
Mei transfers a relation and names failure boundaries. She has not shown that any physical prototype is safe or non-infringing.
5 · Right and wrong
Compare correct or safer execution with the common wrong version
| Moment | Right / safer | Wrong / riskier | Why it matters |
|---|---|---|---|
| Similarity | Map goals and relations. | Choose a source because it looks like a cable. | Surface resemblance can hide a different mechanism. |
| Sources | Compare two structurally similar but visibly different examples. | Memorise one vivid example. | Two sources help abstract the shared schema. |
| Mismatch | Write where force, scale and safety differ. | Copy every source feature. | Unexamined differences cause negative transfer. |
| Evidence | Use the analogy to propose a test. | Treat it as proof the target solution works. | Analogy generates hypotheses; target evidence evaluates them. |
6 · Common mistakes
Spot the error and apply the correction
| Mistake | Fix |
|---|---|
| Roles are replaced with object names. | Use functional labels such as anchor, stored slack and restoring force. |
| One source dominates the principle. | Keep only relations present in both sources. |
| Mismatches are generic. | Name the target-specific failure and what test would expose it. |
| Protected drawings are copied. | Use authorised generic text descriptions and preserve source status. |
7 · Practice
Turn the steps into a usable skill
First session
- Map two authorised source mechanisms.
- Extract one shared schema.
- Generate two target mappings.
- List three mismatches.
- Reject one misleading near match.
Repeat plan
Complete one two-source mapping weekly for four weeks. After 48 hours, transfer the schema to a new benign target without the source cards. Keep target-test results separate from mapping quality.
Progress when
- Role relations, not surfaces, drive the mapping.
- At least three consequential mismatches are identified.
- The schema transfers to a fresh target or is correctly rejected.
Do not progress when
- Sources are proprietary, confidential or culturally governed.
- The target is safety-critical or regulated.
- The analogy substitutes for target evidence.
8 · Check the result
Measure what changed
Correct relational mapping and mismatch detection on a novel target.
How: Using a declared rubric, score role alignment, shared principle, target mapping, three concrete mismatches, foil rejection and target-specific test.
Good result: Every retained mapping traces source role to target role, every consequential mismatch has a test or rejection implication, and the foil is accepted or rejected by relation rather than appearance on two delayed targets. No safety mismatch may remain hidden, and no five-of-six cutoff is treated as general transfer skill.
This does not prove: It does not show the target works, grant source rights or establish broad creative transfer.
Self-check
- What relation is shared by both sources?
- Which target part fills each role?
- Where does the analogy break?
- What result would show negative transfer?
9 · Stop, adapt or get help
Keep the safety boundary practical
Stop and get help
- Stop if the source is confidential, proprietary or culturally restricted.
- Stop if a mismatch creates electrical, structural, medical or other hazard.
- Seek domain, rights and affected-person review before prototype or implementation.
Accessibility and adaptations
- Use a text role table instead of diagrams.
- Provide tactile objects only when safe and authorised.
- Allow spoken mapping and a scribe with relation prompts.
10 · Evidence and limits
Why these instructions are here
- primary research
Classic schema-induction research found comparison of examples can support analogical transfer, while one-example conditions often fail spontaneously.
Schema induction and analogical transfer - primary research
Analogical encoding improved knowledge transfer in a defined negotiation study, supporting structured comparison without proving universal transfer.
Analogical encoding facilitates knowledge transfer in negotiation
Limits
- Analogies preserve selected relations, not every feature.
- A correct mapping can still produce an unsafe or ineffective target.
- Source rights, domain evidence and target testing remain separate gates.
Open the complete canonical research register
- Primary empirical supportLimiting / contrarySchema induction and analogical transfer
Mary L. Gick; Keith J. Holyoak · 1983 · Primary research
- Primary empirical supportLimiting / contraryAnalogical encoding facilitates knowledge transfer in negotiation
Loewenstein J; Thompson L; Gentner D · 1999 · Primary research
- Limiting / contraryOfficial boundary contextCopyright and Artificial Intelligence
United States Copyright Office · 2025 · Official guidance
- Limiting / contraryOfficial boundary contextTraditional Cultural Expressions
World Intellectual Property Organization · 2026 · Official governance
Read the complete evidence interpretation on the Power dossier.
Tutorial delivery controls
Learn, adapt, troubleshoot and resume
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.
Describe sources structurally
For each source, list goal, parts, relations, change over time and user action without product-specific decoration.
Structural descriptions reduce surface fixation.
Each source has roles and relations, not just nouns.
I’m stuck on this step
Reset: Re-read this authored instruction — “For each source, list goal, parts, relations, change over time and user action without product-specific decoration.” — and its success check, then attempt only this step.
Possible snag: One source dominates the principle.
Correction: Keep only relations present in both sources.
Possible snag: Protected drawings are copied.
Correction: Use authorised generic text descriptions and preserve source status.
Stop / get help: Stop if the source is confidential, proprietary or culturally restricted.
Align corresponding roles
Map loose object, anchor, stored slack, restoring force and user action across both sources.
Role alignment exposes the common mechanism.
Every mapped pair serves the same relational function.
I’m stuck on this step
Reset: Re-read this authored instruction — “Map loose object, anchor, stored slack, restoring force and user action across both sources.” — and its success check, then attempt only this step.
Possible snag: Roles are replaced with object names.
Correction: Use functional labels such as anchor, stored slack and restoring force.
Stop / get help: Stop if the source is confidential, proprietary or culturally restricted.
Extract the shared principle
Write one abstract sentence that is true of both sources, such as store slack and return a loose end using bounded restoring force.
An explicit schema is easier to transfer than an example image.
The principle contains relations and constraints.
I’m stuck on this step
Reset: Re-read this authored instruction — “Write one abstract sentence that is true of both sources, such as store slack and return a loose end using bounded restoring force.” — and its success check, then attempt only this step.
Possible snag: The result from “Write one abstract sentence that is true of both sources, such as store slack and return a loose end using bounded restoring force.” does not yet meet this declared check: The principle contains relations and constraints.
Correction: Return to the start of “Extract the shared principle”, reduce complexity or pace, and repeat only the part needed to satisfy: “The principle contains relations and constraints.”
Stop / get help: Stop if the source is confidential, proprietary or culturally restricted.
Map to the target
Assign target components to each role and generate at least two cable concepts.
Target mapping turns a principle into testable possibilities.
Each concept shows all required roles.
I’m stuck on this step
Reset: Re-read this authored instruction — “Assign target components to each role and generate at least two cable concepts.” — and its success check, then attempt only this step.
Possible snag: The result from “Assign target components to each role and generate at least two cable concepts.” does not yet meet this declared check: Each concept shows all required roles.
Correction: Return to the start of “Map to the target”, reduce complexity or pace, and repeat only the part needed to satisfy: “Each concept shows all required roles.”
Stop / get help: Stop if the source is confidential, proprietary or culturally restricted.
Predict target behaviour
Before any mock-up, state what each mapped relation predicts under a simple paper-cable pull and what observation would contradict the analogy.
A prediction turns structural resemblance into a target-specific claim that can fail.
Every concept has one predicted behaviour and one disconfirming result written in advance.
I’m stuck on this step
Reset: Re-read this authored instruction — “Before any mock-up, state what each mapped relation predicts under a simple paper-cable pull and what observation would contradict the analogy.” — and its success check, then attempt only this step.
Possible snag: Mismatches are generic.
Correction: Name the target-specific failure and what test would expose it.
Stop / get help: Stop if the source is confidential, proprietary or culturally restricted.
List mismatches and hazards
Write at least three differences in scale, force, electrical safety, surfaces or failure consequences.
Negative transfer occurs when source rules are copied across important differences.
Every mismatch has a test or rejection implication.
I’m stuck on this step
Reset: Re-read this authored instruction — “Write at least three differences in scale, force, electrical safety, surfaces or failure consequences.” — and its success check, then attempt only this step.
Possible snag: The result from “Write at least three differences in scale, force, electrical safety, surfaces or failure consequences.” does not yet meet this declared check: Every mismatch has a test or rejection implication.
Correction: Return to the start of “List mismatches and hazards”, reduce complexity or pace, and repeat only the part needed to satisfy: “Every mismatch has a test or rejection implication.”
Stop / get help: Stop if the source is confidential, proprietary or culturally restricted.
Reverse-map the target
Starting with each proposed cable component, trace backward to the source role and shared principle. Mark any component that has no source relation or any source relation that lacks a target counterpart.
Reverse mapping exposes forced correspondences and decorative features added after the analogy.
Every retained target feature either maps cleanly or is labelled a separate non-analogical design hypothesis.
I’m stuck on this step
Reset: Re-read this authored instruction — “Starting with each proposed cable component, trace backward to the source role and shared principle. Mark any component that has no source relation or any source relation that lacks a target counterpart.” — and its success check, then attempt only this step.
Possible snag: The result from “Starting with each proposed cable component, trace backward to the source role and shared principle. Mark any component that has no source relation or any source relation that lacks a target counterpart.” does not yet meet this declared check: Every retained target feature either maps cleanly or is labelled a separate non-analogical design hypothesis.
Correction: Return to the start of “Reverse-map the target”, reduce complexity or pace, and repeat only the part needed to satisfy: “Every retained target feature either maps cleanly or is labelled a separate non-analogical design hypothesis.”
Stop / get help: Stop if the source is confidential, proprietary or culturally restricted.
Compare a rival analogy
Map a second source that suggests a different mechanism, such as a loose storage pocket, and compare which target relations each captures or misses.
A rival prevents the first coherent analogy from monopolising the explanation.
The chosen schema wins on declared target relations, or both remain as distinct hypotheses rather than being blended silently.
I’m stuck on this step
Reset: Re-read this authored instruction — “Map a second source that suggests a different mechanism, such as a loose storage pocket, and compare which target relations each captures or misses.” — and its success check, then attempt only this step.
Possible snag: The result from “Map a second source that suggests a different mechanism, such as a loose storage pocket, and compare which target relations each captures or misses.” does not yet meet this declared check: The chosen schema wins on declared target relations, or both remain as distinct hypotheses rather than being blended silently.
Correction: Return to the start of “Compare a rival analogy”, reduce complexity or pace, and repeat only the part needed to satisfy: “The chosen schema wins on declared target relations, or both remain as distinct hypotheses rather than being blended silently.”
Stop / get help: Stop if the source is confidential, proprietary or culturally restricted.
Challenge and transfer later
Compare a misleading surface-similar source, reject it by relation, then after 48 hours apply the schema to storing headphone-cable slack.
A foil and delayed target test relational rather than surface transfer.
The learner explains both rejection and new mapping.
I’m stuck on this step
Reset: Re-read this authored instruction — “Compare a misleading surface-similar source, reject it by relation, then after 48 hours apply the schema to storing headphone-cable slack.” — and its success check, then attempt only this step.
Possible snag: The result from “Compare a misleading surface-similar source, reject it by relation, then after 48 hours apply the schema to storing headphone-cable slack.” does not yet meet this declared check: The learner explains both rejection and new mapping.
Correction: Return to the start of “Challenge and transfer later”, reduce complexity or pace, and repeat only the part needed to satisfy: “The learner explains both rejection and new mapping.”
Stop / get help: Stop if the source is confidential, proprietary or culturally restricted.
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.
Map goals and relations.
Choose a source because it looks like a cable.
Compare two structurally similar but visibly different examples.
Memorise one vivid example.
Write where force, scale and safety differ.
Copy every source feature.
Use the analogy to propose a test.
Treat it as proof the target solution works.
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.