Intramedial is in restricted beta. At sign up or sign in, you have to provide the beta tester password you received or request one at preview@intramedial.com. Thank you.
Loading…
coordination.admitModule 01
Plane module
Intralock admission
Decide every action before it happens: an agent declares its intent, and Intralock admits it or names the reason it may not.
coordination.admit is the plane’s hot path. An agent sends its DID, the resource and the verb, and Intralock evaluates that intent against the compiled policy snapshot, quarantines and stop switches. The answer is an allow or a deny with a reason, with no network call and no LLM.
Agents act when the plane says yes, and the record says why.
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.
grant on an allow; on a deny the code that explains it, such as quarantine or confirmation_required.
enforced
Whether the resource class was at enforce, so the verdict actually applied to the call.
Mechanism
Step by step
How it works
The agent declares the intent
Post actorDid, resource and action to POST /api/v1/acp/coordination/admit before acting. A write or delete also carries a single-use confirmationToken.
The plane's own gates run first
A quarantined actor is refused with quarantine, and a stopped resource with resource_halted. A write without a valid token is refused with confirmation_required and lands in the approval queue.
Intralock evaluates the snapshot
The intent is checked against the compiled grants of the policy snapshot. The kernel is a pure function: same intent, same snapshot, same verdict.
The adoption stage shapes the answer
A resource class runs at observe, advise, transform or enforce. Only enforce can deny; the earlier stages report what enforce would have decided and let the call through.
The decision goes to the log
The decision is written after the response, never before it, so logging adds nothing to the hot path. A decision that went over its time budget is recorded as well.
Press Run (or ⌘/Ctrl + Enter) to decide the request on the left.
It runs in this browser: the plane’s own kernel, with no key, no account and no network call. Change an agent, a lease or a rule on the left and run it again to see the verdict move.
Code
Live example
A real request
A request in the shape the API accepts, and an example response in the shape the module returns.
A release agent and a dependency bot both want repo:payments/main. Both declare first, so the second gets a reason and a holder to wait for, instead of a failed push.
A person on the risky step
An agent may read a table freely, but a delete needs a token. The refusal creates an approval request, and the agent resumes when someone signs.
Adopting without breaking anything
Put one resource class at observe, read what enforce would have decided for a week, then raise that class alone.
A refusal an agent can act on
The reason lets an agent take another route or stop and ask, rather than retry the same denied call in a loop.
When to use something else
Scheduling work inside one team's workflow. Admission decides whether an action may happen, not which task runs next.
Holding a resource across several steps. Admission answers one intent; use coordination.lease to hold it.
Stopping an agent that never declares. Put an enforcement point such as mcp.enforce or github.enforce in its path.
Evidence
Guarantees
What it does, and what it does not
A module is a strong claim about a narrow thing. Rely on it for exactly what it is.
It does
Every intent that reaches it gets a verdict from the same deterministic kernel, with no model involved.
A write or delete at enforce does not pass without a single-use confirmation token bound to that actor, resource and verb.
A quarantined agent stays refused on protected classes, whatever the adoption stage says.
Each decision records its verdict, its reason and whether it was enforced.
It does not
That the agent did what it declared. Compare intents with observed effects in detection.run.
That an agent cannot act around the plane. Admission binds only actions that pass through an enforcement point.
That the policy is right. Intralock applies the compiled mandates exactly as written; replay them in mandates.compile.
Details
Build notes
Before you build
Time budget
The kernel's budget is 5 ms p99 of its own work and 15 ms across a request with Durable Object calls. Both are set in code and checked in tests; samples over budget are recorded.
Fail posture
Each resource class declares fail-open or fail-closed. If the kill-switch store cannot be read, the response says so in killSwitch.readable instead of hiding it.
Protected classes
KMS, identity, ledger and billing stay at enforce. The adoption ladder cannot be used to open them.
Limits and metering
Each admission decision counts as one coordinated action, whatever its outcome. Reads of the map and presence do not count.
A confirmation token is single use; replaying one is refused with confirmation_replay.
Over-budget samples are recorded for the operator; a slow admission is not refused for being slow.
Access
API & MCP
REST and MCP
Authenticate with a workspace API key as a Bearer token. The base URL is https://api.intramedial.com.
REST endpoints
POST/api/v1/acp/coordination/admitDecide one declared intent.
POST/api/v1/acp/coordination/confirmMint a single-use confirmation token for a write or delete.
MCP actions
MCPcoordination.admitDecide one declared intent.
MCPcoordination.confirmMint a confirmation token for a write or delete.