Intent Fidelity Protocol
A test for whether AI did what you meant, not only what you typed.
Intent Fidelity
Protocol.
AI follows instructions literally. This protocol checks whether the intended outcome actually occurred - and whether unintended outcomes occurred too.
Traditional systems ask: "Did the action succeed?" This asks a harder question: "Did the intended outcome occur AND did any unintended outcomes also occur?" The second question is more important than the first.
Three axes of
intent verification.
Every AI response is measured on fidelity, consequence, and endgame. Consequence carries the highest weight because unintended outcomes are harder to detect than intended ones.
The Don't Kick
Problem.
Literal compliance. Spiritual violation. "Don't hit your brother." The child kicks instead. "You didn't say not to kick."
The child is not lying. The instruction was followed literally. The intent - don't harm - was violated. AI does this constantly. Every existing framework evaluates the letter. This protocol evaluates the spirit.
Where intent
verification sits.
The intent verifier runs after the AI engine responds and after alignment checks. It is the final integrity gate before the response reaches you.
Rule-based. Zero additional AI cost. Non-blocking. Best effort.
See intent verification
in action.
DreamerOS is the first AI system with this verification layer running in production. Try it free.
Plain words for the words on this page
Page. A single screen on this site, like the one you are reading. It is not a unit you buy and we never charge for one.
A client-side path in the web app, served over HTTPS; not a billing unit in any plan.
Token. The small pieces a computer chops your words into, about three quarters of a word each. Your plan sets how long one answer can be, counted in tokens. It does not set how many questions you may ask.
Max tokens per response, one value per plan. Each plan card lists its own.
Engine. One AI brand you can talk to. ChatGPT, Claude, Gemini, Grok and Perplexity are the five. Your plan page lists which ones you can use.
Five role names per plan (Build, Review, Synthesis, Signal, Research). Some plans count the engines you connect live, and the limit is checked on every request.
Connector. A link between DreamerOS and a tool you already use, such as Gmail, Notion, Slack, GitHub or Stripe. It lets DreamerOS read from that tool, and in some cases act in it, but only inside rules you set.
39 provider integrations on the gateway, each reached over HTTPS with a scoped, per-provider key.
Receipt. A short record attached to your answers. It names which engine answered, what it cost, which checks passed, and whether sources were checked. You never have to guess what just happened.
One record per answer, written server-side on the gateway: engine, model, plan, cost, and the pass or fail result of the pre-check and post-check.
Memory. The facts about you that DreamerOS keeps and reuses next time, so you stop repeating yourself. Your plan sets how many facts it holds.
Active memory rows per plan, with a smaller fallback for a session with no plan set yet. Each plan card lists its own.
MCP key. A key you paste into another app, such as Claude Desktop or Cursor, so DreamerOS memory and checks work there too. You do not have to change where you already work.
A signed key. Individual tools inside it may carry a plan floor.
Intent fidelity. Checking that the answer answers the question you actually asked, not a nearby one that was easier.
A rule-based check that runs on the gateway, scored on three axes, with no separate model call.
Direction set. The standing written instructions DreamerOS gives every engine before it sees your question, so all five behave the same way.
One canonical system prompt, loaded by the gateway and sent to every engine.
Check. A test run on your question before the engine sees it, and on the answer before you see it.
A pre-check before the engine sees your question, and a post-check before you see the answer; both results ride the receipt.