# TA5 Priority-Change Resolution

Problem:
Prior output said both:
- If priority change is not accepted, fall back to TA5.
- TA5 also needs POST_HEDGE_SLOT and `priority_order_change_required=true`.

Resolution:
- The phrase `priority_order_change_required` was too coarse.
- It must be split into:
  - slot_addition_required
  - existing_exit_relative_order_change_required
  - hardstop_relative_order_change_required
  - hardstop_preemption_required
  - existing_eligible_close_preemption_possible
  - structural_insertion_only
  - current_behavior_semantically_changed

TA9:
- slot_addition_required: true
- existing_exit_relative_order_change_required: false if current HTE/Recovery/BasketClose eligibility suppresses TA9
- hardstop_relative_order_change_required: true for real order sending before the HardStop gate
- hardstop_preemption_required: true for future production close, but must be false when HardStopNow=true
- existing_eligible_close_preemption_possible: yes if guards are omitted; no under the proposed decision table
- structural_insertion_only: true for shadow logging only
- current_behavior_semantically_changed: false for shadow; true for real close

TA5:
- slot_addition_required: true
- existing_exit_relative_order_change_required: false if current HTE/Recovery/BasketClose eligibility suppresses TA5
- hardstop_relative_order_change_required: true for real order sending before the HardStop gate
- hardstop_preemption_required: true for future production close, but must be false when HardStopNow=true
- existing_eligible_close_preemption_possible: yes if guards are omitted; no under the same decision table
- structural_insertion_only: true for shadow logging only
- current_behavior_semantically_changed: false for shadow; true for real close

Conclusion:
- TA5 is not a valid alternative if the business rule is "no pre-HardStop slot / no HardStop-relative behavior change".
- TA5 is only a lower-effect, simpler-condition alternative after the same pre-HardStop slot concept is accepted.
- Therefore `TA5_without_priority_change_valid=false`.
