Our CTO Built an AI Gateway Processing $2.8B. It Took Me 8 Months to Prove It Would Approve Illegal Loans. Then the Regulators Called.

Jun 3, 2026 · 6:09 PM UTC ·9 min read · 0 reactions · 0 comments · 43 views

TL;DR · WeSearch summary

The article discusses the challenges faced by a QA lead in a company that developed an AI gateway processing $2.8 billion. Despite the system being formally verified as safe, the author uncovered issues related to input distribution drift and semantic drift that could lead to regulatory scrutiny. The narrative highlights the tension between formal verification and real-world performance in AI systems.

Key facts

▪The AI gateway was built by a co-founder and has processed over $2.8 billion in transactions.
▪The QA lead spent eight months proving that the system could approve illegal loans despite its formal verification.
▪Three incidents occurred post-deployment that highlighted issues not covered by formal verification.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/xulingfeng/our-cto-built-an-ai-gateway-processing-28b-it-took-me-8-months-to-prove-it-would-approve-illegal-235l
Publication time	Wed, 03 Jun 2026 18:09:56 +0000
Retrieval time	2026-06-03T18:22:52.881Z
Last seen	2026-06-03T18:22:52.881Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	0W_QChVKn1no
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3941526) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } xulingfeng Posted on Jun 3 Our CTO Built an AI Gateway Processing $2.8B. It Took Me 8 Months to Prove It Would Approve Illegal Loans. Then the Regulators Called. A story about formal verification and adversarial testing. About systems that are mathematically safe, and systems that don't fail in the real world — and which one regulators actually care about. Has your company ever made a decision using AI that just felt wrong? A loan that got approved when it shouldn't have.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments