rehoming.planModule 52Plan where this workspace's coordination records should live, see exactly what would move, then carry it to another region on your own say.
rehoming.plan names a source and target region for the workspace's state, leases and ledger rows. execute copies a real snapshot the target region pulls on its own; live presence stays regional, and an EU-bound workspace is pinned by refusing calls from the old region once recorded.
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 abuseRehomingSnapshot.signed is always false; there is no cryptographic attestation of the transfer. plan and execute persist to the policy store and a config key, but neither calls the ledger's appendEvent, so "recorded" means written there, not to the audit ledger other modules use.
Plane module
fromtopinDOsdoClasses/docs/rehoming-planAPI referenceRoutes, bodies and status codes./docs/rehoming-planOpen the consoleSee the module at work in the dashboard, on a seeded fleet or your own./dashboard-preview/rehomingStart freeCreate a workspace and admit your first intent./auth/signup
euBoundstatusplanned from plan, or the recorded state from status.workflowIdexecute runs as an async Cloudflare Workflow rather than inline.plan with a target to region returns the computed from, pinned Durable Object classes and whether the target is EU-bound, as a flat object, not wrapped in a plan key.
execute reads live policy-store keys, leases, D1 rows and Durable Object state, including unsealed ledger leaves, and writes it to a shared CONFIG_KV sidecar key for the workspace.
The target region applies the snapshot lazily on its own next request to this workspace, idempotently keyed by the snapshot's own timestamp.
Once an EU-bound move is recorded, every other ACP module call from the old region returns 421 for this workspace, except rehoming's own routes, which stay reachable everywhere for inspection.
Runs in a shared demo workspace with a demo key: anyone can see what it holds, so send nothing private. rehoming.plan docs
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.
A request in the shape the API accepts, and an example response in the shape the module returns.
POST /api/v1/acp/rehoming/plan Authorization: Bearer av_workspace_•••• Content-Type: application/json { "to": "weur" } → 200 { from, to, pinDOs, doClasses, targetWorker, euBound, status, workflowId, llm } (flat; the { plan } wrapper is what rehoming.status returns, not rehoming.plan)
{
"from": "wnam",
"to": "weur",
"pinDOs": true,
"doClasses": [
"ArenaRoot",
"PresenceHub"
],
"targetWorker": "acp-endpoint-weur",
"euBound": true,
"status": "planned",
"workflowId": null,
"llm": false
}A workspace plans a move to weur, executes it, and from then on every call from its old region is refused with 421 rather than silently serving stale data.
Passing forceInline: true runs the snapshot capture and persistence synchronously instead of handing it to a Workflow, useful when a small workspace does not need the async path.
A workspace moving regions keeps its live PresenceHub websockets connected to the source region; only the last-known presence rows travel in the snapshot, not the open connections themselves.
An operator checks status from whichever region they are working in, since rehoming's own routes stay reachable even after an EU pin takes effect.
signed field is always false; there is no signature over what moved.ledger.blame reads.A module is a strong claim about a narrow thing. Rely on it for exactly what it is.
signed is always false on the snapshot the module writes.appendEvent.execute is itself gated on a human confirmation. Unlike remediation.blast's restore path, rehoming has no separate confirm step before execution.plan's own shape is flatThe plan action's response is not wrapped in a plan key; that wrapper only appears from the separate status action, which returns { plan: stored }.
A capture walks a fixed list of policy-store paths alongside leases, D1 rows and Durable Object state; nothing outside that list is captured.
The EU 421 pin only applies once ITML_REGION is a live production region; the local development region is exempt so a workspace can still be worked on locally after a planned move.
execute writes an unsigned snapshot; there is no attestation of the transfer to verify later.ledger.blame will not show it.restore action; the lifecycle is exactly plan, execute and status.Authenticate with a workspace API key as a Bearer token. The base URL is https://api.intramedial.com.
/api/v1/acp/rehoming/planPlan a region move and see what it covers./api/v1/acp/rehoming/executeCapture and persist the snapshot for the target region to pull./api/v1/acp/rehoming/statusRead the recorded plan and its status.coordination.rehoming.planPlan a move as an MCP action.coordination.rehoming.executeExecute a planned move as an MCP action.coordination.rehoming.statusRead rehoming status as an MCP action.civics.presence14Agent presenceLet agents see which peers are online and what each holds, so a quiet agent is not mistaken for a hostile one.ledger-bundles.snapshot49Signed evidence bundlesSeal your workspace's audit chain into a signed bundle an auditor can check offline, against a key published for anyone to read.exit.objectives53Exit and exportRead the recovery time and recovery point this platform publishes for each kind of data, next to what has actually been measured against them.civics.records48Public records searchAsk the record what happened to one resource, or read the workspace's events plainly, redacted to what your permission actually allows.ledger.blame10Ledger, replay and blameTrace every touch to one resource in order, and replay any event to rebuild the receipt that shows it actually happened.remediation.blast50Blast map and remediationSee what a declared checkpoint's data touched before you undo anything, then restore against it only once a person confirms it by typed phrase.portmind.memory51