Calculation type
A calculation type declared in the taxonomy, data model, and admin UI schema whose description says it should 'increase charges if allowed amount is greater,' but for which no execution logic exists anywhere in CalculationEngine.cs -- selecting it in a FeeLogic will throw at calculation time.
Dead code
No dispatch arm exists for this type, so configuring it throws at pricing time — yet it remains selectable in the UI.
Gotchas
Confirmed dead code by direct inspection of the ApplyAdjustment switch in CalculationEngine.cs (case arms enumerated from line 731 through the MidLevelProviderAdjustment arm, ending in `default: throw new Exception("Calculation type not supported: " + calc.Type.ToString())`) -- there is no `case IncreaseChargesAdjustment` arm, so any FeeLogic that includes this type will throw at runtime the moment ApplyAdjustment reaches it. The model class (CustomerDataModel.cs:965, CalculationLevel hardcoded Charge, no configuration fields beyond base Calculation) and the UI field class (IncreaseChargesAdjustmentField, CustomerSchema.cs:3686, adds no child fields) both exist and it is still selectable in AdjustmentField's ChoiceList (CustomerSchema.cs:3036), so the UI will let a configurer pick a type that is guaranteed to blow up at calculation time -- plumbing was left in place after (or without ever having) execution logic.
class · /home/cary/src/mdc/MdClarity/MDClarity/MDClarityCore/Backend/CustomerDataModel.cs:965
CONFIRMED