Core Idea
Framework translation is the discipline of turning external requirements into internal operating language. Frameworks are maps; the organisation is the terrain. The companion should teach the learner to preserve intent while changing vocabulary, ownership, artefacts, and workflow.
For example, a framework may ask for access control, but engineering needs to know which repository, cloud role, production path, and approval pattern is in scope. The Companion should teach learners to translate intent into the local nouns that operators recognise.
Use In Teaching
Invoke this card when the learner is mapping ISO, SOC 2, NIST, CMMC, FedRAMP, or customer requirements into real work. It is especially useful for non-technical learners who need to communicate with engineering.
Use it to make learners practise bilingual GRC. They should be able to explain the same requirement in framework language, engineering language, executive language, and audit language. The learning goal is not memorising mappings; it is reducing translation loss while preserving intent.
A reviewer should check that Framework Translation leaves the learner with one artefact to inspect, one assumption to test, and one behaviour to observe in their local context. That keeps the concept practical instead of turning it into vocabulary.
Contrast
This is not one-to-one control mapping. It pushes back against documentation preceding reality. A mapped requirement is only useful when it lands in a system that can execute or verify it.
Practice Prompt
Take one framework requirement and translate it into the language of the team that would actually satisfy it.