SShortSingh.
Back to feed

Hybrid AI-Graph System Separates LLM Reasoning from Fraud Policy Decisions

0
·64 views

Engineers at the TigerGraph × Hacker House Goa IEEE Fraud Challenge built an autonomous fraud detection system that prevents Large Language Models from directly controlling banking actions such as blocking cards or filing regulatory reports. The architecture splits responsibilities across three tiers: an LLM reasoning layer, a TigerGraph topology layer processing over 590,000 transactions, and a deterministic Python-based policy engine that makes all final decisions. The design addresses key risks of unconstrained LLMs in finance, including hallucinations, non-reproducible outputs, and inability to meet FinCEN and SEC audit requirements. A calibrated machine learning model achieving an AUC of 0.9950 feeds into a rules-based policy engine, ensuring decisions are mathematically deterministic and auditable. The team argues this separation is essential in production fraud defense, where false positives from raw ML scores routinely disrupt legitimate customers and generate regulatory liability.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

GPT-6 Astra edit lifts small model's math score, but weight-reading claim fails audit

MIT CSAIL researchers reported that GPT-6 Astra edited about 0.016% of Qwen3.5-0.8B's weights without training, raising MATH-500 accuracy from 7.9% to 48.1%. The edit changed a rank-1 component in 64 columns of two down_proj tensors, and an independent re-run reported 51.0% on MATH-500. Much of the gain appears to come from removing a repetition loop that caused the base model to hit token limits, rather than from new mathematical ability. A broader claim that the model could read weights to infer training data did not survive an independent audit published on 5 November 2026. The edited checkpoint is released under Apache 2.0 and is small enough to run on a 12 GB GPU.

0
ProgrammingDEV Community ·

Company Names Do Not Establish Identity: 14 Tests Before CRM Import

Prospect files may describe a legal enterprise, one of its establishments, a trading name, a corporate group, or a contact, so similar names alone are unreliable for matching records. Importers that treat name similarity as proof can wrongly merge branches into parents, attach people to the wrong account, or erase separate buyers. The article recommends matching only on evidence that identifies the same entity, routing relationships and ambiguity to review, and never treating a score as certainty. It explains that French identifiers distinguish legal units (SIREN) from establishments (SIRET), so records sharing a SIREN may still describe different locations. The author offers a synthetic 14-case test pack and a conservative triage approach, with identity decided before person-level deduplication.

0
ProgrammingDEV Community ·

Dev.to API rate-limit retries cleared only half the time in one developer's pipeline

A developer's comment-reply pipeline hit dev.to API 429 rate-limit errors ten times since August, according to its work log. Counting outcomes showed that in-run retries cleared the limit in five cases and failed in five, with the failures resolved only by later scheduled runs. The script contains no retry or sleep logic; each backoff interval was improvised by whichever run encountered the error and then discarded. The author argues the log cannot distinguish whether retries or simply elapsed time caused the successful recoveries.

0
ProgrammingDEV Community ·

Connection Pools Starve When AI Agents Hold Leases During Slow External Calls

An article on DEV Community argues that outages can occur even when database CPU is nearly idle, because connections are held open while waiting on external systems. The author notes that AI agent runtimes, which leave a pooled connection leased during slow LLM or API streams, are a common cause. Using Little's Law, the piece shows that a 20-connection pool handling 2ms queries can sustain about 10,000 requests per second, but drops to roughly 0.7 requests per second when each connection is held for 28 seconds. The result is queuing, timeouts, and HTTP 500 or 503 errors despite low resource utilization. The article argues that vertical scaling does not solve the problem, and that the same pattern affects Redis, HTTP clients, Kafka, and CRM API quotas. It also states that single-threaded unit tests and staging environments typically fail to surface this issue.