Regulatory Reports — evidence packages
Generate structured reports that assemble evidence from Decision Trail, Erasure Proof, Governance Gateway and the GMP Compliance service against the articles of three EU regulations.
Each report is BLAKE2b-256 hashed for tamper detection and can be downloaded as JSON or PDF.
Every per-article finding is computed from the tenant's operational data at generation time, and can come back PARTIAL or INSUFFICIENT_DATA. A COMPLIANT finding means the checks listed for that article passed on the data GRAFOMEM holds — it is input to your own compliance assessment, not a substitute for it.
Supported frameworks
| Framework | Regulation | Articles Covered |
|---|---|---|
| 🇪🇺 EU AI Act | Regulation (EU) 2024/1689 | Art 13 (Transparency), Art 14 (Human Oversight), Art 15 (Accuracy) |
| 🔒 GDPR | Regulation (EU) 2016/679 | Art 17 (Erasure), Art 25 (By Design), Art 30 (Records of Processing) |
| 🏦 DORA | Regulation (EU) 2022/2554 | Art 6 (ICT Risk), Art 9 (Protection), Art 11 (Audit Trail) |
| 📊 Full Audit | All frameworks combined | All 9 articles across 3 frameworks |
Report structure
Each report contains per-article sections, each with:
| Field | Description |
|---|---|
title | The article title (e.g. "Article 13 — Transparency Obligations") |
requirement | The regulatory requirement text |
compliance_evidence | The data the finding was computed from (counts, flags, algorithms in use) |
evidence_basis | Which evidence fields were observed (read from the tenant's data) and which are declared (a property of the platform, stated) |
finding | COMPLIANT, PARTIAL, or INSUFFICIENT_DATA |
The overall finding is COMPLIANT only if every section is; INSUFFICIENT_DATA if any section lacks data; otherwise PARTIAL.
Example: Generate a GDPR report
curl -X POST https://api.grafomem.com/v1/reports/generate \
-H "X-API-Key: $API_KEY" \
-H "Content-Type: application/json" \
-d '{"report_type": "gdpr", "period_days": 30}'
Response (abridged):
{
"report_id": "a1b2c3d4e5f6...",
"title": "GDPR Compliance Report (2026-10-07 → 2026-11-06)",
"status": "complete",
"content": {
"framework": "GDPR",
"regulation": "Regulation (EU) 2016/679",
"sections": {
"article_17_erasure": {
"title": "Article 17 — Right to Erasure",
"finding": "PARTIAL",
"compliance_evidence": {
"erasure_proof_active": true,
"certificates_issued": 12,
"signed_certificates": 9,
"decisions_scrubbed": 4,
"signature_algorithm": "Ed25519",
"content_hash_algorithm": "BLAKE2b-128 of the pre-delete content (server-observed on the delete endpoint; caller-asserted on /v1/erasure/issue)"
},
"evidence_basis": {
"observed": ["erasure_proof_active", "certificates_issued", "signed_certificates", "decisions_scrubbed"],
"declared": ["signature_algorithm", "content_hash_algorithm"]
}
}
},
"overall_finding": "PARTIAL"
},
"content_hash": "2f9d784ac980dc17..."
}
Here three certificates were issued without a signing key configured, so Art 17 is PARTIAL.
API reference
| Method | Path | Description |
|---|---|---|
GET | /v1/reports/stats | Summary: total reports, complete count, last report date |
GET | /v1/reports/frameworks | List available frameworks with article details |
POST | /v1/reports/generate | Generate a report. Body: {report_type, period_days} |
GET | /v1/reports/ | List all reports (summaries, no content) |
GET | /v1/reports/{id} | Get full report with content |
GET | /v1/reports/{id}/download | Download as JSON file |
GET | /v1/reports/{id}/download/pdf | Download as PDF |
DELETE | /v1/reports/{id} | Delete a report |
How each finding is computed
EU AI Act
| Article | Data Source | COMPLIANT when | Otherwise |
|---|---|---|---|
| Art 13 (Transparency) | Decision Trail | at least one decision logged in the period | INSUFFICIENT_DATA |
| Art 14 (Human Oversight) | Governance Gateway | at least one active hitl_required policy | PARTIAL |
| Art 15 (Accuracy) | Compliance | GMP conformance rate ≥ 0.95 | PARTIAL |
GDPR
| Article | Data Source | COMPLIANT when | Otherwise |
|---|---|---|---|
| Art 17 (Erasure) | Erasure Proof | service active, ≥ 1 certificate in the period, all of them signed | no service or unsigned certificates → PARTIAL; no certificates → INSUFFICIENT_DATA |
| Art 25 (By Design) | Platform + Erasure Proof | signing key configured and erasure service active | PARTIAL |
| Art 30 (Records) | Decision Trail | at least one decision logged | INSUFFICIENT_DATA |
Art 25's tenant-isolation evidence is stated as what it is: logical per-tenant residency (tenant-scoped rows in shared storage), not physical segregation.
DORA
| Article | Data Source | COMPLIANT when | Otherwise |
|---|---|---|---|
| Art 6 (ICT Risk) | Governance Gateway | at least one active policy | PARTIAL |
| Art 9 (Protection) | Platform + Governance | signing configured and active rate_limit, pii_guard and content_filter policies | PARTIAL |
| Art 11 (Audit Trail) | Decision Trail + Governance | at least one decision logged | PARTIAL |
Art 9's evidence carries a policy_enforcement_scope line: governance policies are evaluated on requests sent to the evaluation endpoint and by the orchestrator — see Governance Gateway for the enforcement boundary.