

Yeah, that’s a good point. I guess in light of that what I would say is that, if you are going to have a state-run payment processor, you need to build in a) pluralism (enable and encourage multiple processors) and b) legal protections (legally guarantee that the payment processor has a limited remit in terms of allowing all payments unless instructed to block them by a court order) which would help mitigate or slow down anti-democratic backsliding.
End-to-end ML can be much better than hybrid (or fully rules-based) systems. But there’s no guarantee and you have to actually measure the difference to be sure.
For safety-critical systems, I would also not want to commit fully to an e2e system because the worse explainability means it’s much harder to be confident that there is no strange failure mode that you haven’t spotted but may be, or may become, unacceptable common. In that case, you would want to be able to revert to a rules-based fallaback that may once have looked worse-performing but which has turned out to be better. That means that you can’t just delete and stop maintaining that rules-based code if you have any type of long-term thinking. Hmm.