ABS Core v4.3.3
Compliance & Sovereignty

EU AI Act Compliance

Granular mapping of transparency and record-keeping requirements for High-Risk AI.

EU AI Act: Sub-Requirement Mapping

ABS Core was architected to natively satisfy the Record-keeping, Transparency, and Human Oversight requirements defined for High-Risk AI Systems (Title III, Chapter 2).

[!IMPORTANT] Legal Notice: A preliminary legal opinion on compliance with the EU AI Act and LGPD is available under NDA. This technical matrix reflects the controls implemented via code, pending external third-party audit for final certification.

Granular Compliance Matrix

Article & Sub-RequirementLegal DescriptionImplemented ABS Core ControlStatusEvidence
Art. 12(1)The system must automatically record logs of events (Record-keeping).Immutable Ledger (Ed25519) attaches each decision to the cryptographic chain before execution. [OK] ImplementedView Code
Art. 12(3)Logging capabilities must ensure a level of traceability consistent with the system's purpose.Hash-chain timestamping (RFC 3161) prevents temporal alteration of the agent's history. [OK] ImplementedTelemetry Spec
Art. 13(1)The system must be transparent enough to allow users to interpret its outputs (Transparency).OConnector Dashboard exposes the decoded intent trail (Human-readable explanations). [WARNING] In validationAvailable under NDA
Art. 14(2)Human Oversight to prevent or mitigate automation risks.Fail-Closed Interceptor blocks unauthorized routes and allows Human-in-the-loop (HITL) approval. [OK] ImplementedAir-Gapped Ops
Art. 15(1)Resilience against errors, failures, or inconsistencies (Robustness & Cybersecurity).WASM Sandbox & Secret Vault isolate credentials and prevent direct prompt injection into the kernel.⬜ Externally auditedAudit Report under NDA

Full certification of an AI system depends on the final integration (Deployment Context) performed by the client. ABS Core provides the cryptographic infrastructure to enable this approval.

On this page