Skip to content

GCRI · Foundry

Bîst pergalên teknîkî

A technical environment of many systems fails at its seams: two systems each believe they own the same record, an interface changes without notice, or a downstream tool computes its own version of a figure that already exists upstream. The canonical inventory gives each Foundry system one contribution, one boundary and one owner per record type. This page sets out how interface and ownership failures develop and spread, how they are measured, and what system owners and reviewers need to keep the inventory true.

02Pirs

Twenty technical systems: how the risk develops.

Canonical Foundry system inventory. 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

Duplicate ownership

When two systems both write the same kind of record, they diverge silently. Each looks correct alone; the conflict appears only when a decision draws on both and finds two answers to one question.

Mekanîzma

Interface drift

A field changes meaning, a unit changes, an optional value becomes required. Consumers built against the old contract keep running and produce plausible but wrong output. Versioned contracts with compatibility checks on every build are the standard defence.

Mekanîzma

Girêdayîbûnên hevpar

Many systems depend on one identity service, one message bus, one library or one cloud region. A fault or vulnerability there reaches every dependant at once, which is why dependency maps and software bills of materials matter.

Mekanîzma

Authority creep

A system built to support a decision begins to make it: a dashboard threshold becomes an automatic action, a draft becomes a release. Boundaries written into each system definition and enforced at policy gates keep support from becoming authority.

03Çavdêrî bike

Konsola cihê kar û karan.

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.

Konsola cihê kar û karan

Twenty technical systems · Project space 12 · Cluster east

  • Kar dixebitin
    20Çalak
  • Li bendê ma, p50
    8minNormal
  • Xebatên îro
    5327
  • Kota hatiye bikaranîn, % vê mehê
    85Çavdêrî
IllustrativeGCRI · Foundry

Kar

J-77261Ansambla modelên lehiyêXwediyê projeyê00:10:12Dixebite
J-22526Xêzkirina kaşêlan, zoom 0 heta 12Cihê xebatê yê GIS00:01:40Dixebite
J-65648Derxistina delîlanBerpirsê modelê00:00:55Qediya
J-53084Berhevoka bangên amûrê yên ajanêQada ceribandinê ya ajanan00:01:51Astengkirina siyasetê

Bûyerên siyasetê

  1. 10:28DerîBangeya ajanê pejirandina mirovî dixwaze
  2. 10:33AgahîTomara xebatê hatiye mohrkirin
  3. 11:58Hişyar bikeKota li 80 ji sedî ji bo projeyê
Workspace and job console: the screen’s structure, terms and states for Twenty technical systems.Example names and illustrative values; a design, not a record or a live system.
05Rêbaz û delîl

How twenty technical systems 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 twenty technical systems, 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
Record types with more than one declared ownercounther weşanSystem registryDECLARED
Breaking interface changes detectedcount per releaseper buildContract compatibility checksÇAVDÊRÎKIRÎ
Components with a current software bill of materialsproportion of deployed componentsper buildSBOM generation recordsÇAVDÊRÎKIRÎ
Known exploited vulnerabilities in dependenciescount opendailyScans against public advisoriesÇAVDÊRÎKIRÎ
Time to remediate critical dependency vulnerabilitiesrojper advisoryChange and release recordsÇAVDÊRÎKIRÎ
Release artefacts with build provenance attestationsproportion of artefactsher weşanSigned build attestationsÇAVDÊRÎKIRÎ
Systems with a documented boundary and ownerproportion of inventorysê-mehaneSystem registryDECLARED
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
OpenAPI SpecificationMachine-readable HTTP interface contracts that can be compared for breaking changeApache 2.0
Protocol Buffers language specificationCanonical service and message contracts with defined compatibility rulesOpen source, BSD-style
CycloneDX and SPDX specificationsFormats for software bills of materials, licences and component provenanceOpen specifications
OSV vulnerability databaseOpen-source vulnerability advisories keyed to package versionsCC BY 4.0
National Vulnerability Database (NIST)Vulnerability records with severity scoringGiştî
CISA Known Exploited Vulnerabilities catalogueVulnerabilities with evidence of active exploitationGiştî
OpenSSF Scorecard resultsAutomated checks of security practice in open-source dependenciesFree and open
08Biryar

Who decides, and what the evidence serves.

Foundry 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
System ownersWhether a change to their system’s contract or record ownership may proceedCompatibility check results; the consumers of the affected contract
Security officersWhich dependency vulnerabilities must be fixed before release, and which are accepted with a recorded rationaleBills of materials matched against advisories; exploitation status
Architecture reviewersWhether a new capability belongs in an existing system or needs a new boundaryInventory, record ownership map and the proposed contract
Contracting institutionsWhich systems their agreement covers and what each may do with their dataSystem boundaries and the record types each one reads and writes

Outputs this topic produces

  • Inventory of systems with contribution, boundary and record ownership
  • Interface contracts with version and compatibility history
  • Dependency maps and software bills of materials per release
  • Boundary statements of what each system must never do
09Core questions

What a system inventory has to answer.

  • Which system is the authoritative owner of each kind of record?
  • Where does each system’s authority stop, and who decides beyond that point?
  • How do systems exchange records without copying and diverging?
  • Which shared controls apply to every system, so that trust does not depend on each one’s configuration?
10The inventory

Twenty systems, one line each.

Descriptions are of the design. A system page is not a statement that the system is operating for any tenant.

11Mechanisms

One trust spine, composed records.

The systems share one trust spine, the NXS-NSF Sovereignty Framework, so identity, policy and receipts work the same way everywhere. Records are composed rather than duplicated: NXS-NST, NXS-DSS and NXS-EWS use The Global Risks Index (NXS-GRX) products instead of inventing their own risk figures, and NXS-POR publishes only what has passed a public-safe release decision. This is ordinary systems-engineering discipline, a single source of truth per record type and explicit interfaces between subsystems, applied to risk work.

Boundaries are part of each definition. DSS supports analysis, but analysis is not the decision. EWS supports forecast verification and warning packages, but issuing warnings stays with authorised parties. AAP evaluates triggers and readiness, but never releases funds or dispatches resources automatically. Rails records instructions and receipts between institutions, and a receipt is not settlement or external acceptance. Labs runs reproducible experiments, and experiment results are not certification.

12Rêbaz

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

  1. Systems engineeringCanonical system inventory · Contract-first interfaces · Requirements traced to evidenceApplied here
  2. Software and safety-critical systems engineeringFail-closed policy gates · Build provenance and bills of materials · Assurance casesApplied here
  3. High-performance, cloud and edge computingEnsemble scheduling across tiers · Federated execution next to the dataApplied here
  4. Data engineering, interoperability and stewardshipValidation at the ingest boundary · Frozen data cuts for reproducible productsApplied 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.

Why does every record type have one owner?
Because two writers of the same record will diverge. One owner, with other systems composing its records through explicit interfaces, is ordinary systems-engineering discipline and the main defence against conflicting figures.
What is a software bill of materials?
A machine-readable list of the components, versions and licences inside a piece of software. It lets a security team answer quickly, after a new advisory, which releases contain the affected component.
Why are the systems written in several languages?
Each language plane has a defined role: product interfaces and orchestration in TypeScript, fleet and infrastructure control in Go, trust and evidence in Rust, AI and earth observation adapters in Python, advanced mathematics in Julia, authoritative state in PostgreSQL and canonical contracts in Protobuf.
Does a system page mean the system is running?
No. Pages describe the design. Whether a system is implemented, verified, deployed and observed for a tenant are separate questions, each answered by its own evidence.
Why exactly twenty systems?
The number is the registry count of the canonical inventory. It reflects how responsibilities were allocated, not a target; changes to the inventory are made in the registry and reflected on every page.
Can I use one system on its own?
The systems are designed to work together under one trust spine, and access to any of them is scoped to an authorised project.
Is the Labs system the same as Labs?
They share a name. The Labs system is the Foundry capability for governed experiments; Labs is the GCRI platform for experiments and protocols that uses it.
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.

GCRIFoundryFoundry Build and Readiness
Foundry

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.

The Global Centre for Risk and Innovation (GCRI Canada) is a Canadian not-for-profit organisation, not a registered charity, with its registered office in Ontario.