Regulated AI Navigator
Turn an AI use case into its EU AI Act risk class, the regulations it triggers, the obligations, the architecture and the evidence you owe — in about two minutes.
Community-curated knowledge graph, peer-reviewed by experts across law, engineering and governance. Every change traceable →
Every regulation in the graph resolves into concrete technical components — through an article obligation, a control objective, a design pattern or an evidence artefact that a component must produce. Pick a regulation to see its technical surface, how each component is derived, and in which of the triggering use cases it is actually part of the required stack. The gap counts show where the graph reaches a component that no use case yet requires — those are open contribution targets, not settled answers. Open the full graph →
Domain safety regulators whose regimes AI must complement, never replace: EASA (aviation), ERA (rail), NERC CIP (North American grid security). Predictive systems support — they do not substitute — mandated physical maintenance and protection duties.
Operator stop controls and degraded-mode fallbacks; real-time override (veto) channels for HOTL operation.
Software bill of materials incl. model weights and datasets; automated vulnerability patching pipeline.
Verified boot chain and hardened runtimes for edge/IoT deployments per CRA security-by-design.
One procedure reconciling AI Act Art. 73, GDPR Art. 33 (72h), DORA and NIS2 (24h/72h) timelines and recipients.