Skip to content

GCRI · Foundry

Pergalên teknîkî

This is the canonical directory of the 20 technical pergalan of Foundry, published by The Global Centre for Risk and Innovation (GCRI). Each system has one product page here, with what it does, who uses it, where its authorisation boundary sits and the platforms it serves. Other pages across the network link to these pages rather than describing systems in their own words, so there is one reference for each. Information and enquiries are open today.

01Qada xebatê

The workspace for technical systems.

Pipeline

Technical systems · Workspace WS-76 · Example interface, not a record

One stage waitingGCRI · Foundry

Stages

  1. Ingest5 çavkanî
  2. Erê bikeschema · licence
  3. Transformversioned
  4. ModelHigh-performance
  5. Ceribandinheld-out
  6. Releasewith limits

Berhem

Job scheduler logv2.2VekirîÇAVDÊRÎKIRÎ
Tomara modelanv4.3VekirîStatîstîkên weşandî
Tile cache manifestv3.7VekirîVERSIONED
Usage meterv4.4VekirîÇAVDÊRÎKIRÎ

Compute quota

share used vs alert level

CPU hours86 used of 80 used limitStorage75 used of 90 used limitGPU hours40 used of 70 used limit
Pipeline.Navrûyeke ronîker; ne daneya zindî ye.

Foundry · Pipeline. Pipeline: example names and illustrative values, not a record.

02Rêber

The twenty systems.

03How to read it

One spine, many systems.

Çavdêrxaneya pergalan share one trust spine, NXS-NSF, so identity, policy and receipts work the same way everywhere. Each composes or consumes the others’ records rather than re-owning them: NXS-NST, NXS-DSS û NXS-EWS use The Global Risks Index (NXS-GRX) products instead of inventing their own risk figures. The boundaries of each system are summarised on capabilities.

06Pirs

Pirs û bersiv.

Why twenty systems rather than one product?
Each system has a distinct responsibility and limit, which keeps authority clear: the system that analyses is not the one that decides, warns or releases funds.
Can a system be used without the others?
They are designed to work together under NXS-NSF. Access to any system is scoped to an authorised project.
Where do I ask about a specific system?
Binivîse bo forma têkiliyê, naming the system. The acknowledgement gives a reference and names the next step.
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.