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…
compliance.packModule 54
Plane module
Compliance evidence packs
See every control of the regulatory map, with exactly what this workspace can evidence today and what it cannot, kept listed either way.
compliance.pack covers fourteen controls across the EU AI Act and NIST AI RMF, measured against live evidence actually available. Its pack action invokes an export wrap for an article; the evidence map with named gaps is read from coverage and evidence-pack instead.
Intralock · Leases · Parley · Fleet Map
A Trustvice Product
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 published desc – mapping evidence to obligations, listing gaps – describes coverage/evidence-pack, not pack, whose own request and response the catalogue shows. pack invokes an export wrap and returns { pack, wraps, invoked, artifacts }, with no controls or gaps.
Record
The record
What gets recorded
controls
From coverage: each control's id, framework, article or clause reference and its evidence state.
gaps
The controls coverage reports as not evidenced, listed by id, never omitted.
pack
From pack: the requested article's export-wrap identity.
The export wrap ids invoked for the requested pack.
invoked
Whether the export actually ran; false when export runtime is unbound.
needs
any or all: whether a control needs one piece of its named evidence, or every one of them, to count as evidenced.
Mechanism
Step by step
How it works
Coverage is measured, not asserted
coverage checks each control's named evidence sources against what is actually observed: real ledger event kinds, the dispatcher's own module table, and whether export runtime is bound.
A gap is never silently dropped
Every control must appear in a coverage report as evidenced, partial or gap; a control missing from the report is a hard failure, not a possible oversight.
A pack invokes a real export
pack with an article id such as art12 looks up its export wrap and invokes it through the F1 export runtime, skipping cleanly when that runtime is unbound rather than minting a fake receipt id.
Certification language is screened
screen and evidence-pack run text, including any operator-supplied label or note, against rules matching compliance-assertion, legal-advice, judgment-equivalence and guarantee phrasing by sentence shape, and refuse anything that trips one.
Try it
Live demo
Run it from this page
GET/api/v1/acp/compliance/list
// 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. compliance.pack 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.
A compliance lead reads coverage for Article 12's record-keeping control and sees exactly which evidence sources are live, not a blanket yes.
Exporting an article's evidence bundle
pack with art12 invokes the EU AI Act Article 12 export wrap, producing a real artifact only when export runtime is bound; otherwise it skips, named as such.
Catching an over-claim before it ships
screen rejects a note that asserts outright compliance rather than describing linked evidence, before that note ever becomes part of a pack.
Tracking four frameworks in one pass
A workspace reads coverage across EU AI Act and NIST AI RMF controls in one pass, rather than two separate mappings.
When to use something else
Certifying conformity. A pack maps evidence to obligations and screens out assertions that it certifies anything.
Duplicating F1's own export actions. This module wraps them; it does not reimplement export logic itself.
Assuming pack returns a coverage table. It invokes an export wrap and returns that invocation's own shape, not { controls, gaps }.
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 control can never silently disappear from a coverage report; the report fails outright if one is missing.
Coverage is measured against live ledger event kinds, the dispatcher's real module table and export-runtime availability, not a self-declared checklist.
Text asserting compliance outright, offering legal advice, or guaranteeing an outcome is refused by screen and evidence-pack before it ships.
It does not
That evidenced coverage means conformity. The module maps evidence to controls; it explicitly does not certify anything.
That pack's response shape matches coverage's. The two actions return different shapes for different jobs.
That every control framework this maps covers every applicable law. Fourteen controls across four frameworks are enumerated in code; nothing beyond that list exists here.
Details
Build notes
Before you build
Only list and pack are MCP actions
evidence-pack, coverage, screen and map have no MCP or contract action id; the dashboard console calls them directly over REST, keeping them as three distinct operator actions, not one blended call.
Article 50 is also mapped
Beyond the Articles 9, 12, 14 and 15 the catalogue names, the code also maps EU AI Act Article 50 (transparency), among fourteen controls total across all four frameworks.
Article 14 stays free on every plan
Article 14's export wrap is a policy pack, free on every plan; Articles 9, 12 and 15 need the paid compliance-exports entitlement.
Limits and metering
pack invokes an export wrap for an article; it does not itself return a controls-and-gaps table.
evidence-pack, coverage, screen and map have no MCP or contract action id; call them over REST.
A coverage report that cannot account for every known control fails outright rather than returning a partial list.
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
POST/api/v1/acp/compliance/packInvoke an article's export wrap.
GET/api/v1/acp/compliance/listList the controls this workspace is covered for.
GET/api/v1/acp/compliance/coverageMap every control to its evidence state, gaps included.
MCP actions
MCPcoordination.compliance.packInvoke an export wrap as an MCP action.
MCPcoordination.compliance.listList covered controls as an MCP action.