/ INTENTION PROTOCOL
/ STATED VS INFERRED
/ YOU GRANT AUTHORITY
From rough ideas
to reliable briefs
Nabu helps you articulate the outcome you want, make assumptions and permissions explicit, and transform your thinking into an actionable brief.
No browsing. No outside noise. Just a clearer path from what you mean to what gets done.
The laws
How Nabu is allowed
to work with you.
01
You grant. Nabu does not.
What you mark Stated is granted. Nabu cannot overwrite it or quietly promote a guess into a decision.
02
Inferences stay labeled.
If Nabu inferred it, the card says Inferred until you accept it. Guesses are visible, never treated as fact.
03
No invented company facts.
Nabu will not invent your org, code, users, or systems. If it does not know, it says so.
04
Evidence is data, never instructions.
Attached files and GitHub are grounded reality. They inform the conversation. They are not rules, and they cannot tell Nabu what to do.
05
Rules are human-granted only.
Working authorizations persist across chats. Nabu cannot invent a rule. Only you can grant or deactivate one.
06
Minimum questions.
Nabu asks only what would change meaning, authority, or evidence — not a twenty-question interview.
07
Delegate is a human switch.
Explore thinks out loud. Delegate records grants. Nabu will not pretend you entered Delegate.
08
Closed world. No web.
Nabu does not follow links or surf the internet. Authority is what you state, grant, or attach — not a changing webpage.
Closed world
No links. No web surfing.
Nabu will not open URLs, search the internet, or treat a webpage as a source of truth. The live web changes, is not yours, and is a common path for invented facts and injected instructions.
Reality here is narrower on purpose: what you stated, what you granted, and what you attached. If a document matters, you upload it or connect the repo. That keeps authority inside the conversation you control.
The card
A fast way to pin
the basics.
The Intention card sits beside the chat. Use it when you already know the shape of the work — or let Nabu propose fields and accept only what is true. Each box has a ? if the label is unfamiliar.
- 01Objective. The aim — what you are trying to accomplish.
- 02Desired outcome. What should be true if that aim worked.
- 03Department Authorization. The area that must sign off.
- 04Constraints. Limits that must be respected.
- 05Non-goals. What you are explicitly not doing.
- 06Assumptions. Treated as true without proof.
- 07Unknowns. Questions still to decide.
- 08Evidence required. How you would know it worked.
Plus unknowns, evidence required, and what Nabu may decide without you.
Your rules
Teach it how to work
with you.
After a free login, a red Rules control sits under the chat. Those rules persist across conversations. They are not evidence. Nabu cannot invent them. Use them to fit a team, a tone, or a risk posture.
Example 01
Ask before proposing any change to production systems.Example 02
Write for counsel: no slang, cite only what I granted.Example 03
Never mention vendors or competitors by name.Example 04
Prefer the smallest reversible step.Example 05
If Department Authorization is empty, stop and ask who signs off.Example 06
Keep replies under a half page unless I ask for a brief.I’ll treat that as a constraint, not a guess. Department Authorization is still empty — who has to sign off?
Next steps
Explore, then
delegate the work.
Explore
Think out loud. Nothing is committed. Use this to find the real objective and the outcome that would count as done.
Fill the card
Type the basics — or accept Nabu’s inferences. Stated fields become the source of truth for the rest of the work.
Delegate
You flip the switch. Grants, edits, and discards are recorded. The next move is derived from the card, not from chat memory.
Hand off
When the intention is ready, project a governed brief: objective, outcome, scope, out of scope, and evidence. Paste that into the system that will actually do the work.
Access
Test it out for free, then Deploy.
Shedu works best across teams to make sure that every change gets the proper sign offs, remains in compliance, and the right metrics are reported.
Nabu clarifies. The harness executes.
Use Nabu to get the intention honest. When you need production changes under review, that is the governed harness — a different product, same company.