cd /news/ai-agents/naeos-technical-build-log-002-intent… · home topics ai-agents article
[ARTICLE · art-139163] src=dev.to ↗ pub= topic=ai-agents verified=true sentiment=· neutral

NAEOS Technical Build Log #002 Intent Is Not Authority

A developer is building NAEOS, an open-source engineering layer for AI coding agents that separates agent intent from authorization, so a model can propose an action without being the authority that approves it. The design routes actions through a pipeline of Agent → Proposal → Policy → Authorization → Runtime → Observation, producing auditable records such as "Policy P-014 authorized capability C-003 under version V-2" followed by an execution receipt. The project argues that prompt instructions and in-context policy files influence a model but do not constitute an independent authorization boundary.

by read2 min views2 publishedSep 24, 2026

One assumption keeps appearing in AI agent systems:

If the model understands what needs to be done, it can decide what should be done. I don't think those are the same problem.

An AI coding agent can produce an excellent plan.

It can understand the repository.

It can identify the required files.

It can even correctly predict the command that needs to be executed.

But none of that means the agent is authorized to execute the action.

This distinction is becoming one of the core ideas behind NAEOS:

Intent ≠ Authorization

The model produces intent.

A policy system determines whether that intent is allowed.

The runtime executes an authorized action.

And observation verifies what actually happened.

So the flow becomes:

Agent → Proposal → Policy → Authorization → Runtime → Observation

This sounds like additional complexity.

But consider what happens without the separation.

An agent receives:

“Update the production configuration.”

The model decides:

“I need to modify this configuration file and restart the service.”

What prevents the model from deciding that the restart is also allowed?

Prompt instructions?

System messages?

A policy file inside the context?

Those mechanisms can influence the model.

They don't necessarily constitute an independent authorization boundary.

That's the problem I'm trying to address with NAEOS.

The model should be able to propose an action without becoming the authority that approves the action.

This also creates a cleaner audit model.

Instead of:

Agent said it was allowed.

we want:

Policy P-014 authorized capability C-003 under version V-2. Then:

Runtime executed C-003.

External observation produced receipt R-8291.

Now the system can distinguish what was proposed, what was authorized, what was executed, and what was actually observed.

That's a very different trust model.

I'm currently implementing and testing these ideas in NAEOS as an open-source engineering layer around AI coding agents.

The interesting question for me isn't:

“How do we make agents more obedient?”

It's:

“How do we design the system so obedience isn't the security boundary?”

Repository:

https://github.com/NAEOS-foundation/naeos How are you currently separating agent intent from actual authorization in your AI systems?

── more in #ai-agents 4 stories · sorted by recency
── more on @naeos 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/naeos-technical-buil…] indexed:0 read:2min 2026-09-24 ·