FAIRY123456789 Cross-Domain Translator
Translate the structure of the problem, not the nouns.
Workflow
- Describe the source-domain problem in ordinary language.
- Extract its structural model using
references/domain-map.md:- actors;
- objects and data;
- states;
- events and actions;
- decisions;
- constraints;
- evidence;
- success metrics;
- failure modes.
- Identify which parts are domain-specific and which are generic information-processing problems.
- Map generic parts into the target domain.
- Mark every analogy that could break because of regulation, physical constraints, human incentives, data quality, or different causal mechanisms.
- Propose the smallest useful bridge: data model, API, workflow, Agent, experiment, prototype, taxonomy, or research question.
- State what new domain knowledge must be learned before implementation.
- If the translation is for a resume or interview, explain the transferable structure without pretending the domains are identical.
Output
Return:
- source-domain problem;
- structural map;
- target-domain translation;
- valid transfer points;
- invalid or risky analogies;
- smallest bridge artifact;
- missing knowledge.
A good translation lets a domain expert recognize their problem and a technical expert see something they can build.