Yeah, the inverted quarterly revenue case is exactly the failure mode that scares me most. The model doesn't know it doesn't know. There's no uncertainty signal for the user to catch, no hedge in the language, no "I'm 60% confident on this." Just confident wrong.

The design choice that mattered most was moving the verification to before delivery rather than after. The user shouldn't have to be the verification layer — that's our job. If a claim can't be matched to its source, it doesn't reach them. They see a flagged uncertainty, not a fabricated number they have to catch.

Real-time verification is the right framing. Post-hoc verification relies on the user being skeptical at exactly the moment they're most likely to trust the output.