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.
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.
权限漂移
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.
背景不断积累
笔记、中间文件、缓存摘录和智能体记忆会在数月中不断积累。持久化上下文使工作站更有用,但受限数据也会因此流入其所有者从未批准的位置,脱离项目中关于哪些数据已进入的记录。
条款在底层发生变化
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.
输出离开边界
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.
工作区与作业控制台。
团队跟踪该主题时会使用的界面:其指标、状态与决策。名称为示例,数值仅作示意。
工作区与作业控制台
项目工作站 · 项目空间 12 · 东区集群
- 运行中的作业11活跃
- 排队等待,p503分钟正常
- 今日运行81023
- 本月已用配额,%79关注
就业
| J-19648 | 洪水模型集合 | 项目所有者 | 00:46:12 | 运行中 |
| J-32079 | 瓦片渲染,缩放级别 0 至 12 | GIS 工作空间 | 00:04:40 | 运行中 |
| J-63588 | 证据导出 | 模型管理方 | 00:00:39 | 已完成 |
| J-74223 | 智能体工具调用批次 | 智能体沙盒 | 00:01:41 | 策略拦截 |
政策事件
- 10:40关口代理调用需要人工批准
- 10:53信息运行记录已封存
- 11:21预警项目配额已达 80%
Workstations are designed to let national teams work across domains in one place.
项目工作站如何建模、测量和测试。
模型、其假设、数据和不确定性,以科学家或工程师会核查的形式呈现。结构遵循已发表的方法。所取数值仅为示意,不是研究发现。
模型、方程与假设
The model structure used for project workstations, the assumptions it makes and how each is tested.
Ri = f(Hi, Ei, Vi, Ci)危害、风险暴露、脆弱性和应对能力EAL = ∑k pk · Lkover events k with annual probability pkxt+1 = A xt + B ut + εtA carries the couplings, u the shock, ε the error| 假设 | 为何制作 | 如何检验 |
|---|---|---|
| 在一次事件中,危害与暴露相互独立 | 使损失积分保持可计算 | 与基于联合记录拟合的 copula 进行比较 |
| 耦合在工作点附近是线性的 | 让冲击通过 A 传播 | 在线性范围之外施加扰动并比较 |
| 脆弱性曲线可以在不同地点之间迁移使用 | 很少有本地曲线可用 | 在有观测损失的地方据此进行验证 |
- 输入
- 带溯源信息的版本化数据集
- 成果
- 分布,绝不是单一数字
- 代码
- 连同模型卡和测试一起发布
- 复现
- 相同的数据、代码、环境和随机种子
衡量什么,以及衡量得如何。
每个指标都注明其单位、频率、背后的来源类型以及数值将附带的证据标签。此处不显示数值:数值由计划依据其自身权限提供。
| 指标 | 单位 | 节奏 | 来源类型 | 标签 |
|---|---|---|---|---|
| Access grants past their review date | 每个项目的数量 | 每周 | Access-control records | 观测 |
| 从角色变更到访问权限撤销的时间 | 小时 | 每个事件 | 身份与访问日志 | 观测 |
| Data sources with current owner terms recorded | 已登记来源所占比例 | 每月 | 来源登记册 | 已声明 |
| Requests failed closed at the policy gate | 每期计数 | 每日 | 政策决策日志 | 观测 |
| 经记录审查后发布的成果 | proportion of released outputs | 每次发布 | 审查和发布记录 | 观测 |
| Stored artefacts without a declared data class | 计数 | 每周 | 存储清单扫描 | 观测 |
| 已结项但仍有有效访问权限的项目 | 计数 | 每月 | Project register | 观测 |
证据来自何处。
具名公共数据集与机构记录,各自注明许可类别。依协议获得的来源仅按其条款使用,绝不再次发布。
| 来源 | 它提供什么 | 许可类别 |
|---|---|---|
| ORCID 登记册 | 研究人员的持久标识符,用于将行动与经核实的人员关联 | CC0 for public data |
| 研究机构注册库(ROR) | 项目和数据所属机构的持久标识符 | CC0 |
| GA4GH Data Use Ontology | 可随数据集一同流转的机器可读数据使用条件 | 免费开放,须署名 |
| RDA DMP Common Standard | A machine-actionable data management plan covering purpose, storage, retention and sharing | 免费开放,须署名 |
| SPDX 许可证列表 | Standard identifiers for the licences recorded against each source | CC0 |
| Creative Commons and Open Data Commons licence texts | The terms behind most open datasets a project draws on | Public licence texts |
| National data protection authority guidance | Lawful bases, transfer rules and breach notification duties for personal data | 各主管机构的公开记录 |
由谁决定,以及证据服务于什么。
Foundry 负责准备证据。以下决定由所列机构依其自身规则作出,绝不由平台作出。
| 谁来决定 | 问题 | 本页面服务的证据 |
|---|---|---|
| 项目负责人 | 谁可以在项目中行动、作用于哪些 系统,以及何时关闭 | 现行资助与角色的对照;超过审查期限的资助;结项状态 |
| 数据所有方 | Whether their data may enter, for which purpose, and whether it may train models or be published | Source register with terms; copies and derived products traced to the source |
| Data protection authorities and officers | Whether personal data processing in the project has a lawful basis and adequate safeguards | 涉及的数据类别、处理地点、访问日志、保留时间表 |
| 审查负责人 | 输出成果是否已准备好离开项目 | 输出成果的来源追溯、证据标签和审查记录 |
该主题产生的产出
- Project charter with owner, purpose, data terms, openness profile and closeout point
- 列出已过期授权的访问权限审查
- Source register with current owner terms per dataset
- 将每项产出与其审查相关联的发布日志
从业人员对项目环境的常见提问。
- Who owns the question, and who is accountable for what the project produces?
- 哪些数据可以进入,依据谁的条件,出于什么目的?
- 如何在数月的工作中保持上下文,又不使其变成无人管理的档案?
- 当人员、角色和智能体发生变化时,权限如何随之调整?
- What happens to data, outputs and access when the project closes?
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.
How it is engineered, and where the limits are.
Verified and delegated
身份保证和有记录的授权委托,使任何行动始终可以追溯到某个人或负有责任的代理。
Attribute-based decisions
结合角色、用途和数据类别的访问规则,使一次登录不会打开某人曾经获得授权的全部内容。
回执
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.
Where this page’s references lead.
阅读本页时所对照的机构和文件。状态和版本会变化;每个链接都指向发布机构。
问题与解答。
What is permission drift?
登录是否会开放一个人被授予的全部内容?
项目结束时会发生什么?
工作站可以存放个人数据吗?
我现在可以开通工作站吗?
开放程度概况是否影响结果?
What happens at closeout?
Can a project span several countries?
从本页贡献证据。
Reports 是联合体的季刊。您对该主题的了解可以成为下一期中的证据、案例或更正,署名归您,并在属于您本人作品时以 CC BY 4.0 发布。
- 电子邮件网关 GW-GCRI从本页发送证据、更正、案例、方法、审查、翻译或概况投稿。它会带上本页标签送达,由负责的编辑接收。
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- 报告GCRI查看所有贡献方式贡献类型、各自的评审方式、您获得的署名、许可协议,以及绝不接受的内容。
切勿发送个人数据、敏感基础设施细节或您无权分享的任何内容。贡献在使用前会经过审查;发送贡献不赋予署名权或编辑权,赞助也绝不能换取研究结论。
法律文件。
本网站上的地图、数据和图表仅作为背景和一般信息展示。它们不是建议、预测或预警;信息的局限见免责声明和数据说明。