The Nexus cycle in Nexus Registry: question, evidence, build, organize, test, publish, decide and renew, with the page and owner of each step.
The Nexus cycle in Nexus Registry is the eight-step path by which a question in the governance and institutions field becomes evidence, a Foundry build, an organized community, a controlled test, a publication and a decision taken by the competent authority. Here the evidence step rests on data engineering, interoperability and stewardship as well as digital identity and public digital systems, and findings feed Methods and Technical.
Fig.A programme from scoping to the owner's decision. Design, not a record.
For how work moves in this field, in GCRI's spatial-intelligence reading, the map opens on population density, true-colour imagery and night lights, framed on World; every other NASA layer, live feed and forecast waits in the layer list.
The interactive map needs JavaScript; the layer list and sources are below.
Layers 3
People and exposure, 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.
For how work moves in this field, in GCRI's spatial-intelligence reading, the map opens on population density, true-colour imagery and night lights, framed on World; every other NASA layer, live feed and forecast waits in the layer list.Satellite and model products as NASA publishes them, each with its own date; indicators, not assessments of any place; claim ceiling INTEGRATED.
Layers and dates
In Nexus Registry the cycle is about records: every question, evidence set, build, test, publication and decision in the other platforms leaves an identified, versioned record here, which is what makes the renew step possible.
| Step | Owner |
|---|---|
| Question | National, regional or institutional priority |
| Evidence | STEM foundation of the platform |
| Build | Nexus Foundry |
| Organize | Nexus Ecosystem: community, chapters, councils, national cells |
| Test | Nexus Universe (independent site) |
| Publish | Nexus Reports |
| Decide | Competent authorities and institutions, through Nexus Rails |
| Renew | Corrections and the next annual agenda |
Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.
| Term | Definition |
|---|---|
| Nexus cycle | The eight-step loop by which work moves in every Nexus field: question, evidence, build, organize, test, publish, decide and renew, each step with a named owner. |
| Competent authority | The body that a law or regulation designates to exercise a given power or duty, such as a supervisor, a civil protection agency or a ministry; only it can take the decisions the law assigns to it. |
| Peer review | Evaluation of a work by independent experts in the field before publication. |
| Versioning | Keeping each changed state of a record as a distinct, dated version linked to the ones before and after it. |
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
The current service level is R0: information and enquiries. 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.