negative transfer

**Negative transfer** is **performance loss on a target task due to harmful influence from unrelated or conflicting tasks** - Shared parameters absorb incompatible patterns that reduce specialization quality for specific objectives. **What Is Negative transfer?** - **Definition**: Performance loss on a target task due to harmful influence from unrelated or conflicting tasks. - **Core Mechanism**: Shared parameters absorb incompatible patterns that reduce specialization quality for specific objectives. - **Operational Scope**: It is applied during data scheduling, parameter updates, or architecture design to preserve capability stability across many objectives. - **Failure Modes**: If not detected early, negative transfer can waste compute and mask useful architectural choices. **Why Negative transfer Matters** - **Retention and Stability**: It helps maintain previously learned behavior while new tasks are introduced. - **Transfer Efficiency**: Strong design can amplify positive transfer and reduce duplicate learning across tasks. - **Compute Use**: Better task orchestration improves return from fixed training budgets. - **Risk Control**: Explicit monitoring reduces silent regressions in legacy capabilities. - **Program Governance**: Structured methods provide auditable rules for updates and rollout decisions. **How It Is Used in Practice** - **Design Choice**: Select the method based on task relatedness, retention requirements, and latency constraints. - **Calibration**: Track per-task deltas versus isolated baselines and rebalance or separate tasks when persistent regressions appear. - **Validation**: Track per-task gains, retention deltas, and interference metrics at every major checkpoint. Negative transfer is **a core method in continual and multi-task model optimization** - It defines the downside boundary for aggressive task sharing.