Translation is not copying vocabulary into new clothing#
When a framework moves into a new context, the temptation is to keep the words and ignore the origin. That creates a false sense of fidelity. The terminology remains visible, but the purpose, constraint set, and interpretive lineage may already be gone.
Respect for origin means asking what problem the framework was built to solve, what it was not built to solve, and what assumptions give it meaning. Without that respect, translation becomes distortion with good manners.
Why origin matters#
Frameworks are not free-floating vocabularies. They emerge from questions, traditions, and boundaries. If those boundaries are erased during translation, the framework may sound portable while losing its center.
This is especially important in cross-domain work. Moving a concept from one field to another can be valuable, but only if the receiving context does not pretend the concept arrived without history.
UKM matters because it keeps knowledge relations explicit. MoM matters because translation among frameworks needs a larger structure to keep the relations accountable.
Practical takeaway#
Before translating a framework, ask:
- what question gave rise to it
- what limits shaped it
- what would be lost if it were simplified
- what still needs to remain visible in the new context
Respect for origin is what keeps translation from becoming extraction.