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

推荐订阅源

S
SegmentFault 最新的问题
J
Java Code Geeks
V
V2EX
Blog — PlanetScale
Blog — PlanetScale
博客园 - 司徒正美
Hugging Face - Blog
Hugging Face - Blog
F
Fortinet All Blogs
aimingoo的专栏
aimingoo的专栏
B
Blog
A
About on SuperTechFans
有赞技术团队
有赞技术团队
月光博客
月光博客
Microsoft Azure Blog
Microsoft Azure Blog
阮一峰的网络日志
阮一峰的网络日志
腾讯CDC
美团技术团队
大猫的无限游戏
大猫的无限游戏
爱范儿
爱范儿
N
Netflix TechBlog - Medium
C
Check Point Blog
Recent Announcements
Recent Announcements
博客园 - Franky
博客园 - 叶小钗
T
Tailwind CSS 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
Is AI governance only about safety, or should it also con...
Anna Jambhul · 2026-05-14 · via DEV Community

Anna Jambhulkar

I’ve been researching the AI governance runtime category while building NEES Core Engine, and one thing became clearer to me:

Most AI governance tools are designed around risk reduction.

They help answer questions like:

Is the output unsafe?
Is there PII in the prompt?
Is the model violating policy?
Is the system compliant with internal or regulatory rules?

That is important. But while building AI products, I noticed another failure mode:

An AI can be “safe” and still be unreliable as a product.

It can drift from its intended role.
It can change tone across sessions.
It can misuse memory or context.
It can behave differently even when the product logic expects consistency.
It can follow a prompt but break the actual user experience.

That led me to a different framing:

Traditional AI governance asks: “Is this response safe?”
Behavioral governance asks: “Is this AI behaving the way the product intended?”

This is the direction I’m exploring with NEES Core Engine — a governance runtime that sits between an application and the model provider, not only to filter harmful content, but to enforce things like:

identity consistency
memory boundaries
intent-aware policy decisions
runtime traceability
product-defined behavior

The difference I’m seeing is:

Standard governance runtime: protect the company from AI risk.
Behavioral governance runtime: protect the product from AI unpredictability.

For example, in a support bot, safety filtering is not enough. The bot also needs to stay within its role, follow product logic, respect memory boundaries, and behave consistently across sessions.

For AI agents, this becomes even more important because the system may use tools, access data, or make workflow decisions.

I’m curious how other founders and AI builders think about this:

When building AI products, do you see governance mostly as a compliance/safety layer — or do you also need a runtime layer that controls behavior, identity, memory, and intent?

Would love feedback from anyone building agents, AI assistants, internal copilots, or customer-facing AI products.