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…
cartographer.mapModule 17
Plane module
Cartographer edge review
Keep connections between resources on a map you control: the cartographer proposes, and a person or a bound you wrote approves.
cartographer.map returns the ratified edges, the amendments waiting for approval and the auto-ratify bounds in force. A model reads text and proposes edges off the hot path. A person ratifies each one, or a bound in the compiled mandates lets listed relations through up to a cap.
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 single bound that stopped the edge, never a bare count.
bounds.relations
The relations the compiled mandates let the cartographer ratify. Empty means the bound is closed.
bounds.max
The most edges one batch may ratify: eight when relations are listed and no cap is.
pendingDropped
On propose and infer: how many older pending edges were dropped to stay within the queue limit.
Mechanism
Step by step
How it works
Edges are proposed
infer sends text to an off-path model for candidate edges, and propose takes edges an agent or person names. Both pass the same checks before anything is written.
The bound decides what passes
An edge goes through only if its relation is bounded, both endpoints are already on the map, it would not merge two live leases held by different agents, and the cap is not reached.
The rest waits with a reason
Everything else is queued as bounds_closed, relation_not_bounded, unknown_endpoint, would_merge_active_conflict or cap_exceeded.
A person ratifies or dismisses
edge ratifies an edge as the operator and clears it from the queue. dismiss drops it, and nothing reaches the map.
Try it
Live demo
Run it from this page
GET/api/v1/acp/cartographer/map
// 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. cartographer.map 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 agent reports that the billing service calls the ledger. The edge waits in pending until an operator ratifies it, instead of reshaping the map on a model's word.
Letting low-risk relations through
A mandate lets calls edges ratify, three at a time. Other relations still wait for a person.
Stopping a merge of live leases
A proposed edge would join two resources held by different agents right now. It is held as would_merge_active_conflict.
Dropping a wrong guess
A suggested edge is wrong. dismiss removes it from the queue and the map stays as it was.
When to use something else
Reading the nodes themselves. Edges here are pairs; the node list with rings is worldmodel.graph.
Writing the bound. It is law, compiled and ratified through mandates.compile; the cartographer only reads it.
Deciding who may use a resource. Edges say how resources relate, and access comes from grants through coordination.admit.
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 model's proposal never reaches the map on its own; it needs a bound that covers it or a person's edge call.
With no bound in the compiled mandates, auto-ratification is closed. A missing or unreadable policy can only deny it.
Each held edge names the one bound that stopped it, so the reason is on the record.
A name becomes known through an actor's declaration, not a model's mention, so a model cannot mint territory.
It does not
That a ratified edge is true. It is accepted as stated, and the cartographer does not test it against traffic.
That the model's suggestions are good. Pending edges carry no confidence score.
Who approved an edge. The map keeps the edge, not the person who ratified it.
That the queue is complete. It keeps the newest 500 and drops older ones.
Details
Build notes
Before you build
Where a bound comes from
Two kinds of grant in a compiled mandate, for the principal cartographer: ratify on imd://cartographer/edge/rel/<relation> for each relation, and ratify on imd://cartographer/edge/max/<n> for the cap.
Who may approve
edge and dismiss need the policies.approve permission. propose and infer need policies.propose.
An off-path model
infer runs a classifier model off the hot path, through a queue or workflow when one is bound. Admission never waits on it, and its answer is only a proposal.
Limits and metering
The pending queue holds 500 edges. Older ones are dropped and counted in pendingDropped.
A batch ratifies at most bounds.max edges: eight when the mandate lists relations and sets no cap.
infer answers queued when a queue or workflow takes it. Pass forceInline: true to run it inside the request.
Reading the map is not metered.
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
GET/api/v1/acp/cartographer/mapRead ratified edges, pending amendments and the bounds.
POST/api/v1/acp/cartographer/edgeRatify one edge as the operator.
POST/api/v1/acp/cartographer/proposePropose edges and let the bounds sort them.
POST/api/v1/acp/cartographer/dismissDrop a pending edge without writing it.
POST/api/v1/acp/cartographer/inferAsk the off-path model for candidate edges.
MCP actions
MCPcoordination.cartographer.mapRead the cartographer's map as an MCP action.
MCPcoordination.cartographer.edgeRatify one edge as an MCP action.
MCPcoordination.cartographer.inferAsk the model for candidate edges as an MCP action.