watchdog.checkModule 36Catch a plane that is issuing leases or credentials too fast, or has gone quiet, by reading the ledger instead of asking the plane.
watchdog.check reads the ledger and reports rate anomalies in two families: lease grants, and credential issuance through iam.assume and iam.warehouse. It raises a rate-spike, a burst by one actor and . It imports nothing from the modules it watches and stores nothing.
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
went-silentwatchdog/check answers when it is called. No cron, queue or page is wired to it, so a finding is seen only when something reads the route. Call it from your own scheduler and route findings to your alerting.
findingscoderate-spike, burst or went-silent.family/docs/watchdog-checkAPI referenceRoutes, bodies and status codes./docs/watchdog-checkOpen the consoleSee the module at work in the dashboard, on a seeded fleet or your own./app/watchdogStart freeCreate a workspace and admit your first intent./auth/signup
lease or credential.actorburst, and null for the other codes.observed0 for went-silent.baselinenull for silence.whyscannedbackgroundtuningnowMs to pin the clock.GET /api/v1/acp/watchdog/check lists the workspace's ledger events and keeps two families: coordination.lease, and iam.assume with iam.warehouse.
Events fall into ten buckets of 60,000 ms. A rate-spike is raised when the newest bucket is at least four times the median of the earlier ones, and at least five.
A burst is raised for an actor with ten events of one family inside 5,000 ms. The finding names the actor and the count.
went-silent is raised when a family has been absent for 15 minutes while at least three other ledger events arrived in that time. A ledger that is quiet everywhere raises nothing.
The response carries findings, how many events were scanned, how many were background, and the watched kinds, so a silence finding can be checked against the other traffic.
Runs in a shared demo workspace with a demo key: anyone can see what it holds, so send nothing private. watchdog.check 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/watchdog/check Authorization: Bearer av_workspace_•••• → 200 { at, findings, scanned, background, watched }
{
"at": "2026-11-01T09:15:00.000Z",
"findings": [
{
"code": "went-silent",
"family": "credential",
"actor": null,
"observed": 0,
"baseline": null,
"why": "no credential events at all while 14 other ledger events were written in the last 15 minutes – zero is not quiet when the ledger is still moving"
}
],
"scanned": 57,
"background": 41,
"watched": {
"lease": [
"coordination.lease"
],
"credential": [
"iam.assume",
"iam.warehouse"
]
}
}It keeps issuing credentials but stops writing them down. The ledger stays busy on other kinds, so went-silent fires for the credential family.
One agent takes leases in a tight loop. burst names its DID and how many it took.
A fleet starts taking leases together. The newest bucket passes four times the median and rate-spike fires.
A tenant with no traffic at all raises no finding, because silence counts only while other ledger events keep arriving.
coordination.admit; the watchdog reads history.detection.run.A module is a strong claim about a narrow thing. Rely on it for exactly what it is.
coordination. ledger events, so a caller cannot forge the lease events it counts.went-silent finding, and only while other traffic continues.A request may pass tuning with bucketMs, buckets, spikeMultiple, minSpike, burstMs, burstCount, quietMs and aliveEvents. The defaults are 60,000 ms, 10, 4, 5, 5,000 ms, 10, 15 minutes and 3.
Credential issuance appears in the ledger as a fact: who, and against what. The key, secret and tokens are not written.
A failed write of a lease or credential event raises no error. The gap is what went-silent exists to catch.
GET /api/v1/acp/watchdog/families returns the watched kinds and the default tuning.
iam.assume and iam.warehouse.actorDid, holder, principal or did). Events with none count toward spikes but not bursts.tuning applies to that call only. No route stores a threshold or a schedule.Authenticate with a workspace API key as a Bearer token. The base URL is https://api.intramedial.com.
/api/v1/acp/watchdog/checkRun one pass over the ledger and return findings./api/v1/acp/watchdog/familiesList the watched kinds and the default tuning.This module has no MCP action. Call it over REST from any agent or program.
detection.run07Conflict detectionTurn contention between agents into a filed case with the evidence attached, instead of an alert nobody can answer.drills.frt35Turf-war drillsCheck on demand, or on a cadence you set, that the kernel's core guarantees still hold, and keep a scorecard of every run.coordination.lease02Resource leases and queuesHold a resource for one agent at a time, with a lease that lapses on its own and a queue for the agents that have to wait.conflict-audit.latest33Conflict audit reportRead the latest conflict audit: where agents contended, how well the record backs it, and which resources are ready to move from observe to enforce.drills.counterfactual34Counterfactual simulationAsk what a policy change would do before you make it: re-run chosen requests with grants dropped or added, and see each answer change.conformity.sweep37SI/AI disclosure conformityFind which agents may speak to a person without a disclosure label before an authority does, and test a fleet change before you make it.