NOTE
Adapter Pattern
Translating one interface/protocol/data model into the contract expected by a client.
This is a historical learning note and may contain outdated or incomplete understanding.
An adapter converts an existing component’s interface or data model into the one a client expects. It is common at external-service, persistence, legacy, and framework boundaries.
Keep translation logic at the boundary so external concepts do not leak through the core domain. An adapter should make semantic differences explicit rather than silently pretending incompatible contracts are identical.