Requirements traceability for AI governance
Obligations from law, standards and procurement terms are decomposed into requirements and traced to evidence from analysis, inspection or test, so gaps show before a deployment decision is taken.
GRF · Innovation Nexus
Systems engineering gives innovation governance a way to trace requirements through complex socio-technical systems. It links legal and policy requirements to design, testing and operation, exposes interfaces where failures pass between organisations, and supports readiness gates for programmes that move technology from laboratory to use.
Systems engineering is an interdisciplinary approach to designing and managing complex systems over their life cycle. It focuses on requirements, interfaces and interactions so that the whole performs as intended. In innovation, artificial intelligence and industry and robotics, systems engineering exposes interfaces where failures propagate between components and organisations. It supports designing interconnected infrastructure with explicit dependency management. The canonical description is on the STEM Commons.
Obligations from law, standards and procurement terms are decomposed into requirements and traced to evidence from analysis, inspection or test, so gaps show before a deployment decision is taken.
Technology, integration and adoption readiness are assessed at programme gates, so funders decide on scale-up with the maturity of both the technology and its users in view.
System-theoretic hazard analysis traces how a robot, its software, its operators and its supervising authority interact, finding control gaps that component testing misses.
Night lights, population density and flood water over China, from NASA GIBS. Each layer carries its own date.
The interactive map needs JavaScript; the layer list and sources are below.
Layers 3
Connected activity, for this page
Keyboard, with the map focused
Hold Ctrl or ⌘ and scroll to zoom
Latest available
NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © OpenStreetMap contributors (ODbL) · Natural Earth
Loading the latest NASA imagery.
Drag to move. Ctrl or ⌘ and scroll, pinch or the buttons to zoom; hover for the values under the pointer; reset returns to the region.
Connected activity, framed on China.Satellite and model products as NASA publishes them, each with its own date. They are indicators, not assessments of any place.
Layers and dates
Datasets and records used by systems engineering on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.
| Data | Role | Label |
|---|---|---|
| Requirements and traceability records | Links between obligations, design and evidence | DECLARED |
| Test, verification and validation records | Evidence that requirements are met | OBSERVED |
| Standards texts (ISO/IEC/IEEE 15288, ISO 10218, IEC 61508) | Life cycle and functional safety requirements | Published statistics |
| Programme readiness assessments | Maturity at each gate | ESTIMATED |
| Incident and post-deployment reports | Failures that requirements missed | REPORTED |
Three families of instruments side by side against the baseline, each with its own lag and adoption speed, under the coverage and compliance you set; effect sizes are teaching values to replace with evidence. Scenario: named assumptions about the future, not a forecast. The map on this page shows China; the model itself is not tied to a place.
Controls
Readouts
| Year | Baseline | Regulation | Economic incentive | Information and capacity |
|---|---|---|---|---|
| 0 | 100.0 | 99.5 | 98.8 | 99.1 |
| 1 | 102.0 | 101.2 | 100.1 | 99.8 |
| 2 | 104.0 | 102.5 | 101.1 | 99.9 |
| 3 | 106.1 | 103.5 | 101.6 | 100.0 |
| 4 | 108.2 | 103.7 | 101.8 | 100.7 |
| 5 | 110.4 | 103.2 | 101.7 | 102.1 |
| 6 | 112.6 | 102.0 | 101.6 | 103.9 |
| 7 | 114.9 | 100.4 | 101.6 | 105.9 |
| 8 | 117.2 | 99.2 | 102.1 | 108.0 |
| 9 | 119.5 | 98.6 | 102.9 | 110.1 |
| 10 | 121.9 | 98.9 | 104.2 | 112.3 |
| 11 | 124.3 | 99.7 | 105.7 | 114.5 |
| 12 | 126.8 | 101.1 | 107.4 | 116.8 |
| 13 | 129.4 | 102.7 | 109.4 | 119.2 |
| 14 | 131.9 | 104.5 | 111.4 | 121.6 |
| 15 | 134.6 | 106.5 | 113.5 | 124.0 |
| 16 | 137.3 | 108.5 | 115.7 | 126.5 |
| 17 | 140.0 | 110.7 | 118.0 | 129.0 |
| 18 | 142.8 | 112.9 | 120.4 | 131.6 |
| 19 | 145.7 | 115.1 | 122.8 | 134.2 |
| 20 | 148.6 | 117.4 | 125.2 | 136.9 |
The model runs on the teaching values set by the controls. To calibrate it for a place, read it against these admitted layers and series, which this page's map can draw:
Across the six pillars, led by Nexus Consortium
Each requirement is traced to verification evidence from analysis, inspection, demonstration or test. Independent reviews check completeness at life cycle gates.
| Check | How it is done |
|---|---|
| Bidirectional traceability | Every requirement traces to evidence, and every piece of evidence traces back to a requirement |
| Independent gate review | Readiness assessments are reviewed by people outside the programme team before a gate is passed |
| Emergence check | Post-deployment incidents are fed back to test whether requirements missed socio-technical interactions |
Emergent behaviour in open or socio-technical systems may not be captured by requirements. Rigid processes can slow adaptation to change.
The steps an instrument takes from mandate to evaluation, each with the pillar that runs it, and the decisions that stay with the authority. Teaching model with stated illustrative values, not a prediction. The map on this page shows China; the model itself is not tied to a place.
Across the six pillars, led by Nexus Consortium
Assembled from the Nexus Standards area profile Frontier technology risk standards: the hazards it names, the systems and communities that carry the loss, the controls and institutions that dampen it and the data that observe it. Pick an initiating event and step through the cascade to see where mandates meet and which decisions fall to whom. The Map view places the run on an example geography with open data. Every weight is a stated assumption. An exercise for dialogue, not a forecast, an assessment or a position. To model a place of your own choosing, open the full System Builder.
Hazards
Systems and couplings
Controls
NS-0 Constitution and principlesNS-10 Policies and clauses (machine-readable obligations: definition, binding, evaluation and enforcement)NS-11 Verification and monitoring (evidence, attestations, zero-trust conformance observation)NS-12 Software, model and AI/ML artefacts (supply chain, model cards, dataset sheets)NRS-H104 Hazard family: Quantum technology and cryptographic transition (NHS-1 tech.quantum)NRS-T9 Quantum technology and cryptographic transition riskNRS-T0 Exponential technology risk and responsible innovationNRS-H109 Hazard family: Energy-transition technology failures (NHS-1 tech.energy-transition)NRS-M19 Method fabric: Cyber, AI and frontier technologyNRS-U12 Universe platform profile: Foresight NexusObservation
Example geography
Systems Science and Modelling stewards systems engineering for the Consortium and reviews how it is applied across platforms.
The instruments, mandates, actors and accountability arrangements a policymaker, diplomat or development agency works with, citing the agreements that set them. Structures follow the frameworks named. Any state or progress drawn is illustrative, not a record.
The kinds of instrument available on systems engineering for innovation governance, by level of government and cooperation.
| Instrument type | Local | National | Regional | Global |
|---|---|---|---|---|
| Regulatory | Zoning, building codes | Laws, standards, licensing | Harmonised rules | Conventions and treaties |
| Economic | Local levies, grants | Budget lines, taxes, insurance schemes | Risk pools, regional funds | Financing mechanisms |
| Information | Local warnings | Disclosure, early warning, statistics | Data sharing arrangements | Global monitoring and reporting |
| Institutional | Local committees | Lead agencies, coordination councils | Regional bodies and secretariats | Multilateral mandates |
| Cooperative | Community agreements | Partnership compacts | Memoranda and joint programmes | Agreements and joint commitments |
Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information. We run no advertising. You can review your choices at any time through Privacy choices at the foot of every page.