The AI Act expects logging for high-risk systems and a disclosure to people who deal with an agent. Intramedial admits each action under a versioned mandate, so the record exists because the plane ran, not because someone wrote it up.
mandates.compile coordination.admit conformity.sweep 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
A Trustvice Product
compliance.pack ledger-bundles.snapshot A document that says what the system should log is not the log. Regulators and customers ask for the log, the rule it ran under, and proof that neither was rewritten.
Which version of the rule was in force when the agent acted?
Does every agent that talks to a person carry the disclosure label?
Can we hand an auditor the evidence without giving them our systems?
Versioned mandates answer the first, a disclosure sweep the second, and a signed bundle the third. Each is evidence of one narrow fact, and none of them is a certificate of conformity.
AppliesDepends on the system’s risk class
High-risk AI systems must allow automatic recording of events over their lifetime, and providers must keep the logs for a period. Dates differ by role and class, so read the Act and ask counsel which apply to you.
Official text ↗AppliesDepends on the system’s use
People who interact with an AI system must be told so, unless it is obvious. The conformity sweep lists agents that may reach a person without a label, so gaps surface before a change ships.
Official text ↗AppliesOngoing
Enterprise buyers now ask for the same three things about any agent that can move money or data: the rule, the log and an independent check. A signed bundle answers faster than screenshots.
Legal references are summarised and dated as of October 2026. They are given so you can see where the need comes from, not as legal advice. Read the official text, and ask counsel how it applies to you. Intramedial does not make any organisation compliant with any law.
The charter is written in the mandate studio and compiled into a signed policy snapshot. The preview shows what it would admit or deny before anything is applied.
Each call to coordination.admit is decided against that snapshot, and the entry names the snapshot used, so the rule behind any decision can be named later.
The compliance module maps controls from the AI Act and NIST AI RMF to evidence you actually have, and lists what is missing.
You seal a stretch of the chain into a signed bundle. The auditor verifies it against the published key without calling Intramedial.
Each module decides one kind of thing. Open a module for its fields, limits and errors.
mandates.compileCompiles the rule an agent runs under and previews its effect, so the version in force can be named.
Open module →coordination.admitAdmits each action against the compiled snapshot and records which snapshot decided it.
Open module →conformity.sweepLists agents that may reach a person without the disclosure label Article 50 asks for.
Open module →compliance.packMaps Article 12 and other controls to the evidence this workspace holds, and names the gaps.
Open module →ledger-bundles.snapshotSeals a signed bundle of the chain that an auditor can check offline.
Open module →Acme compiles a mandate for its billing agent without applying it, reads the preview, and later pulls the Article 12 evidence pack for its auditor.
curl -sS https://api.intramedial.com/api/v1/acp/mandates/compile \
-H "Authorization: Bearer $INTRAMEDIAL_KEY" \
-H "Content-Type: application/json" \
-d '{
"source": "mandate billing-writes\nallow write on repo:payments/main for did:web:acme.example:agent:billing",
"apply": false
}'{ "id": "art12" }
→ 200 { pack, wraps, invoked, artifacts }Request fields as documented: /docs/compliance-pack
A ledger entry is evidence of a narrow fact: this decision was made on this input under this policy at this time, and the chain has not changed since. It is not a certificate, an audit or legal advice, and it does not by itself satisfy any legal obligation.
Give an auditor, a customer or yourself the record of what your agents did, scoped to the reader, and leave with it intact.
civics.records ledger.blame exit.objectives ledger-bundles.snapshot Hold a risky intent until a person approves it, and make destructive changes wait for a second, different person.
coordination.approve dual-control.scopes civics.asks coordination.admit Rehearse how your agents behave when they fight over the same ground, then settle real conflicts by negotiation, arbitration and a person.
drills.frt detection.run negotiate.propose arbitration.arbiter The Try it terminal runs the real admission kernel on your machine. It needs no account and sends nothing, and each decision comes back with its reason.
