Hacker News new | ask | show | jobs
by doctorpangloss 216 days ago
“Determinism is necessary for compliance”

Says who?

The stuff you comply with changes in real time. How’s that for determinism?

3 comments

Author here—fair point, regs are a moving target . But FSB/BIS/CFTC explicitly require reproducible outputs for audits (no random drift in financial reports). Determinism = traceability, even when rules update at the very least

Most groups I work with stick to traditional automation/rules systems, but top-down mandates are pushing them toward frontier models for general tasks—which then get plugged into these workflows. A lot stays in sandbox, but you'd be surprised what's already live in fin services.

The authorities I cited (FSB/BIS/CFTC) literally just said last month AI monitoring is "still at early stage" cc https://www.fsb.org/2024/11/the-financial-stability-implicat...

Curious how you'd tackle that real-time changing reg?

* https://www.fsb.org/2025/10/monitoring-adoption-of-artificia...

This was the link I meant from Oct ‘25 reiterating early stages of AI monitoring

Please give an example of a statutory compliance item that "changes in real time".

That's not the way regulations work. Your compliance is measured against a fixed version of legislation.

Fair pt—statutes lock in. But enforcement lists (OFAC, sanctions) update constantly and require re-screening. The framework proposed ensures deterministic re-runs: same input = same output, keeping audit trails clean when data shifts underneath
Ha ha, the FinCEN BOI drama. Form D. Qualified clients. R&D credits. Export rules.

My bro, the tariffs. The first table of tariffs was written by ChatGPT!

> That's not the way regulations work.

Whatever regulations you are thinking of, they are myths now. I'm not saying deregulation - that isn't happening. In every industry - I know more about healthcare than finance - clear, complex, well specified regulations are being replaced by vague, mercurial ones. The SEC has changed many things too.

Also, what happens if you add a space to the end of the prompt? Or write a 12.00 to 12.000?
Good q—spacing could mess with tokenization, untested but def plausible. Worth a quick test on the setup - through the code for the fin svcs harness for tinkering / testing diff prompts/model arch’s based on feedback https://github.com/ibm-client-engineering/output-drift-finan...