Adapter
Definitions
An implementation of a Block for one platform flavor — vanilla, declarative, AEM as a Cloud Service — written against the published contract rather than ported from another adapter
Three adapters of one Component Contract, each from the contract, are how the contract is tested: if they agree, the contract said enough.
The whole family of realizations for one output channel — web, Figma, email, banner and display, interactive sales aids — consuming the Core and knowing everything about its channel that the Core deliberately does not
The Agentic DS draft's sense: every channel is an adapter, not a separate system. Compatible with the cwds sense — a channel adapter is made of realization adapters — and wider.
The word for a realization that was written from the contract. Porting an adapter from another adapter tests nothing; writing each from the Component Contract's anatomy and token contract tests the contract.