# NCRC Regulatory Hub - Design Baseline

## Public expert-review attribution rule

Public regulatory pages use neutral labels such as `Expert View`, `Expert Analysis`, `Discussion Point`, and `Open Regulatory Question`.

Individual expert names and affiliations are not displayed publicly by default.

Internal provenance must retain the source file, source version, author/reviewer identity when known, review date/status, and the distinction between official source material and expert interpretation.

Public attribution of an individual expert requires a later explicit publication decision. Removing public attribution must never remove internal provenance.

## Information hierarchy

Every regulatory subject uses four visibly distinct evidence classes:

1. Official regulation
2. NCRC explanation
3. Expert View
4. Open Regulatory Question / Grey Zone

Expert View must never be presented as statutory text or as an official legal interpretation.

## Regulatory Hub structure

### Overview
A short explanation of why automotive cybersecurity can involve multiple overlapping regulatory frameworks and why scope depends on the product, vehicle category, market placement and type-approval context.

### Frameworks

#### UN R155
- Cyber security and Cyber Security Management System (CSMS)
- Scope
- Approval and CSMS
- Vehicle-type requirements
- Development, production and post-production lifecycle
- Annex 1 - Information document
- Annex 2 - Communication
- Annex 3 - Approval mark
- Annex 4 - CSMS certificate
- Annex 5 - Threats and corresponding mitigations
- Official sources
- Link to NCRC R155 traceability in Threat Register

#### UN R156
- Software updates and Software Update Management System (SUMS)
- Scope
- Approval and SUMS
- Software update requirements
- RXSWIN / software-identification context
- Annex 1 - Information document and declaration
- Annex 2 - Communication
- Annex 3 - Approval mark
- Annex 4 - SUMS certificate
- Official sources

#### EU Cyber Resilience Act
- Regulation (EU) 2024/2847
- Products with digital elements
- Scope and exclusions
- Essential cybersecurity requirements
- Vulnerability handling
- Economic-operator obligations
- Product categories and conformity-assessment context
- Market surveillance
- Official and consolidated sources

### Scope interaction

#### Type Approved Zone
Vehicle/products clearly handled through the applicable type-approval framework and automotive cybersecurity/update requirements.

#### CRA Zone
Products with digital elements placed on the EU market that are not covered by an applicable sector-specific exclusion.

#### Grey Zone
Products, software, hardware, embedded devices or tools for which the boundary between vehicle type approval, component/product placement on the market, and CRA applicability requires further assessment.

All statements in this section must be tagged by authority level: Official / NCRC explanation / Expert View / Open question.

### Automotive ecosystem views
- Passenger/commercial vehicles and trailers
- L-category vehicles
- Agricultural/off-highway ecosystem
- Non-road mobile machinery
- Automotive supply chain
- Software components
- Hardware and embedded connectivity units
- Development/production/service tools and toolchains
- EV charging and infrastructure
- Workshop and diagnostic equipment
- Aftermarket digital products
- Cloud and digital services

### Expert View
The first Expert View source is an internal discussion presentation analysing CRA and automotive type-approval boundaries. Public pages do not identify the individual author. Internal provenance retains the original file and authorship.

Key themes to preserve as expert analysis rather than legal conclusions:
- Type Approved Zone / CRA Zone / Grey Zone model
- assurance gaps deeper in the automotive supply chain
- distinction between vehicle cybersecurity compliance and component security assurance
- CRA questions around reusable software, embedded units and automotive tools/toolchains
- infrastructure, aftermarket and digital services outside the vehicle type-approval package
- off-highway, NRMM and L-category overlap questions

### Official sources
For every framework provide direct links to primary/legal sources and, where useful, consolidated/documentation versions. Clearly label legal status.

## Traceability model

Public card metadata:
- authority: official | ncrc_explanation | expert_view | open_question
- framework: r155 | r156 | cra | other
- topic
- source link when official/public
- status: current | review | open

Internal provenance metadata:
- source_id
- source_file
- source_version
- author/reviewer identity
- source_date when explicitly known
- extraction/reference location
- review status
- publication attribution decision

## Separation from Threat Register

`regulatory.html` explains frameworks and their interaction.

Threat pages show threat-specific regulatory traceability, starting with the promoted R155 review baseline.

The hub may link to the Threat Register, but should not duplicate all T-xxx mappings.

## Future extension

The information model should allow later addition of R156 and CRA traceability without changing the authority/provenance model established for R155.
