Start where it costs nothing: agents that ask what they should know. Add authority where questions have consequences. Put the gate in the path where consequences are real. Every agent can stand at a different depth, and most companies run all three at once.
The agent asks what it should know.
Before the work starts, any agent can ask what governs it: which decisions apply, which limits hold, who owns the call. Nothing is blocked and nothing is held. The AI you already use simply stops guessing.
agentPreparing the Acme renewal proposal.
memnoxDiscounts above 15% need the CFO. The May pricing decision applies.
The agent asks whether it may act.
The agent declares the action and its size, and the organization answers before anything runs: allowed, denied, or held for the person who owns the call. The question and the answer are both on the record.
agentRefund $4,500 to Acme.
memnoxHold. Refunds above $1,000 go to the finance manager.
Memnox stands in the path.
For the work with real consequences, the gate sits between the agent and the system it reaches. A blocked action is not a warning that was ignored. It never ran.
agentdb.migrate production
memnoxBlocked. Production migrations need a person.
Every question, verdict and approval feeds the shared understanding. An exception a person approves today becomes the rule applied tomorrow, and the next decision, in any department, is made against it.
How the depth is chosenDecisions get made in threads, meetings and hallways, then live in whoever was in the room. Memnox keeps each one as operating state: what was decided, on whose authority, where it applies, and whether it still stands. Anyone who asks, person or agent, gets the answer from the record, not from whoever happens to remember.
When an agent asks which provider to use, it does not get a stack of documents to weigh. It gets the decision, who had the standing to make it, the scope it holds in, and the evidence it rests on. Acting on it is never a guess about which paragraph wins.
Stripe carries European payments.
Companies disagree with themselves. The handbook names one standard, a newer thread decided another, and this quarter's work already reflects the change. Memnox surfaces the conflict, names the decision that likely supersedes the old one, and holds it for the owner to confirm. Until a person rules, no agent quietly picks a side.
on recordPostgreSQL is the engineering standard. · #212
newerPlatform team agreed to move to MongoDB.
observedNew services already ship on MongoDB.
memnoxconflict · likely supersedes #212 · held for the platform lead to confirm
Every decision keeps the dates it held and the one that replaced it, so the two questions a company actually asks both have answers.
What is our policy today?
The active decision, with its authority and the scope it holds in.
Why do we do it this way?
The chain behind it: what it replaced, who signed it, and the evidence at the time.
Every company already has private discussions, executive decisions, HR policy, legal constraints, customer context and financials that are not for everyone. Memnox does not store that in one pile. It understands who each fact belongs to, and enforces it before any person, agent or application reaches for it.
Acquire Company X
Available to
Ask the sales agent what leadership decided on 14 May and there is nothing to leak. The decision is not in its reality.
A decision, a meeting, a document and a policy are not text to be retrieved. Each one arrives knowing six things about itself.
Classification is not a label someone is trusted to honour. It is the boundary every request is resolved against, whether it came from a person, an agent or an internal service.
Alice in Engineering opens the platform migration she is on.
She cannot open Finance. Bob in Finance cannot open a security incident.
The support agent reads tickets, FAQs and customer policy.
Payroll, the roadmap and legal negotiations are not in its reality.
A connected tool reaches exactly as far as the team that connected it.
Connecting a system never widens what anyone can reach through it.
Bring a consultant in for two weeks, scoped to one project. When the two weeks are up, the access and the context go with them. Nobody has to remember to revoke anything.
Architecture, data handling and our current compliance posture are covered directly with your security and legal teams.