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.quarantineModule 32
Plane module
Agent quarantine
Cut one agent off at admission, but only with the second person's approval or a ruling that names that exact agent.
coordination.quarantine adds an agent's DID to the quarantine set, so admission answers quarantine for it. The route is destructive and default closed: it needs a warrant, either a dual-control request another administrator approved or an adjudicated case at rung 3 or 4 that names the agent.
Intralock · Leases · Parley · Fleet Map
A Trustvice Product
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.
The coordination.quarantine action accepts only did, so it has no place for a warrant. Send the REST route with a warrant field, or use coordination.halt with scope: agent, which an administrator can call directly.
Record
The record
What gets recorded
did
Required. The agent to quarantine. actorDid is accepted as an alias.
warrant
Required over REST. An object with kind (dual-control or adjudicated) and the id of the request or case.
For lift. A reason that goes into the coordination.lift event.
quarantined
In the fleetmap response: the DIDs currently in the quarantine set.
Mechanism
Step by step
How it works
Forms and phases
A
Dual-control warrant
warrant: {kind: dual-control, id} where id starts dc_. One administrator files dual-control/request for the quarantine scope; a different administrator approves it.
B
Adjudicated warrant
warrant: {kind: adjudicated, id} where id is a case. The case needs a standing ruling at rung 3 or 4, a quarantine remedy, and this DID among the subjects it names.
Step by step
Get a warrant
File a dual-control request for the quarantine scope with this body, or have an arbitration case reach a ruling that orders quarantine for this agent.
Send the route
quarantine takes did and the warrant. Without one the dispatcher refuses with 403 before the module runs.
Admission refuses
The DID joins the quarantine set and is stored with the workspace's policy. The next admission for that agent answers quarantine.
Try it
Live demo
Run it from this page
GET/api/v1/acp/coordination/fleetmap
// No body: this is a GET. Press Run.
Runs in a shared demo workspace with a demo key: anyone can see what it holds, so send nothing private. coordination.quarantine docs
Responses
Press Run to send the request on the left to the shared demo workspace.
Runs in a shared demo workspace with a demo key: anyone can see what it holds, so send nothing private.
Code
Live example
A real request
A request in the shape the API accepts, and an example response in the shape the module returns.
An arbitration case rules quarantine for one agent. The case is the warrant, and nobody has to repeat the decision with a second administrator.
Two administrators agree
One files the request, the other approves it with MFA. The quarantine route accepts the approved id as its warrant.
Checking who is stopped
fleetmap returns the quarantined DIDs along with agents, leases and presence, so a console can show what admission will refuse.
Releasing an agent
lift removes the DID. Its administrator and reason are ledgered, which a bare quarantine call does not do.
When to use something else
Stopping an agent at once as an administrator. Use coordination.halt, which needs a reason and ledgers itself, but no second person.
Revoking a single grant. That is the revoke route, which carries the same kind of warrant.
Deciding that an agent should be quarantined. arbitration.arbiter rules on cases; this route applies the outcome.
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
A call without a valid warrant is refused by the dispatcher, because the gate is closed by default.
An adjudicated warrant is checked against the real case: rung 3 or 4, a standing ruling, a matching remedy and a matching subject.
A ruling against one agent is not a warrant against another; the case must name this DID.
A quarantined agent is refused at admission with the reason quarantine, with no model call.
It does not
That the quarantine records who set it or why. The route stores the DID only and writes no event of its own; the request or case is the record.
That the agent is refused everywhere. Like any denial, it applies where the resource class is at enforce; protected classes always are.
That the agent has stopped running. Quarantine refuses admissions; the process may still act outside the plane.
Details
Build notes
Before you build
Why the gate is default closed
A gate that is not on the path protects nothing, so it sits in the dispatcher. A destructive route with no warrant is refused, not waved through.
Rulings are exempt from two people
A rung-3 ruling already has a case file, a ledger trail and an appeal, so it does not need two administrators to apply its own remedy.
What a ruling must be
A referral to a human, a fallback ruling and a reopened case are not warrants. A model ruling stands only where a detector or an administrator named the subject.
Permissions
lift is for a signed-in administrator. fleetmap is a read and carries no role.
Limits and metering
quarantine without did returns 400, and without a warrant it returns 403.
The warrant must be for the quarantine scope and for this subject, or the call is refused.
The coordination.quarantine and coordination.lift actions take only did, so a warrant or a why cannot ride them.
Quarantine is a set of DIDs; it holds no expiry, so it lasts until lift or unhalt.
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/quarantineQuarantine an agent under a warrant.
POST/api/v1/acp/coordination/liftLift a quarantine and ledger who lifted it.
GET/api/v1/acp/coordination/fleetmapRead agents, leases, presence and the quarantine set.
MCP actions
MCPcoordination.quarantineQuarantine from an action call; the action cannot carry a warrant.
MCPcoordination.liftLift a quarantine from an action call.
MCPcoordination.fleetmap.getRead the Fleet Map from an agent.