G09 · PAGE · agentsGCRI dossier · service level R0
GCRINexus FoundryEstablished
Nexus Foundry · AI and agents

AI and agents

Nexus Foundry is the technical work environment of the Nexus Consortiums, and its public gateway is published by The Global Centre for Risk and Innovation (GCRI). AI agents and automated tools can be useful in that environment only if they act within limits that people set, record and can stop. This page explains which tool actions agents are designed to be permitted, how agents and models are evaluated before they receive authority, and the boundaries that apply to every agent action. The current service level is R0: information and enquiries.

Nexus FoundryRegister
  1. 01FieldsData and compute, Methods and modelling
  2. 02STEM methods6 canonical methods applied
  3. 03Topics8 subject pages
  4. 04Counterparts1 platforms in shared fields
  5. 05PublisherThe Global Centre for Risk and Innovation

GCRI · Established · service level R0

01In brief

The short answer.

AI agents in Nexus Foundry are automated tools that may act only within limits that people set, record and can stop. The page explains which tool actions agents are designed to be permitted, how agents and models are evaluated before they receive any authority, and the boundaries that apply to every agent action.

02Geography

Digital demand and connectivity in Southeast Asia.

Urban demand centres and the hubs that anchor digital and data infrastructure, shown for Southeast Asia as an example geography for this subject.

Urban demand centres and the hubs that anchor digital and data infrastructure.Indicator derived from Natural Earth at map scale; a screening view, not an assessment.
GCRI · Nexus Foundry · fieldDESIGN FIGURE
03Permitted actions

An agent acts only within a scoped authority record.

In the design of the Nexus Sovereignty Framework (NSF), every agent and tool holds an authority record that states its purpose, the tools it may call, the data classes it may touch, its rate limits and its kill-switch. Requests without an explicit policy decision fail closed, including agent and tool calls.

Scope

Declared tools and data

An agent calls only the tools and reads only the data its record names, inside one authorized project.

Receipts

The same receipts as people

Agent actions pass the same policy gates and receive the same receipts as human actions.

Stop

Kill-switches at the gate

Scopes, limits and kill-switches are enforced at the gate, not left to the agent's own configuration.

04Attribution

Every action is bound to an identity and a supervisor.

In research work in Labs, agents may run analyses and draft artifacts, but each action is bound to an agent identity, its configuration, model, tool set, budget and supervising institution, and it remains an assertion until a person reviews it. In Studio, agent behaviour inside a composition is declared with its purpose, tools and scope, and the trust spine enforces that scope at runtime.

05Evaluation

Evaluation comes before authority.

  1. 01

    Contract testing

    Integrations and agents are tested against their declared contracts before they receive authority in any tenant.

  2. 02

    Model evaluation

    Promotion of a model requires evaluation records, including red-team results where the use calls for them.

  3. 03

    Data use

    No tenant data is used for training without a recorded decision by the data owner.

  4. 04

    Review of outputs

    Agent outputs used in evidence, reports or decisions are reviewed and attributed to the people who accept them.

06Key terms

Terms used on this page.

Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.

TermDefinition
AI agentAn AI system that pursues goals by planning and taking actions with some autonomy.
Human oversightReview of automated decisions by people with the authority and information to change them.
Excessive agencyGranting an AI system more permissions or autonomy than its task requires, an OWASP risk category.
Kill switchA control that halts an agent's actions immediately when triggered.
07Boundaries

What agents never do.

  • Take a decision that belongs to an institution, an official or a competent authority.
  • Issue a warning, release funds, dispatch resources or sign an acceptance.
  • Act outside an authorized project, or on data the project has no right to use.
  • Present a draft as reviewed evidence.

Public questions about responsible AI are taken up on GCRI responsible technology, and by The Global Risks Alliance (GRA) for financial services at GRA AI and models.

08Questions

Questions and answers.

Can I connect my own agent to Nexus Foundry?
Not at R0. Agent and integration access opens with authorized projects, under the contract testing described here. Technical questions go to contact@therisk.global.
Who is responsible for what an agent does?
The supervising institution named in the agent's authority record, and the person who accepts its output. The agent is never the accountable party.
Can an agent be stopped immediately?
The design enforces kill-switches at the policy gate, so an operator can withdraw an agent's authority without relying on the agent to comply.
Is my data used to train models?
Not without a recorded decision by the data owner. Projects choose what their data may be used for.
Nexus Foundry

Bring your expertise to this field.

The current service level is R0: information and enquiries. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.

Have questions?