Skip to content

GCRI · Reports

Labs and foundry series

Labs and foundry reports record technical tests: prototypes, software, sensors, data pipelines and procedures exercised under stated conditions. Test evidence is easy to overstate, because a passed test under controlled conditions is read as readiness for use. This page sets out how test reports are structured, reviewed and archived, how readiness levels are evidenced rather than declared, and what such evidence can support for those deciding whether to adopt or fund a technology.

02Pirs

Labs and foundry series: how the risk develops.

Technical test and readiness evidence. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.

Mekanîzma

Test conditions narrow the claim

A test establishes behaviour under the conditions tested, with the inputs, environment and version used. Reports that omit those conditions invite readers to generalise beyond them.

Mekanîzma

Readiness declared not shown

Technology readiness levels are often self-assigned. Without the evidence each level requires, a readiness claim moves from test report to procurement decision unchecked.

Mekanîzma

Negative results go missing

Failed and inconclusive tests are seldom written up, so the published record overstates success rates and others repeat tests that have already failed.

Mekanîzma

Versions change underneath

Software and hardware change after testing. A result cited without the version tested is attached to a system that may no longer exist in that form.

03Çavdêrî bike

Series production desk.

Ekrana ku tîmek dê ji bo şopandina vê mijarê bikar bîne: pîvan, rewş û biryarên wê. Nav mînak in û nirx nîşander in.

Series production desk

Labs and foundry series · Annual synthesis · Edition 7

Data check behind planGCRI · Reports

Editions in production

Senteza salaneGerdûnîData check81W10
Country profile 7WelatPeer review97W16
Water outlookSectoralNivîsandin32W38
Methods note 4RêbazHatiye weşandin100qediya

Data check, annual synthesis

Values traced, %79 of 100 requiredLabels attached, %95 of 100 requiredUncertainty stated, %73 of 100 required

Edition pipeline

  1. Planlijne
  2. Draftauthors
  3. Data checkevery value
  4. Peer reviewtwo rounds
  5. Editorialdecision
  6. WeşanDOI
  7. Rastkirinbi guhertoyan
Series production desk: the screen’s structure, terms and states for Labs and foundry series.Example names and illustrative values; a design, not a record or a live system.
04In the five domains

Labs and Foundry editions report what was tested and built for each domain.

05Rêbaz û delîl

How labs and foundry series is modelled, measured and tested.

Model, texmînên wî, daneyên wî û nediyariya wî, bi şeweyê ku zanyar an endezyar kontrol bike. Avahî rêbazên weşandî dişopînin. Nirxên hatine xêzkirin nimûneyî ne, ne encam in.

Model, hevkêşe û texmîn

The model structure used for labs and foundry series, the assumptions it makes and how each is tested.

Xetera hêmana iRi = f(Hi, Ei, Vi, Ci)metirsî, rûbirûbûn, lawazî û kapasîteya serederiyê
Windahiya salane ya hêvîkirîEAL = ∑k pk · Lkover events k with annual probability pk
Pergalên girêdayîxt+1 = A xt + B ut + εtA carries the couplings, u the shock, ε the error
TexmînÇima tê çêkirinÇawa tê ceribandin
Metirsî û rûbirûbûn di nav bûyerekê de serbixwe neEntegrala windahiyê ji hesabkirinê re maqûl dihêleBi lihevhatineke copula li ser tomarên hevbeş re bidin ber hev
Girêdan li nêzî xala xebatê xêzik inDihêle şok di A de belav bibinJi derveyî rêza xêzik tevlihev bike û bide ber hev
Xêzên lawaziyê di navbera cihan de têne veguhastinXêzikên herêmî kêm tên dîtinLi hember windahiyên çavdêrîkirî erê bike li cihê ku hene
Têketin
danehevên bi guhertoyan û çavkaniyê
Derketin
belavkirin, tu carî jimarên tenê
Kod
bi qerta modelê û ceribandinan re hat weşandin
Zêdebûn
heman dane, kod, jîngeh û tov
Formulasyonên standard ên xetereyê û qada rewşê; texmînên navborî ji bo rêbazê tîpîk in, ji bo nirxandinê hatine diyarkirin, ne encam in.
FAIR guiding principles · GO FAIR and FORCE11W3C PROV · World Wide Web ConsortiumGuidance on consistent treatment of uncertainties · IPCCCEOS Analysis Ready Data · Committee on Earth Observation Satellites
06Nîşander

What is measured, and how well.

Each indicator carries its unit, its cadence, the kind of source behind it and the evidence label a value would carry. No values are shown: a programme supplies them under its own authority.

NîşaneYekîneRîtmSource typeNîşan
Test protocols registered before testingpercent of reportsper reportRegistry recordsÇAVDÊRÎKIRÎ
Test reports with archived code, data and configurationpercent of reportsper reportRepository deposit recordsÇAVDÊRÎKIRÎ
Readiness level claimed and evidence attachedlevel claimed; yes or no for evidenceper reportReport and evidence annexDECLARED
Negative and inconclusive results publishedcount per periodannualSeries catalogueHATIYE RAPORKIRIN
Version of the tested system identifiedpercent of reportsper reportReport metadataÇAVDÊRÎKIRÎ
Independent technical review completedyes or no, with reviewer roleper reportReview recordDECLARED
07Çavkanî

Where the evidence comes from.

Named public datasets and institutional records, each with its licence class. Sources by agreement are used only under their terms and never republished.

ÇavkanîWhat it givesLicence class
ZenodoArchived test data, configurations and software releases with DOIsMetadata CC0, licence per record
Software HeritagePreserved source code at the exact revision testedCode under its own licence
OSF RegistriesPre-registered test protocols and analysis plansMetadata CC0, licence per registration
protocols.ioPublished step-by-step methods with versions and DOIsLicence per protocol, mostly CC BY
NIST National Vulnerability DatabaseKnown vulnerabilities for software components under testGiştî
08Biryar

Who decides, and what the evidence serves.

Reports prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.

Kî biryarê didePirsEvidence this page serves
Procurement and adoption boardsWhether a tested technology is ready for a pilot or operational useReadiness evidence annexes, test conditions and known limitations
Innovation funders and programme managersWhether to fund the next stage of developmentReadiness level with its evidence, negative results and open risks
Technical review panelsWhether a test report is complete and its conclusions follow from the evidenceRegistered protocols, archived data and version identifiers
Standards and conformity assessment bodiesWhether test methods are suitable for a future standardDocumented test procedures and their reproducibility

Outputs this topic produces

  • Test reports stating conditions, versions and acceptance criteria
  • Readiness evidence annexes mapping each level to its evidence
  • Archived configurations and data for each test
  • A register of negative and inconclusive results
09Core questions

What the series asks.

Technical claims about tools and systems need evidence that others can inspect. A system that is said to work under stress should show the test that proved it, the conditions of the test and what failed. Publishing that evidence, including negative results, guards against overstated readiness and helps institutions judge what a tool can and cannot do.

  • What exactly was tested, under which protocol, with which data and in which environment?
  • What passed, what failed and what was not tested?
  • Does the evidence support the stated next step, and only that step?
  • Which observations or signals warrant further analysis, and how reliable are they?
10Çarçove

What the series covers.

Three series report evidence from building, testing and observing.

Labs

Experiments and testbeds

Results from completed protocols, including null and negative results.

Foundry

Build and readiness

Evidence about Foundry systems against stated readiness criteria, never as certification.

Signals

Çavdêrî

Signals from monitoring, labelled by source and confidence, prompting analysis rather than action.

The series follows the logic of test and evaluation practice in engineering: a claim is only as good as the protocol that tested it, and readiness is always readiness for something specific. A tool that has passed a laboratory test is not ready for field use, and a system that worked in one exercise has not shown that it will work in every setting. Editions state these limits next to each result.

11How editions are built

How editions are built, and their limits.

  1. 01

    Protokol

    Each result cites a protocol registered before the test, so outcomes cannot be selected after the fact.

  2. 02

    Environments

    Test conditions are described; results from a testbed may not transfer to live operation.

  3. 03

    Pîvanên amadebûnê

    Readiness is assessed against criteria for a stated next step. It is not approval, bankability or certification.

  4. 04

    Signal quality

    Observatory signals state their source, coverage and false-alarm characteristics where known.

12Rêbaz

How it is studied, and what the methods cannot say.

  1. Data engineering, interoperability and stewardshipStructured publishing in JATS XML · Persistent identifiers across the recordApplied here
  2. Uncertainty quantification and model validationCalibrated language in assessments · Certainty of evidence ratingsApplied here
  3. Probability and statisticsMeta-analysis with heterogeneity stated · Small-study and publication biasApplied here
13Where this page’s references

Where this page’s references lead.

Sazî û belgeyên ku ev rûpel li hember wan tê xwendin. Rewş û çap diguherin; her girêdan diçe ba saziya derxistinê.

14Pirs

Pirs û bersiv.

What is a technology readiness level?
A scale describing how far a technology has progressed from basic principles to demonstrated operation. Each level requires specific evidence; a level stated without that evidence is a declaration, not a demonstration.
Why publish failed tests?
Because a record of successes alone misleads. Negative and inconclusive results show where a technology does not work and stop others repeating the same test.
Does a passed test mean a system is safe?
No. It means the system met the stated criteria under the stated conditions. Safety depends on use, context and conditions the test may not have covered.
Does a readiness report mean a system is approved?
No. Readiness is fitness for a stated next step within a stated scope. It is not approval, certification or a statement that a service operates.
Are failed tests published?
Yes. Negative and null results are part of the evidence, and omitting them would overstate readiness.
Can vendors publish results in the series?
Results appear only from protocols run under the programme’s review. Vendor claims are labelled Institution-reported if cited at all.
Are observatory signals warnings?
No. They prompt analysis. Warnings remain with competent authorities.
rêzeya Pergalên StratejîkTevkarî bike

Ji vê rûpelê delîl bidin.

Reports weşana sê mehane ya Konsorsiyûmê ye. Tiştê ku tu li ser vê mijarê dizanî dikare di çapa pêş de bibe delîl, dosya an rastkirin, bi navê te û di bin CC BY 4.0 de weşandî li cihê ku karê te bi xwe be.

GCRIrêzeya Pergalên StratejîkXetera pergalên gerdûnî û berxwedanXetera pergalan û berxwedana welatanWelat, sê mehane
rêzeya Pergalên Stratejîk

Rêbazek, danehevek an pirsek bîne.

Agahî û pirs îro vekirî ne. Pirsek referansekê distîne û gava piştî wê dide nasîn; serlêdan, drav, veqetandina hesabkirinê û tomarkirin tenê dema ku tîm, mercên wê û kapasîteya vekolînê hebin vedibin.