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.
Labs and foundry series on the record.
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.
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.
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.
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.
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.
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
Editions in production
| Senteza salane | Gerdûnî | Data check | 81 | W10 |
| Country profile 7 | Welat | Peer review | 97 | W16 |
| Water outlook | Sectoral | Nivîsandin | 32 | W38 |
| Methods note 4 | Rêbaz | Hatiye weşandin | 100 | qediya |
Data check, annual synthesis
Edition pipeline
- Planlijne
- Draftauthors
- Data checkevery value
- Peer reviewtwo rounds
- Editorialdecision
- WeşanDOI
- Rastkirinbi guhertoyan
Labs and Foundry editions report what was tested and built for each domain.
Editions carry verification evidence under NS-11 of the proposed Nexus Standards. A test result is not an approval.
- Negative results.
- Replications.
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.
Ri = f(Hi, Ei, Vi, Ci)metirsî, rûbirûbûn, lawazî û kapasîteya serederiyêEAL = ∑k pk · Lkover events k with annual probability pkxt+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 ne | Entegrala windahiyê ji hesabkirinê re maqûl dihêle | Bi lihevhatineke copula li ser tomarên hevbeş re bidin ber hev |
| Girêdan li nêzî xala xebatê xêzik in | Dihêle şok di A de belav bibin | Ji derveyî rêza xêzik tevlihev bike û bide ber hev |
| Xêzên lawaziyê di navbera cihan de têne veguhastin | Xêzikên herêmî kêm tên dîtin | Li 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
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îşane | Yekîne | Rîtm | Source type | Nîşan |
|---|---|---|---|---|
| Test protocols registered before testing | percent of reports | per report | Registry records | ÇAVDÊRÎKIRÎ |
| Test reports with archived code, data and configuration | percent of reports | per report | Repository deposit records | ÇAVDÊRÎKIRÎ |
| Readiness level claimed and evidence attached | level claimed; yes or no for evidence | per report | Report and evidence annex | DECLARED |
| Negative and inconclusive results published | count per period | annual | Series catalogue | HATIYE RAPORKIRIN |
| Version of the tested system identified | percent of reports | per report | Report metadata | ÇAVDÊRÎKIRÎ |
| Independent technical review completed | yes or no, with reviewer role | per report | Review record | DECLARED |
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 gives | Licence class |
|---|---|---|
| Zenodo | Archived test data, configurations and software releases with DOIs | Metadata CC0, licence per record |
| Software Heritage | Preserved source code at the exact revision tested | Code under its own licence |
| OSF Registries | Pre-registered test protocols and analysis plans | Metadata CC0, licence per registration |
| protocols.io | Published step-by-step methods with versions and DOIs | Licence per protocol, mostly CC BY |
| NIST National Vulnerability Database | Known vulnerabilities for software components under test | Giştî |
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ê dide | Pirs | Evidence this page serves |
|---|---|---|
| Procurement and adoption boards | Whether a tested technology is ready for a pilot or operational use | Readiness evidence annexes, test conditions and known limitations |
| Innovation funders and programme managers | Whether to fund the next stage of development | Readiness level with its evidence, negative results and open risks |
| Technical review panels | Whether a test report is complete and its conclusions follow from the evidence | Registered protocols, archived data and version identifiers |
| Standards and conformity assessment bodies | Whether test methods are suitable for a future standard | Documented 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
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?
What the series covers.
Three series report evidence from building, testing and observing.
Experiments and testbeds
Results from completed protocols, including null and negative results.
Build and readiness
Evidence about Foundry systems against stated readiness criteria, never as certification.
Ç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.
How editions are built, and their limits.
- 01
Protokol
Each result cites a protocol registered before the test, so outcomes cannot be selected after the fact.
- 02
Environments
Test conditions are described; results from a testbed may not transfer to live operation.
- 03
Pîvanên amadebûnê
Readiness is assessed against criteria for a stated next step. It is not approval, bankability or certification.
- 04
Signal quality
Observatory signals state their source, coverage and false-alarm characteristics where known.
How it is studied, and what the methods cannot say.
- 01Data engineering, interoperability and stewardshipStructured publishing in JATS XML · Persistent identifiers across the recordApplied here
- 02Uncertainty quantification and model validationCalibrated language in assessments · Certainty of evidence ratingsApplied here
- 03Probability and statisticsMeta-analysis with heterogeneity stated · Small-study and publication biasApplied here
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ê.
Pirs û bersiv.
What is a technology readiness level?
Why publish failed tests?
Does a passed test mean a system is safe?
Does a readiness report mean a system is approved?
Are failed tests published?
Can vendors publish results in the series?
Are observatory signals warnings?
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.
- E-nameDergeh GW-GCRIJi vê rûpelê bişîninDelîl, rastkirin, doz, rêbaz, nirxandin, wergerandin an têketina profîlê. Bi nîşana vê rûpelê digihîje, ji ber vê yekê edîtorê xwediyê wê wê bistîne.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- rêzeya Pergalên StratejîkGCRIHemû rêyên beşdariyê bibîneCureyên beşdariyê, her yek çawa tê nirxandin, tu çi navlêkirinê distînî, lîsans û tiştê ku qet nayê qebûlkirin.
Tu carî daneyên şexsî, hûrgiliyên binesaza hesas an tiştekî ku mafê we yê parvekirinê tune ne neşînin. Beşdarî berî bikaranînê tê nirxandin; şandina wê nivîskarî an mafên edîtorî nade û sponsorî tu carî encamekê nakire.
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.
Belgeyên hiqûqî.
Nexşe, dane û jimarên vê malperê ji bo çarçoveyê û agahiyên giştî têne nîşandan. Ew ne şîret, ne pêşbînî û ne hişyarî ne; sînorên agahiyê di Daxuyaniyên Berpirsiyariyê û Daxuyaniyên Daneyê de hatine diyarkirin.