EU AI Act · RCAN §22-26 5 endpoints live · 2026-04-24

Filed with regulators.
Not just generated.

Five RCAN §22-26 attestation packets — FRIA, safety-benchmark, IFU, incident-report, EU-register. One robot-md emit-* command per packet. All five endpoints live at Robot Registry Foundation.

§ 01 — The 5 packets

Five attestation packets. One command each.

Each packet covers a different EU AI Act obligation. All are signed with your robot's key and routed to the live RRF endpoint.

§22
FRIA Fundamental Rights Impact Assessment
EU AI Act Art. 9: pre-deployment assessment of impact on fundamental rights. Automated checklist derived from ROBOT.md capabilities, safety gates, and RCAN LoA level. Filed before first deployment.
# emit + sign + submit robot-md emit-fria ROBOT.md \ --sign --submit
Live /api/compliance/fria →
§23
Safety benchmark ISO 42001 self-assessment
ISO 42001 + RCAN §23: structured safety self-assessment linked to the robot's RRN. Covers hazard analysis, control measures, and residual risk. Signed envelope with audit-trail hash.
robot-md emit-safety-benchmark ROBOT.md \ --sign --submit
Live /api/compliance/safety-benchmark →
§24
IFU Art. 13(3) Instructions for Use
EU AI Act Art. 13(3): machine-readable instructions for use — what the robot can and cannot do, under what conditions, with what safety constraints. Derived from ROBOT.md capabilities and body sections.
robot-md emit-ifu ROBOT.md \ --sign --submit
Live /api/compliance/ifu →
§25
Incident report Art. 72 serious incident notification
EU AI Act Art. 72: structured incident report — timestamped, linked to RRN, signed. Required within 15 days of a serious incident. robot-md provides the structure; the operator provides the incident narrative.
robot-md emit-incident-report ROBOT.md \ --description "..." \ --sign --submit
Live /api/compliance/incident-report →
§26
EU Register Art. 49 Per-model EU AI Act registration
EU AI Act Art. 49: registration of the AI system in the EU database. Requires an RMN (model number). Routed through RRF to the official register endpoint. robot-md handles the RCAN-signed envelope.
robot-md emit-eu-register ROBOT.md \ --sign --submit
Live /api/compliance/eu-register →
§ 02 — Status check

Check filing status in one command.

robot-md compliance status queries RRF and returns which packets have been filed and accepted. 

$ robot-md compliance status ./ROBOT.md
# robot-md compliance status ./ROBOT.md # RRN: RRN-000000000003 | RMN: RMN-000000000004 ✓ fria ACCEPTED 2026-04-24T11:32:01Z ✓ safety-benchmark ACCEPTED 2026-04-24T11:33:15Z ✓ ifu ACCEPTED 2026-04-24T11:34:02Z ✓ incident-report NONE no incidents filed ✓ eu-register ACCEPTED 2026-04-24T11:35:40Z Ready for submission · 4/5 packets filed · 0 incidents

Note: pass the file path (./ROBOT.md), not a directory, to avoid issue #32 (directory-vs-file resolution bug, tracked).

§ 03 — Identity prerequisite

Register first. File second.

All five compliance packets require a valid RRN. Run robot-md register ROBOT.md before emitting any packets. See the Registry page for the full registration flow including key generation and RMN assignment.

Ready for submission All §22-26 endpoints live · Signed envelopes · RCAN 3.0
Register your robot → Let Compliance-bot file for you → RRF live endpoints →