AIDAL.
VerifyRegulationsDashboardGet API key
Public transparency

What AIDAL actually looks like
from the outside.

Real, unpadded numbers — how much runs through the platform, whether the anchor system has actually held up, and every time it hasn't.

…
Decisions — development use
Across — founder development, demo, and integration accounts. Not external customers.
…
Decisions — internal testing
Generated by automated security and integration testing across — accounts. Retained immutably, excluded from the figure on the left.
0 external customers. Every account above — all of them, and all of the decision volume with them — is the founder's own usage. No company outside AIDAL has signed up yet. Said plainly here instead of letting the raw numbers imply otherwise.
Anchor system history
Loading…
Platform incident log

Incidents about AIDAL's own infrastructure — not customers' private AI-incident reports, which stay confidential to the company that filed them.

GPG signing key rotatedresolved2026-07-24
The original anchor-signing key existed only as a GitHub Actions secret, with no backup kept outside it. Secrets are write-only by design — once that was the only copy, it was unrecoverable, confirmed by direct search rather than assumed. A new key was generated, backed up in two independent locations, and rotated in. Anchors dated 2026-07-24 and earlier still verify against the archived old key; anchors from 2026-07-25 onward verify against the current one.
3 early anchor signatures don't verifydisclosed2026-05-01 to 2026-05-03
Found during testing, not by an external report. The signatures published for these 3 dates don't match their currently-published file contents. Every anchor from 2026-05-04 onward verifies correctly. 2026-04-30, the very first anchor, predates signing being implemented and has no signature at all.
Daily anchor job went silent for 11 daysresolvedearly operation
The anchor job originally ran as an in-process background thread inside the API server. It stopped running for 11 days without anyone noticing — an in-process thread dying is invisible from outside the process. It now runs on an external GitHub Actions cron instead, specifically because a failed scheduled run emails the repo owner automatically; a silently-dying thread does not.
This page shows aggregate, platform-wide numbers only. It does not reveal any single company's volume, decisions, or incidents unless that company has separately and explicitly opted in to being named — nothing does that yet.
Found a flaw in any of this? anthony@tryaidal.com. We'll publish what you find.