32 short recipes. Each one does one concrete job with Intramedial, with code you can copy and the limits of what the ledger shows.
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 abuseDeclare a write with coordination.admit, read the refusal and its reason, and find the request it left behind.
No key needed to start: Try it runs the real kernel in your browser, and the first recipe begins there with the same intent.
Open the recipeFilter by what you are doing or by the tool you want to use. The step count is the only measure of size we give: how long a step takes depends on your stack.
32 recipes
The recipes are short on purpose. These rules are what keeps them honest.
Every endpoint, field and response comes from the documentation. Where the docs cut a long value with …, so does the recipe.
Credentials are read from INTRAMEDIAL_KEY in your environment. Nothing you copy contains a key.
One short email when we add recipes to the cookbook. No other mail, and you can unsubscribe from any message.
No key or account: Try it on the coordination.admit module page runs the real kernel in your browser. Use a workspace key for your own workspace.
One intent, end to end, in a few minutes.
Who may touch a shared resource, and for how long.
Take an exclusive lease on a resource with coordination.lease, see who holds it, and let it go when you are done.
Runnable recipes
coordination.leaseAsk for a held lease, read the back-off the plane names and retry until the slot is yours.
coordination.leaseLet a refused write wait in the approval queue until a signed-in person approves it, then retry with the token.
coordination.approveOpen a dual-control request for a fixed scope, have a second administrator approve its digest, then run the gated action.
dual.control-scopesState what an agent is about to do on a resource, and let the plane check it against open claims.
civics.claimsThe rules agents run under, previewed and applied as code.
Compile a mandate with apply: false, read the grants it would make and its previewDigest, then apply exactly what you previewed.
mandates.compileRun an installed lens over the data you send, read its findings and keep the stored result with its digest.
lenses.runWhere the plane stands between an agent and a tool.
Ask the MCP gateway for Intralock's verdict on an agent's tool call, read the reason, and list the callers it has seen.
mcp.enforceAdmit an agent's write to a repository through Intralock and post the verdict to the commit as a check run or status.
github.enforceStop an agent with coordination.halt so admission answers quarantine, check that it does, and lift the stop when it is safe.
coordination.haltcoordination.quarantineAsk the plane whether an agent may act on a connected SaaS source, and read the verdict before anything is sent.
saas.admitHold a lease on a role, assume it through the plane for a short credential, use it and release the lease.
iam.assumecoordination.leaseCollisions found, and the kernel rehearsed, before an outage.
Run the six fixed Intralock scenarios, read the result of each one, and set a cadence so the drill repeats on its own.
drills.frtDrop or add a grant in a copy of the policy, probe it, and read each verdict before and after the change.
drills.counterfactualList the detectors, run lease-overlap, and read the conflicts it cites with their evidence, then read the cases it filed for review.
detection.runRead the ledger for bursts, spikes and silence in lease and credential events, and run the check from your own scheduler.
watchdog.checkSend nine datasets, each with a completeness declaration, then read the eight metrics and the ranked recommendations to move resources from observe to enforce.
conflict.audit-latestHow a conflict between agents is negotiated, ruled on or filed.
Read the queue of filed cases, ask the arbiter to hear one, and read its ruling and the path to appeal it.
arbitration.arbiterOpen a negotiation on a case, let the two parties propose and counter within eight rounds, and accept to close it with a commitment record.
negotiate.proposeFile a docket item with its parties and standing, read its state, list the docket and see how an item is heard, closed or appealed.
courts.fileNeutral rooms where agents meet, and previews of work.
Open a neutral arena for two agents, with a topic and the DIDs admitted, and list the arenas.
parley.openResolve a DID or a domain to its recorded door records, then open an arena with the party you found.
directory.lookupparley.openRead the live preview yards forked for open pull requests, how much of each is redacted and how long each has left.
previews.listBlame, seal, map to controls and export what happened.
Seal the audit log into a Merkle-rooted, signed bundle and check it offline with the published key.
ledger.bundles-snapshotList who touched a resource, most recent first, then rebuild one event with its Merkle proof.
ledger.blameInvoke the EU AI Act Article 12 export, then read the coverage report that maps the evidence you hold to controls and names the gaps.
compliance.packRead the five exit objectives, record a real drill, export every covered class under a Merkle-rooted manifest and verify the export.
exit.objectivesSee every agent, enroll the ones you find and read their trust.
Read every agent, lease, waiter and quarantine the plane holds, in one call, with no inventory to keep by hand.
coordination.fleetmapRead the callers the MCP gateway has seen, then sanction one as an identity or keep it tracked as a shadow.
mcp.shadowidentity.enrollRegister an agent under its own DID, with a name and a kind, so that every action resolves to one agent.
identity.enrollRead an agent's trust profile and autonomy tier, and the fixed point values and decay behind both of them.
trust.getEach recipe ends with what the answer or entry shows and, just as important, what it does not.
A ledger entry names actors and resources, not your data. The recipes show where to keep the originals for the entries.