Not the OP, but I recognize this kind of situation from my own frustrations at bigcorps:
There are probably
1) many legacy systems with slightly different definitions of opted out, which may be out of sync with each other, forcing the developer to figure out an algorithm for what to decide in the many edge cases, forcing the dev to gather more requirements from many different stakeholders who did not anticipate this
2) many organizatioal owners for all these involved systems and for pieces of the logic and it's consequences, all of whom have different corporate priorities and incentives and calendar schedules
The result is a trivial thing becomes a jungle of scheduled meetings to gain access to the appropriate systems and to make decisions about each edge case, and ultimately go further up the change to reconcile incompatible opinions about how edge cases should be handled
There are probably
1) many legacy systems with slightly different definitions of opted out, which may be out of sync with each other, forcing the developer to figure out an algorithm for what to decide in the many edge cases, forcing the dev to gather more requirements from many different stakeholders who did not anticipate this
2) many organizatioal owners for all these involved systems and for pieces of the logic and it's consequences, all of whom have different corporate priorities and incentives and calendar schedules
The result is a trivial thing becomes a jungle of scheduled meetings to gain access to the appropriate systems and to make decisions about each edge case, and ultimately go further up the change to reconcile incompatible opinions about how edge cases should be handled