GCRI · Foundry
STEM foundation of Foundry
The science, technology, engineering and mathematics Foundry rests on. Each method has a canonical page in the STEM Commons, hosted by the Global Centre for Risk and Innovation (GCRI), and a page here on how it is applied in this field.
Six pages under STEM foundation of Foundry.
The methods behind the field.
- 01High-performance, cloud and edge computingEnsemble scheduling across tiers · Federated execution next to the dataSteward · Data and ComputeApplied here
- 02Data engineering, interoperability and stewardshipValidation at the ingest boundary · Frozen data cuts for reproducible productsSteward · Data and ComputeApplied here
- 03Geospatial information systemsImagery catalogues through STAC · Exposure overlays with stated aggregationSteward · Space and Earth ObservationApplied here
- 04Artificial intelligence and machine learningEarth observation models with spatial validation · Model cards and promotion recordsSteward · Artificial Intelligence and Autonomous SystemsApplied here
- 05Systems engineeringCanonical system inventory · Contract-first interfaces · Requirements traced to evidenceSteward · Systems Science and ModellingApplied here
- 06Software and safety-critical systems engineeringFail-closed policy gates · Build provenance and bills of materials · Assurance casesSteward · Cybersecurity and Digital ResilienceApplied here
Why Foundry needs this combination of methods.
Foundry work rests on computing and data engineering for the platform, geospatial methods for maps, AI and machine learning for models and agents, systems engineering for integration, and safety-critical software practice for assurance.
Grounding makes claims checkable.
When a finding names the methods it depends on, a reader can see its assumptions and limits, and an expert in that method can challenge it.
Where this page’s references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
Questions and answers.
What is a steward platform?
Contribute evidence from this page.
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.
- EmailGateway GW-GCRISend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- 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.
- ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
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.
Bring a method, a dataset or a question.
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.
Legal documents.
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.