Skip to content

GCRI · Foundry

وێستگەکانی کاری پڕۆژە

A project workstation holds a team’s question, data, models, agents and decisions together for as long as the work lasts. The main risk is context that outlives its purpose: access granted for one task persists, data stays on terms nobody rechecks, and an output leaves before review. This page sets out how permission and context drift develop, how they are measured, and what project owners and data owners need to keep a workstation inside its mandate.

02پرسیارەکە

Project workstations: how the risk develops.

Project onboarding, persistent context and permissions. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.

میکانیزم

Permission drift

Access is granted for a task, a role or a deadline and then outlives it. People move teams, contractors finish, agents are added for one analysis and kept. Each grant was reasonable when made; together they open more than any current purpose justifies.

میکانیزم

Context accumulates

Notes, intermediate files, cached extracts and agent memory pile up over months. Persistent context is what makes a workstation useful, and it is also where restricted data ends up in places its owner never approved, outside the record of what entered the project.

میکانیزم

Terms change underneath

A data owner narrows a licence, withdraws a permitted purpose or reclassifies a dataset. Unless the change reaches every copy, derived table and model trained on the data, the project keeps working on terms that no longer hold.

میکانیزم

Outputs leave the boundary

An unreviewed figure is pasted into a briefing, a draft map is shared by link, a model is exported. Once outside, an output carries the authority of the project without its caveats, and recalling it is slow or impossible.

03چاودێری

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

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

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

Project workstations · Project space 12 · Cluster east

  • کارە کارا
    11چالاک
  • چاوەڕوانی ڕیز، p50
    3کەمترینئاسایی
  • ئەمڕۆ کاردەکات
    81023
  • کۆتا بەکارهاتوو، % ئەم مانگە
    79چاودێری
IllustrativeGCRI · Foundry

کارەکان

J-19648کۆمەڵەی مۆدێلی لافاوخاوەنی پڕۆژە00:46:12کارا
J-32079ڕەندەری کاشی، زووم 0 بۆ 12شوێنی کاری GIS00:04:40کارا
J-63588هەناردەکردنی بەڵگەپارێزەری مۆدێل00:00:39تەواو بوو
J-74223کۆمەڵەی بانگکردنی ئامرازی ئەیجێنتقوتووی تاقیکاریی ئەیجێنت00:01:41بلۆکی سیاسەت

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

  1. 10:40دەروازەبانگکردنی ئەیجێنت پێویستی بە پەسەندی مرۆڤ هەیە
  2. 10:53زانیاریتۆماری ڕاکردن لەسەر مۆر کراوە
  3. 11:21ئاگادارکردنەوەکۆتا گەیشتە 80 لە سەد بۆ پڕۆژەکە
Workspace and job console: the screen’s structure, terms and states for Project workstations.Example names and illustrative values; a design, not a record or a live system.
04In the five domains

Workstations are designed to let national teams work across domains in one place.

05ڕێگا و بەڵگە

How project workstations is modelled, measured and tested.

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

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

The model structure used for project workstations, 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ناونیشان
Access grants past their review datecount per projectهەفتانەAccess-control recordsچاودێریکراو
Time from role change to access revocationhoursper eventIdentity and access logsچاودێریکراو
Data sources with current owner terms recordedproportion of registered sourcesمانگانەSource registerDECLARED
Requests failed closed at the policy gatecount per perioddailyPolicy decision logsچاودێریکراو
Outputs released with a recorded reviewproportion of released outputsبۆ هەر وەشانێکReview and release recordsچاودێریکراو
Stored artefacts without a declared data classcountهەفتانەStorage inventory scanچاودێریکراو
Projects past closeout with live accesscountمانگانەProject registerچاودێریکراو
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
ORCID registryPersistent identifiers for researchers, used to tie actions to verified peopleCC0 for public data
Research Organization Registry (ROR)Persistent identifiers for the institutions that own projects and dataCC0
GA4GH Data Use OntologyMachine-readable data-use conditions that can travel with a datasetFree and open, attribution
RDA DMP Common StandardA machine-actionable data management plan covering purpose, storage, retention and sharingFree and open, attribution
SPDX License ListStandard identifiers for the licences recorded against each sourceCC0
Creative Commons and Open Data Commons licence textsThe terms behind most open datasets a project draws onPublic licence texts
National data protection authority guidanceLawful bases, transfer rules and breach notification duties for personal dataPublic records, per authority
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
Project ownersWho may act in the project, on which systems, and when it closesCurrent grants against roles; grants past review; closeout status
Data ownersWhether their data may enter, for which purpose, and whether it may train models or be publishedSource register with terms; copies and derived products traced to the source
Data protection authorities and officersWhether personal data processing in the project has a lawful basis and adequate safeguardsData classes present, processing locations, access logs, retention schedule
Review leadsWhether an output is ready to leave the projectLineage of the output, its evidence labels and the review record

Outputs this topic produces

  • Project charter with owner, purpose, data terms, openness profile and closeout point
  • Access reviews listing grants past their date
  • Source register with current owner terms per dataset
  • Release log linking each output to its review
09Core questions

What practitioners ask about project environments.

  • Who owns the question, and who is accountable for what the project produces?
  • Which data may enter, on whose terms, and for which purpose?
  • How is context kept across months of work without becoming an unmanaged archive?
  • How do permissions follow people, roles and agents as they change?
  • What happens to data, outputs and access when the project closes?
10Mechanisms

Scope first, then context, then permission.

A project is defined before it is opened: the question and the institution that owns it, an accountable owner, the people and agents who may act, the data sources with the owner’s terms for each, the systems it may reach, the deployment profile it runs on, an openness profile from open through consortium-shared and confidential to restricted, a review plan and a closeout point.

Persistent context is the main source of value and the main source of risk. Workstations are designed to share a common set of rooms, such as Station, Mission, Maps, Data, Builder, Reports and Knowledge, so that work looks the same across systems. What a person sees in each room depends on the project’s permissions, not on the room. Permission drift, where access granted for one purpose outlives that purpose, is a well-documented failure in shared research environments; the design answers it by evaluating each request, in the NXS-NSF (trust, authorisation and assurance) Sovereignty Framework, against identity, mandate, purpose and data class, and by failing closed when no explicit decision exists.

11Methods and limits

How it is engineered, and where the limits are.

ناسنامە

Verified and delegated

Identity assurance and recorded delegation, so that an action can always be traced to a person or an accountable agent.

سیاسەت

Attribute-based decisions

Access rules that combine role, purpose and data class, so that one sign-in does not open everything a person has ever been granted.

تۆمارەکان

Receipts

Each consequential action produces a receipt that the project owner can review.

Limits: policy engines are only as good as the policies written into them, and receipts show what happened, not whether it was wise. Project reviews remain a human responsibility.

12میتۆدەکان

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. Data engineering, interoperability and stewardshipValidation at the ingest boundary · Frozen data cuts for reproducible productsApplied here
  4. Artificial intelligence and machine learningEarth observation models with spatial validation · Model cards and promotion recordsApplied here
13Where this page’s references

Where this page’s references lead.

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

14پرسیارەکان

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

What is permission drift?
The gap that opens between what people and agents are allowed to do and what their current purpose requires. It builds from individually reasonable grants that are never reviewed, and it is closed by expiry dates, periodic review and deny by default.
Does signing in open everything a person has been granted?
In the design, no. Each request is evaluated against identity, mandate, purpose and data class for the project in hand. Being authenticated is not being authorised, and an entitlement held elsewhere does not carry over.
What happens when a project closes?
Access ends, retention rules decide what is kept and for how long, and data is returned to or deleted for its owner as agreed. Outputs already released keep their review record and lineage.
Can a workstation hold personal data?
Only where the data owner and the applicable data protection law allow it, with the data class declared and processing kept to the permitted location. The project owner and the data protection officer hold that decision.
Can I open a workstation now?
Not yet. Projects open when their terms and review capacity exist. Institutions can describe a candidate project to the contact form, and the acknowledgement gives a reference and names the next step.
Does the openness profile affect results?
No. It governs who can see the work, never whether its results are valid.
What happens at closeout?
Access is closed, outputs and records are retained as the terms require, and data is returned or deleted as its owner decided.
Can a project span several countries?
Yes, where each data owner agrees. Federation creates no right to move data; where data cannot move, analysis is designed to run where the data is held.
ڕاپۆرتەکانبەشداربە

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

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.