Consider moving OccupationalData.retirementDate (R4 ballot's OccupationalData.retirementStatus.effective_x_) under the OccupationalData.pastOrPresentJob backbone element

This is somewhat related to my other tracker (GF#14478) that suggested employmentStatus (as well) could be tracked per job (not per person).

Employers, for example, track this data (both status and retirement dates) at the employer level – not the person level. If a person has 2 jobs with 2 employers and retires from one job, then that employer will consider their status as retired regardless of whether the employee has a second job.