GCRI · PAGE · labsGCRI dossier · service level R0
GCRINexus Ecosystem
Ecosystem · Labs

Labs gateway

Nexus Labs is where candidate technologies and methods are tested against the problem they claim to solve, under representative operating conditions. The Global Centre for Risk and Innovation (GCRI) stewards Labs as part of the Nexus Ecosystem. This gateway explains the test protocol, separates published results from concepts still in research and states what a test does not confer. A technology's novelty or a vendor's benchmark does not establish its fitness for a national mission; a Labs test is designed to find out. Return to Nexus Ecosystem.

The Global Centre for Risk and InnovationRegister
  1. 01InstitutionThe Global Centre for Risk and Innovation (GCRI)
  2. 02Service levelR0: information and enquiries
  3. 03In briefThe short answer
  4. 04ProtocolEvery test follows the same protocol
  5. 05Results and conceptsPublished results are kept apart from ideas
  6. 06BoundariesWhat a test does not confer
  7. 07Key termsTerms used on this page

GCRI · Institution · service level R0

01In brief

The short answer.

Nexus Labs is where candidate technologies and methods are tested against the problem they claim to solve, under representative operating conditions, following one test protocol. GCRI stewards it as part of the Nexus Ecosystem; a test answers one question about one candidate under stated conditions, confers no certification, and no evaluation is released yet.

02Geography

Landscapes and remoteness in the Caribbean.

Mountain ranges, deserts, wetlands, glaciers and reefs, and how remote each division is from large cities, shown for the Caribbean as an example geography for this subject.

Mountain ranges, deserts, wetlands, glaciers and reefs, and how remote each division is from large cities.Indicator derived from Natural Earth at map scale; a screening view, not an assessment.
GCRI · institution · fieldDESIGN FIGURE
03Protocol

Every test follows the same protocol.

  1. 01

    Use case and comparator

    The intended problem, the current practice it is compared with and who would use it.

  2. 02

    Data and metrics

    The data, the measures of success and the known limitations, fixed before the test.

  3. 03

    Reproducible build

    A versioned candidate built so that others can repeat the test.

  4. 04

    Test envelope

    Interoperability, failure behaviour, rights, security, resource cost and human use.

  5. 05

    Findings

    Measured evaluation, failure cases, interoperability findings and a transition recommendation.

04Results and concepts

Published results are kept apart from ideas.

Published

Reviewed results

A result is shown as published only after review, with its protocol, data limits and failure cases.

Concept

Future concepts

Capabilities still in research are labelled as research and never presented as tested.

Negative

Failures count

Failed tests produce documented failure cases, and negative findings can be published.

05Boundaries

What a test does not confer.

A Labs test answers one question about one candidate under stated conditions. It does not travel beyond those conditions, and the boundaries below stay attached to every result.

  • Testbed participation is not a regulatory sandbox, an accreditation or a procurement status.
  • Sponsorship never influences a result, and evaluation never depends on a high contribution.
  • Experiment results are not certification.
  • Selection for a test call is documented, with its criteria.
06Key terms

Terms used on this page.

Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.

TermDefinition
TestbedA controlled setting, from a lab rig to a field site or sandbox, for trying a technology before it meets real conditions of use.
Test protocolA document fixing a test's conditions, procedure and pass criteria before it is run.
Operating-environment fidelityHow closely test conditions match the conditions in which a technology will be used.
Null resultA finding of no detectable effect, which still informs future campaigns when published.
07Status

No released evaluations yet.

No Labs evaluation is listed as released. Released work will appear on Nexus Labs and in the Labs Evidence series of Nexus Reports. The current service level is R0: information and enquiries. Teams interested in a test call can see Innovation programmes; the governance of technology is examined by The Global Risks Forum (GRF) through its Innovation Nexus.

08Questions

Questions and answers.

Can a company pay to have its product tested?
Support never buys a result. Testing follows a published protocol, and selection for a call is documented with its criteria.
Will a successful test help us win contracts?
A test is not a procurement status or a certification. It produces evidence that a buyer can examine under its own rules.
Are results published if a technology fails?
Yes, where rights allow. Failure cases and negative findings are part of the record.
Who can propose a test?
Research teams, universities, technology providers, startups and implementation teams, either with their own proposal or in response to an open testbed call. Each proposal receives a documented decision, and an accepted one receives an evaluation plan before any work starts.
The Global Centre for Risk and Innovation

Start with an enquiry.

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.

Have questions?