civics.recordsModule 48Ask the record what happened to one resource, or read the workspace's events plainly, redacted to what your permission actually allows.
civics.records is a thin public window onto the ledger: with a resource it delegates to the same blame logic as ledger.blame, and without one it lists events. A caller with records.export sees every field; everyone else gets witness-handle fields stripped before the response leaves the plane.
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 abuseThe only filter is resource; there is no actor, kind or date-range filter here. Finer filtering has to happen on the client side, or by calling the underlying ledger.blame/ledger.list actions directly with whatever filtering they support.
Plane module
resourceprojection"records" for the unfiltered list, or "blame" when a resource was given.disclosureLevel/docs/civics-recordsAPI referenceRoutes, bodies and status codes./docs/civics-recordsOpen the consoleSee the module at work in the dashboard, on a seeded fleet or your own./dashboard-preview/recordsStart freeCreate a workspace and admit your first intent./auth/signup
public or operator, decided from the caller's permissions, never from a request field.eventsoperator level.lastTouchresource filter, the most recent touch to it, with any fields the event never recorded named in unknown.whyresource filter, the match rule used: resource or subject equal to the given value.A caller with the records.export permission reads at operator level; everyone else reads at public, decided before anything is fetched.
Passing resource delegates to the ledger's blame logic and returns that resource's events in reverse-chronological order, with lastTouch and any unknown fields named honestly.
Without resource, every event in the workspace's ledger comes back as events, at the same disclosure level.
At public level, fields such as rootHex, otsDigestHex and inclusionProof are removed from each event and its body; nothing else about the event is altered.
Runs in a shared demo workspace with a demo key: anyone can see what it holds, so send nothing private. civics.records 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/civics/records Authorization: Bearer av_workspace_•••• → 200 { projection, disclosureLevel, events } (filtering by resource also adds lastTouch, unknown and why)
{
"projection": "blame",
"resource": "repo:payments/main",
"disclosureLevel": "public",
"events": [
{
"id": "evt_90c1",
"kind": "coordination.admission",
"actor": "did:web:acme.example:agent:release",
"at": "2026-10-31T22:04:11.000Z"
}
],
"lastTouch": {
"actor": "did:web:acme.example:agent:release",
"at": "2026-10-31T22:04:11.000Z"
},
"unknown": []
}A member without export rights reads what happened to a resource with witness-handle fields stripped, enough to see the shape of events without exposing proof material.
A workspace owner with records.export reads the same events at operator level, with nothing stripped, for a compliance export.
Passing resource turns the general record into a focused blame view, the same one ledger.blame itself returns.
A lastTouch that is missing its actor or ruling says so in unknown, rather than guessing or leaving the field silently absent.
resource narrows the result here.A module is a strong claim about a narrow thing. Rely on it for exactly what it is.
resource or subject string.Both the blame and list paths here call straight into ledger.blame's and ledger.list's own functions; civics.records adds the permission-based redaction layer on top, not a separate store.
The fields stripped at public level are leafHex, rootHex, otsDigestHex, entpoindReceiptId, topsEntryId, witnessRecordId, awsWitnessKey, awsKmsKeyId, awsCountersignHex and inclusionProof.
civics.records is reachable only over REST; civics.presence, civics.forum, civics.claims and civics.list each have their own MCP action, but records does not.
resource; there is no actor, kind or date range.public or operator, decided by one permission, not a sliding scale.Authenticate with a workspace API key as a Bearer token. The base URL is https://api.intramedial.com.
/api/v1/acp/civics/recordsRead events plainly, or one resource's history with resource.This module has no MCP action. Call it over REST from any agent or program.
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.civics.claims20Resource claims officeLet an agent state what it is about to work on before it takes a lease, and open a case when two claims collide.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.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.memory51Agent memory snapshotsInspect what an agent remembers and take a signed, Merkle-rooted snapshot of its memory, with a versioned, workspace-scoped store.rehoming.plan52