DA

DA addresses Distributional Gap Bridging—reducing the feature-space mismatch between source and target domains when labeled target data is unavailable or scarce. Its Small Labeled, Unlabeled profile reflects the defining operational condition: the target domain lacks sufficient labeled examples to support task-specific FT, The Parametric Update mechanism operates by training a feature extractor alongside an explicit domain discriminator or statistical divergence minimizer, yielding a Partial footprint (the alignment layers and feature extractor are updated; task heads may remain frozen) ^[66]. The defining taxonomic boundary is DL, FM: at the LLM tier, the DA goal persists but the mechanism is superseded—CPT achieves distributional alignment by continued self-supervised training on unlabeled target-domain corpora, and domain-specific PEFT injects target-domain signal via lightweight adapters. System documentation for LLM-level DA must therefore specify the concrete CPT or PEFT pathway rather than invoking classical DA terminology. At the DL, FM tier, change-control documentation should specify which alignment layers were updated and which domain-discriminator architecture was used, as these define the precise structural boundary of the modification event; regression testing should verify that source-domain performance is preserved alongside target-domain improvement—necessitating a dual-distribution evaluation protocol as part of the validation record.

DA. Stops at DL, FM: the goal of bridging domain gaps persists at the LLM level, but the mechanism is superseded by CPT and domain-specific PEFT. PE vs.\ ICL ( vs. ). While structurally identical on their underlying mechanism (D1), scope (D5), and model tier (D6), and partially overlapping in their goals (D2) and persistence (D4), the shift in data requirements (Zero-Shot vs. Few Demonstrations) causes their profiles to diverge. ICL uniquely introduces Task Specialization, while PE distinctly extends to Behavior Control and Version-Persistent implementations.