Skip to content

GCRI · Foundry

بیست سیستەمی تەکنیکی

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.

02پرسیارەکە

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.

میکانیزم

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.

میکانیزم

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.

میکانیزم

پشتبەستنی هاوبەش

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.

میکانیزم

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چاودێری

کۆنسۆڵی شوێنی کار و کارەکان.

ئەو شاشەیەی تیمێک بۆ بەدواداچوونی ئەم بابەتە بەکاری دەهێنێت: پێوەر، دۆخ و بڕیارەکانی. ناوەکان نموونەن و بەهاکان ڕوونکەرەوەن.

کۆنسۆڵی شوێنی کار و کارەکان

Twenty technical systems · Project space 12 · Cluster east

  • کارە کارا
    20چالاک
  • چاوەڕوانی ڕیز، p50
    8کەمترینئاسایی
  • ئەمڕۆ کاردەکات
    5327
  • کۆتا بەکارهاتوو، % ئەم مانگە
    85چاودێری
IllustrativeGCRI · Foundry

کارەکان

J-77261کۆمەڵەی مۆدێلی لافاوخاوەنی پڕۆژە00:10:12کارا
J-22526ڕەندەری کاشی، زووم 0 بۆ 12شوێنی کاری GIS00:01:40کارا
J-65648هەناردەکردنی بەڵگەپارێزەری مۆدێل00:00:55تەواو بوو
J-53084کۆمەڵەی بانگکردنی ئامرازی ئەیجێنتقوتووی تاقیکاریی ئەیجێنت00:01:51بلۆکی سیاسەت

ڕووداوی سیاسەت

  1. 10:28دەروازەبانگکردنی ئەیجێنت پێویستی بە پەسەندی مرۆڤ هەیە
  2. 10:33زانیاریتۆماری ڕاکردن لەسەر مۆر کراوە
  3. 11:58ئاگادارکردنەوەکۆتا گەیشتە 80 لە سەد بۆ پڕۆژەکە
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.
05ڕێگا و بەڵگە

How twenty technical systems is modelled, measured and tested.

مۆدێلەکە، گریمانەکانی، داتاکانی و نادڵنیاییەکەی، بەو شێوەیەی زانا یان ئەندازیارێک دەیپشکنێت. پێکهاتەکان ڕێگا بڵاوکراوەکان دەگرنەبەر. بەهاکانی کێشراو نموونەییە، نەک دۆزینەوە.

مۆدێل، هاوکێشەکان و گریمانەکان

The model structure used for twenty technical systems, the assumptions it makes and how each is tested.

مەترسیی توخمی iRi = f(Hi, Ei, Vi, Ci)مەترسیدەر، ڕووبەڕووبوون، لاوازی و توانای مامەڵەکردن
زیانی ساڵانەی چاوەڕوانکراوEAL = ∑k pk · Lkover events k with annual probability pk
سیستەمە هاوبەستەکانxt+1 = A xt + B ut + εtA carries the couplings, u the shock, ε the error
گریمانەبۆچی دروست دەکرێتچۆن تاقی دەکرێتەوە
مەترسیدەر و ڕووبەڕووبوون لە ناو پێشهاتێکدا سەربەخۆنئینتێگراڵی زیان بە ئاسانی دەهێڵێتەوەبەراورد بکە لەگەڵ گونجاندنی کۆپیولا لەسەر تۆمارە هاوبەشەکان
هاوبەستییەکان لە نزیک خاڵی کارکردن هێڵینڕێگە دەدات شۆکەکان بڵاو ببنەوە لە Aلە دەرەوەی مەودای هێڵیی شڵەژێنە و بەراورد بکە
چەمکەکانی لاوازی لە شوێنێکەوە بۆ شوێنێکی تر دەگوازرێنەوەچەمکی ناوخۆیی بە دەگمەن بەردەستەلەگەڵ زیانە چاودێریکراوەکان پشتڕاستی بکەرەوە کە هەن
تێکردنەکان
کۆمەڵە داتای وەشانکراو لەگەڵ ڕەسەنایەتی
دەرچووەکان
دابەشبوون، نەک یەک ژمارە
کۆد
بڵاوکراوەتەوە لەگەڵ کارتی مۆدێل و تاقیکردنەوەکان
بەرهەمهێنانەوە
هەمان داتا، کۆد، ژینگە و تۆو
فۆرمۆلەکردنی مەترسی و دۆخ-بۆشایی ستاندارد؛ ئەو گریمانانەی لیست کراون ئاسایین بۆ ڕێگاکە، بۆ پێداچوونەوە ڕاگەیەندراون، نەک ئەنجام.
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
06نیشاندەرەکان

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.

نیشاندەریەکەڕیتمSource typeناونیشان
Record types with more than one declared ownercountبۆ هەر وەشانێکSystem registryDECLARED
Breaking interface changes detectedcount per releaseper buildContract compatibility checksچاودێریکراو
Components with a current software bill of materialsproportion of deployed componentsper buildSBOM generation recordsچاودێریکراو
Known exploited vulnerabilities in dependenciescount opendailyScans against public advisoriesچاودێریکراو
Time to remediate critical dependency vulnerabilitiesڕۆژper advisoryChange and release recordsچاودێریکراو
Release artefacts with build provenance attestationsproportion of artefactsبۆ هەر وەشانێکSigned build attestationsچاودێریکراو
Systems with a documented boundary and ownerproportion of inventoryوەرزانەSystem registryDECLARED
07سەرچاوەکان

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.

سەرچاوە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 scoringدۆمەینی گشتی
CISA Known Exploited Vulnerabilities catalogueVulnerabilities with evidence of active exploitationدۆمەینی گشتی
OpenSSF Scorecard resultsAutomated checks of security practice in open-source dependenciesFree and open
08بڕیارەکان

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.

کێ بڕیار دەداتپرسیارەکەEvidence 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.

12میتۆدەکان

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

13Where this page’s references

Where this page’s references lead.

ئەو لەش و بەڵگەنامانەی ئەم لاپەڕەیەیان لەگەڵ دەخوێنرێتەوە. دۆخ و وەشانەکان دەگۆڕێن؛ هەر بەستەرێک دەچێتە لای لەشی دەرکەر.

14پرسیارەکان

پرسیار و وەڵام.

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.
ڕاپۆرتەکانبەشداربە

لەم لاپەڕەیەوە بەڵگە پێشکەش بکە.

Reports بڵاوکراوەی وەرزیی کۆنسۆرتیۆم ـە. ئەوەی تۆ لەسەر ئەم بابەتە دەیزانیت دەتوانێت لە وەشانی داهاتوودا ببێتە بەڵگە، کەیس یان ڕاستکردنەوە، بە ناوی خۆتەوە و لەژێر CC BY 4.0 بڵاو دەکرێتەوە کاتێک کاری خۆتە.

GCRIFoundryFoundry Build and Readiness
Foundry

ڕێگایەک، کۆمەڵە داتایەک یان پرسیارێک بهێنە.

زانیاری و پرسیار ئەمڕۆ کراوەن. پرسیارێک ژمارەی ئاماژەی پێدەدرێت و هەنگاوی دواتر دیاری دەکات؛ داواکاری، پارەدان، تەرخانکردنی کۆمپیوتەر و تۆمارکردن تەنیا کاتێک دەکرێنەوە کە تیم، مەرج و توانای پێداچوونەوەیان هەبێت.

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.