Who may touch this? Who is holding it? Who approved it? Start from the need. Each page explains where the question comes from, how Intramedial admits or refuses the action before it happens, and exactly what its record can and cannot show.
Put admission in front of your MCP servers, repositories, SaaS tools and cloud accounts. Every agent gets a lease or a reason – and you keep the lever to stop any of them.
© 2026 Intramedial. All rights reserved. Intramedial is a product by Trustvice. Secured and supercharged by Avonao Labs.
Report abuseEvery solution runs on the same path: an agent declares an intent, Intralock admits or refuses it, and the ledger keeps the reason. What changes is the resource at stake.
Stop two agents from writing to the same repository, table or slot at once, and show which one held it and why the other waited.
Use cases
coordination.admit mandates.compile detection.run ledger.blame Keep the decisions your agents were allowed to make, under which rule, in a record an auditor can check without asking you.
mandates.compile coordination.admit conformity.sweep compliance.pack Rehearse how your agents behave when they fight over the same ground, then settle real conflicts by negotiation, arbitration and a person.
drills.frt detection.run negotiate.propose arbitration.arbiter Let agents queue for a deploy slot, ship in checked stages, and keep an unqueued write from reaching the repository.
coordination.admit change-trains.list previews.list mcp.enforce Stop one agent or the whole workspace in a single step, then map what it touched before you undo anything.
watchdog.check coordination.halt ledger.blame remediation.blast Hold a risky intent until a person approves it, and make destructive changes wait for a second, different person.
coordination.approve dual-control.scopes civics.asks coordination.admit Put every MCP tool call through admission, see the callers nobody registered, and give agents cloud credentials only for the length of a lease.
mcp.enforce mcp.shadow ledger.blame coordination.admit Give an auditor, a customer or yourself the record of what your agents did, scoped to the reader, and leave with it intact.
civics.records ledger.blame exit.objectives ledger-bundles.snapshot The same decision answers different people. These groupings are a starting point, not a rule: most needs touch more than one team.
You run the agents, the pipeline or the gateway, and you are the one paged when two of them collide. You want the check inside the code path itself, with no second system to run.
You need to see which agent holds what, notice a caller nobody registered, and show afterwards who was allowed to do what, and under which rule.
You need records that hold up when someone else checks them: a regulator, an auditor, a customer’s counsel. You also need to know precisely where that record stops.
Whatever the need, an admission has the same four properties. They are narrow on purpose.
The check runs ahead of the action. A refused intent never reaches the resource, and says why.
Every denial names its rule. Nobody reads a log to learn why an agent was stopped.
Each action resolves to one registered agent with one owner, never to a shared service account.
Decisions land in an append-only ledger under Merkle roots, so a past entry cannot be quietly edited.
Tell us what your agents touch and who must answer for it. We will say plainly whether Intramedial fits, and when it does not.
The Try it terminal runs the real admission kernel on your machine. It needs no account and sends nothing, and each decision comes back with its reason.
