惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园_首页
博客园 - Franky
大猫的无限游戏
大猫的无限游戏
博客园 - 三生石上(FineUI控件)
量子位
博客园 - 聂微东
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
S
SegmentFault 最新的问题
Apple Machine Learning Research
Apple Machine Learning Research
爱范儿
爱范儿
V
Visual Studio Blog
雷峰网
雷峰网
T
Tailwind CSS Blog
宝玉的分享
宝玉的分享
Blog — PlanetScale
Blog — PlanetScale
有赞技术团队
有赞技术团队
博客园 - 叶小钗
Microsoft Azure Blog
Microsoft Azure Blog
T
The Blog of Author Tim Ferriss
U
Unit 42
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
小众软件
小众软件
阮一峰的网络日志
阮一峰的网络日志
Y
Y Combinator Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Stop Using LLMs to Audit Other LLMs: You Are Bricking You...
Eren Özgüney · 2026-05-30 · via DEV Community

Eren Özgüney

Look at your modern Agentic AI stack.

An agent wants to execute a tool, trigger a deployment, access a database, or call an external API.

Because nobody fully trusts a probabilistic black box, many teams now use a second probabilistic black box to validate the first one.

Think about what is actually happening.

You are running hundreds of billions of parameters, consuming tokens, burning GPU resources, and adding hundreds or thousands of milliseconds of latency just to answer a simple operational question:

  • PASS
  • HOLD
  • RED

Or in plain English:

  • Continue
  • Verify
  • Stop

For many production systems, that's the only decision that matters.

Yet we often spend orders of magnitude more compute determining whether an action should execute than executing the action itself.

That feels dangerously close to architectural bankruptcy.

The Illusion of Prompt-Based Safety

We've all done it.

You create a prompt:

"You are a security validator. If the action appears unsafe, return RED."

Then reality arrives.

Prompt injections appear.

Edge cases appear.

Different model versions behave differently.

The same input occasionally produces different outputs.

And your cloud bill keeps growing.

At some point, a difficult architectural question emerges:

Can a probabilistic system reliably govern another probabilistic system?

Many teams assume the answer is yes.

I'm not convinced.

The Problem Isn't Intelligence

This is where I think the industry may be looking at the problem incorrectly.

The challenge is not intelligence.

The challenge is governance.

LLMs are exceptional at:

  • Reasoning
  • Summarization
  • Code generation
  • Natural language interaction

But governance is a different problem.

Governance is not asking:

"What is the best answer?"

Governance is asking:

"Should this action be allowed to proceed?"

Those are fundamentally different questions.

A Different Architecture

While exploring this problem, we ended up building a separate deterministic governance layer internally.

Instead of generating text, it performs structural measurement.

Instead of token prediction, it evaluates operational behavior.

Instead of producing paragraphs, it produces a hard decision boundary:

  • PASS
  • HOLD
  • RED

To make this practical, the architecture is separated into three deterministic stages:

QRL — Quantified Risk Layer

Measures risk exposure, escalation potential, and projected operational impact.

ACE — Adversarial Consistency Engine

Evaluates structural inconsistencies, masking patterns, divergence, and conflict signals.

DDE — Deterministic Decision Engine

Converts the measured operational state into a final posture:

  • PASS
  • HOLD
  • RED

The interesting part is not the implementation.

The interesting part is the outcome.

The governance layer operates in sub-millisecond latency and produces the same measurement for the same structural input.

No prompt engineering.

No token accounting.

No GPU dependency.

No semantic interpretation layer.

The Real Debate

I am not arguing that LLMs are unnecessary.

Quite the opposite.

LLMs are one of the most important technological breakthroughs of our lifetime.

The question is whether we are using them for problems they were never designed to solve.

As AI agents begin executing real-world actions, we will need systems that can:

  • Prevent unsafe progression
  • Enforce operational boundaries
  • Remain predictable under load
  • Scale to millions of decisions per day

My suspicion is that future AI systems will not be purely probabilistic.

They will be hybrid systems.

A probabilistic generation layer.

And a deterministic governance layer.

A Question For Engineers Building Agent Systems

If your agent executes 10 million actions per day, how does your governance layer work?

  • Another LLM?
  • Rules and regex?
  • Human review?
  • Traditional policy engines?
  • Something else entirely?

I'm genuinely curious.

Where do you draw the line between semantic reasoning and deterministic control in production-scale AI systems?

And more directly:

If your agent executes 10 million actions per day, would you really trust another LLM to approve every single one?

Why?