Layer 01
Horizontal AI law
The AI Act governs broader AI-system obligations and risk logic. It matters, but it is not the only text that explains how automated-driving approval works.
- EU AI Act
- Implementation timeline
- Support and guidance layer
Learn the regulation stack, not just isolated documents
A visual entry point for standards, regulation, and approval-oriented learning.
This surface is built on top of the vault’s standards domain. Its job is not to mirror legal text, but to make the structure easier to enter: what belongs to horizontal AI law, what belongs to vehicle approval, what belongs to UNECE rulemaking, and what supports the engineering evidence layer.
AI Act
EU 2022/1426
WP.29 / GRVA
R155 / R156 / R157
ISO/SAE 21434
Regulation Stack
Start by separating the layers instead of mixing “Europe regulation” into one bucket.
Layer 02
EU sector-specific ADS approval
This is where type approval, automated-driving-system requirements, testing, ODD, safety management, and reporting become much more operational.
- EU Regulation 2022/1426
- Provision map
- Technical service layer
Layer 03
UNECE institutional and instrument layer
WP.29 and GRVA organize a wider rulemaking and harmonization space. Instrument-level reading here is often where detailed assisted- and automated-driving requirements become visible.
- WP.29
- GRVA
- UN R155 / R156 / R157 / R171
Layer 04
Cross-cutting assurance and engineering support
These are not always market-entry laws by themselves, but they shape how evidence, cybersecurity, software updates, and safety work become legible.
- ISO/SAE 21434
- ISO 26262
- Vulnerability disclosure and handling
Learning Routes
Different questions should enter through different paths.
01
AI Act route
Use this when the question is about high-risk logic, obligations, implementation timing, or how to study the Act without drowning in article order.
Architecture
Timeline
Study sets
Case layer
02
European automated-driving map route
Use this when the question is how AI Act, EU vehicle approval, UNECE instruments, and market-entry signals connect instead of standing alone.
Map
2022/1426
WP.29
Company entry signals
03
Cybersecurity and software-update route
Use this when the practical question is how R155, R156, and engineering standards such as ISO/SAE 21434 actually support market-facing work.
R155
R156
21434
Evidence layer
04
Market-entry and approval route
Use this when the question is less about one law and more about how a company actually becomes legible to authorities, technical services, and Europe-facing stakeholders.
EU framework
Technical service
Germany layer
Signals
Featured Topics
The first public standards surface should lead with bounded, high-value anchors.
European automated-driving regulation map
The best first answer to “what does Europe regulation actually mean for automated driving?” is a map, not a single document page.
EU AI Act study architecture
A staged study structure that turns one long regulation into learnable clusters, practical routes, and scenario return points.
EU Regulation 2022/1426
A closer approximation to real automated-driving approval mechanics than the AI Act alone, especially once ODD, testing, authority review, and technical services come into view.
WP.29 / GRVA / R155 / R156 / R157
A practical path for understanding cybersecurity, software updates, and automated-driving-specific requirements inside the wider UNECE structure.
Reading Approach
“Make it readable” does not mean “make it loose.”
Readable before intimidating
This surface tries to make regulation enterable through structure, not through oversimplification. The first job is to reduce confusion about what belongs to which layer.
Layered, not flattened
Regulations, standards, institutions, and market signals do not do the same work. A good learning site should separate them before it compares them.
Original text still matters
Public explanation can guide reading order and build intuition, but it should stay anchored to the source set and leave space for returning to the official text.
Next Build Steps