Analytical and data resources

Pêvajo

Analytical and data resources: Build, sign and accept

An admitted mission becomes a cycle project; the build is pinned, verified and signed, and the Global Risks Forum (GRF) records acceptance for exercise, not permission to deploy.

1. 01 Request and sources

   1. 01Admitted mission becomes a cycle projectTomar · Universe to FoundryAn admitted mission becomes a cycle project with a decision case.
   2. 02Qualify data sources and resourcesStep · the Global Centre for Risk and Innovation (GCRI)GCRI qualifies data sources and resource offers and builds the scenario models. An offer is not an allocation.

2. 02 Build and verify

   1. 03Source snapshotTomar · NXS-FAC (blueprints, builds and signing)The snapshot pins the commit, dependencies and generator versions.
   2. 04Build contractRecord · NXS-FAC (blueprints, builds and signing)The build contract declares the artefact kind, environment and reproducibility envelope.
   3. 05Integrate and buildModel · GCRIGCRI integrates software and data, signs builds, and tests security and interoperability.
   4. 06Verification suiteGate · NXS-FAC (blueprints, builds and signing)Required and advisory checks stay separate. Reproducibility needs pinned inputs, declared nondeterminism and independent rebuilds.

3. 03 Sign and admit

   1. 07Sign the exact artefactStep · NXS-FAC (blueprints, builds and signing)NXS-FAC builds, attests and requests a signature via a scoped signer identity. It holds no key material.
   2. 08Package admissionStep · NXS-NXQ (software, models and capability lifecycle)NXS-NXQ receives the signed package and keeps admission evidence that binds the task, data class, evaluation suite and expiration.

4. 04 Accept

   1. 09Core Build ReportTomar · GCRIThe Core Build Report is the go or no-go record. Universe assembles the Core and holds the decision for the exercise.
   2. 10G3 · Avakirin ji bo pratîkê hatiye pejirandinDerî · The Global Risks ForumGRF records whether the build is accepted for exercise. A signed build or release candidate is not permission to deploy to production.

Salê bernameyê · NXS-FAC · UniverseDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The record order follows the Builds and Releases room lists of NXS-FAC.