Modeling a fraud-approval agent as a POMDP: approve, verify, or escalate under uncertainty
deepikaau · reddit · 2026-09-11
A developer is prototyping an agent that handles supplier bank-change requests, deciding between approving, verifying via a second channel, or escalating when it can't tell genuine intent from a compromised account. They model it loosely as a POMDP — hidden state = genuine vs. fraud; evidence signals include urgency language, first-time changes, and payment-history matches — and ask others who've built decision-under-uncertainty agents what broke first in real or simulated testing. A candid look at why fraud-approval is a cost-sensitive decision problem, not a clean classification task.
More from coding & agent
- NVIDIA open-sources SoL-Pi: auto-research loops cut agent token cost by up to 54% — udmrzn · 2026-09-11
- Keep the Claude Desktop Workflow, Swap in Local Models via Ollama for Privacy — Technovangelist · 2026-09-11
- Fable 5.1 agent self-onboards into a simulated company's AP department on ERP — ysu_nlp · 2026-09-11
- DeepSeek V4.1 Flash Architecture: 552B MoE with Asymmetric 8B Read / 16B Decode Compute — demian_ai · 2026-09-11
- First-time dev builds a full learning platform in ~35 hours with heavy AI assistance — Dry-Dragonfruit-2159 · 2026-09-11
- Five Days With Grok Bot: MacBook-Level Simplicity for Personal Agents — rseroter · 2026-09-11