ITU Radio Regulations
Spectrum limits, captured as constraints.
An embedded radar sensing module — the system class the RF/radar recipe covers: a mixed-signal board where spectrum, EMC, environmental and fabrication standards constrain the design as hard as the sensing requirement does.

For an RF system, spectrum allocation, EMC immunity, environmental endurance and board-fabrication rules are not compliance you bolt on at the end — they are constraints the architecture has to satisfy from the first trade.
The RF/radar recipe pulls them in as tracked obligations so the design is proven against them, not merely tested against them later.
Driven by the embedded RF/radar recipe, extending the electronics recipe.
Spectrum limits, captured as constraints.
EMC limits, captured as constraints.
Environmental limits, captured as constraints.
Board-fabrication rules the allocation has to respect.
Take an RF sensing module from need to a released baseline with spectrum, EMC, environmental and fabrication constraints carried as first-class, traced obligations.
Frame the sensing requirement and the regulatory environment it operates in.
Pull spectrum (ITU), EMC (IEC 61000) and environmental (IEC 60068) limits in as constraints.
Trade the RF architecture against those constraints, not around them.
Allocate onto the board with its fabrication rules (IPC-2228 / 6018).
Close verification against every regulatory constraint before baseline.
The regulatory constraints have to be in the requirement baseline, not discovered late.
Every requirement is singular and verifiable.
Spectrum, EMC and environmental limits are captured as constraints.
A verification method is assigned to each requirement.
The initial hazard list exists.
The recipe is where a system class encodes its standards; the gate is where a human confirms they made it into the baseline.

Keep exploring