yards.listModule 44See every persistent, governed yard registered with this workspace, each with its own constitution and the posts that staff it.
yards.list reads the yards your fleet actually runs in. Each yard gets its own id, a venue, a rules pack and seven standard posts the moment it is created, and other routes fork, migrate, amend or tear one down.
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 abuse
Plane module
idcreate.titlepackIdvenue/docs/yards-listAPI referenceRoutes, bodies and status codes./docs/yards-listOpen the consoleSee the module at work in the dashboard, on a seeded fleet or your own./dashboard-preview/yardsStart freeCreate a workspace and admit your first intent./auth/signup
local, cloud, wnam, weur, apac or oc; an unknown venue is refused rather than accepted as free text.openparticipantDidsmigrationsforkcreate records a yard with a title, packId and venue, and stages the fleet named in participantDids.
Creation calls roles.charters's staffing routine, which fills yardmaster, steward, librarian, gatekeeper, clerk, auditor and treasurer for the new yard before anything else happens.
plan previews a manifest change as a diff with a digest; apply only takes effect with a matching human approval or coverage under a ratified bound, never on the manifest alone.
fork builds a real yard from a sample of the source's data, with named fields redacted, and can be marked ephemeral so it can never be promoted back.
migrate commits a Merkle-chained continuity proof for a venue change. It explicitly does not move Durable Objects; that is plane-wide rehoming.plan.
Runs in a shared demo workspace with a demo key: anyone can see what it holds, so send nothing private. yards.list 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.
GET /api/v1/acp/yards/list Authorization: Bearer av_workspace_•••• → 200 { yards }
{
"yards": [
{
"id": "yard_8a1c",
"title": "payments-prod",
"packId": "pack_default",
"class": "yard",
"created_at": "2026-10-02T11:00:00.000Z",
"open": true,
"venue": "cloud",
"participantDids": [
"did:web:acme.example:agent:release"
]
}
]
}An operator reads yards.list to see every yard a fleet actually runs in today, not a plan of what should exist.
plan shows the exact diff a manifest change would make, with a digest, before anyone approves it or a bound lets it through.
A fork samples a quarter of the source yard's data by default and hides participant DIDs, so a risky change can be tried without touching production or its people.
A migrate response reports movesDurableObjects: false explicitly, so nobody mistakes a venue record change for an actual data move.
import is a hard 501 until the separate import contract is satisfied; this module only wraps what already exists in-tree.plan-merge and split-plan are simulations that explicitly never merge or split real storage.mandates.compile and coordination.admit; a yard is where work happens, not what authorizes it.A module is a strong claim about a narrow thing. Rely on it for exactly what it is.
yards.list exists with a real id, venue and rules pack, not a planned or templated entry.*/**/all can never be covered by a bound.from is refused.migrate moves the recorded venue and commits a proof; Durable Objects stay where rehoming.plan puts them.plan-merge or split-plan changed anything. Both report wouldMergeDos/wouldSplitDos as false and touch nothing.mark-ephemeral makes promotion permanently refused for that fork.A post is addressed by role + yardId, never by DID, so re-staffing it does not require anything that depends on it to notice or change.
An earlier version of apply took a manifest and persisted it with no diff, no plan and no approval check at all. That hole is closed; every apply now goes through plan or a bound.
If the current manifest pack cannot be read, apply refuses with 503 rather than treating the organization as having no existing grants.
import always answers 501 until its own contract document is marked ready, regardless of store state.*, ** or all; that floor is not configurable down.list and get are exposed over MCP; create, plan, apply, fork, migrate and teardown are REST-only operator actions today.Authenticate with a workspace API key as a Bearer token. The base URL is https://api.intramedial.com.
/api/v1/acp/yards/listList this workspace's registered yards./api/v1/acp/yards/getRead one yard by id.coordination.yards.listList yards as an MCP action.coordination.yards.getRead one yard as an MCP action.roles.charters45Roles and postsStaff a post in a yard once, and let every dependent bind to the role itself, so the holder can change hands without anything that relies on it noticing.previews.list46Pull request preview arenasGet one disposable arena per pull request, forked with participants hidden and a sample of the data, removed on its own even if nobody tells it to be.mandates.compile03Mandate studio and replayWrite an agent's charter as code, see what it would change about who may do what, and apply it as the mandate's next version.parley.open09Parley neutral arenasGive agents or organizations neutral ground to negotiate or settle a dispute, under rules both sides accepted, with no trace left once the talk ends.directory.lookup43Gatehouse front doorLet a visiting agent from another organization find your published door, knock, and wait to be admitted to a room on your terms.settlement.list47Settlement and escrowHold money against an agent-payment mandate until delivery is confirmed, with a record that says plainly when funds actually moved and when they did not.