{
  "notice": "Illustrative mapping from the AI Governance Engineer Body of Knowledge v0.5.0 (not a claim of conformity)",
  "version": "0.5.0",
  "license": "CC BY 4.0",
  "licenseUrl": "https://creativecommons.org/licenses/by/4.0/",
  "schemaVersion": 1,
  "schema": "https://aigovernanceengineer.com/api/v1/schemas/control.json",
  "self": "https://aigovernanceengineer.com/api/v1/controls/aige-ctl-deploy-018.json",
  "source": "https://aigovernanceengineer.com/controls/deployment-and-monitoring#aige-ctl-deploy-018",
  "citation": {
    "title": "AI Governance Engineering: The Thesis & Body of Knowledge",
    "authors": [
      "Jorge García Aibar"
    ],
    "parentDoi": "https://doi.org/10.5281/zenodo.22956197",
    "conceptDoi": "https://doi.org/10.5281/zenodo.22857084"
  },
  "control": {
    "id": "AIGE-CTL-DEPLOY-018",
    "profile": "deployment-and-monitoring",
    "url": "https://aigovernanceengineer.com/controls/deployment-and-monitoring#aige-ctl-deploy-018",
    "json": "https://aigovernanceengineer.com/api/v1/controls/aige-ctl-deploy-018.json",
    "title": "Named responsibilities per team for each agent",
    "version": "0.2",
    "status": "draft",
    "reviewerStatus": "open",
    "depth": "derived",
    "objective": "For each agent, responsibilities are written down by team across its lifecycle (leaders, product, security and users), a person is named for each duty, the allocation is linked from the registry entry, and contracts with model developers, agent providers and hosts of MCP servers or tools state how obligations are shared.",
    "failureModes": [
      "An agent has an owner in the registry and no written allocation of the other duties, so no one answers for red teaming, user education or monitoring.",
      "A duty is assigned to a team with no named person.",
      "A contract with an agent provider or an MCP server host is silent on who answers for security, performance or data protection."
    ],
    "scope": "AI agents an organisation builds, buys or runs, including agents from external providers and the MCP servers or tools they use.",
    "enforcementPoints": [
      "deploy",
      "periodic"
    ],
    "verification": [],
    "evidence": [
      {
        "artefact": "Responsibility allocation per agent (the lifecycle RACI), linked from the agent's registry entry; contract clauses for external parties",
        "schemaId": "agent-register-entry",
        "schema": "https://aigovernanceengineer.com/schemas/agent-register-entry.v1.json",
        "layer": 2
      }
    ],
    "failureResponse": {
      "effect": "alert",
      "text": "An agent with no responsibility allocation linked from its registry entry, or a duty with no named person, is raised to the agent's owner."
    },
    "layer": 2,
    "secondaryLayers": [],
    "patterns": [],
    "seeds": [],
    "derivedFrom": [
      {
        "kind": "schema",
        "ref": "agent-register-entry",
        "url": "https://aigovernanceengineer.com/resources/templates#schema-agent-register-entry"
      },
      {
        "kind": "chapter",
        "ref": "governing-agents",
        "url": "https://aigovernanceengineer.com/bok/governing-agents"
      }
    ],
    "mappings": {
      "obligations": [],
      "iso42001": [],
      "nistAiRmf": [
        {
          "id": "GOVERN 2.1",
          "title": "Roles and responsibilities and lines of communication related to mapping, measuring, and managing AI risks are documented and are clear to individuals and teams throughout the organization."
        }
      ],
      "owasp": [],
      "atlas": [],
      "aiuc1": [],
      "csaAicm": [],
      "other": [
        {
          "framework": "IMDA MGF for Agentic AI v1.5",
          "ref": "2.2.1 Clear allocation of responsibilities within and outside the organisation, p.26",
          "note": "Direct fit: Responsibilities allocated to teams across the agent lifecycle; obligations shared with external parties set in contracts (p.28)"
        }
      ]
    },
    "references": [
      {
        "n": 58,
        "title": "Governing AI agents",
        "text": "Governing AI agents (AI Governance Engineering Body of Knowledge v0.5.0, chapter 23, section \"Named responsibilities\"). AI Governance Engineer (Jorge García Aibar). 2026-09.",
        "url": "https://aigovernanceengineer.com/bok/governing-agents#named-responsibilities",
        "verified": "primary"
      },
      {
        "n": 6,
        "title": "Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1",
        "text": "Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1 (subcategories cited by id: GOVERN 1.6, 1.7, 2.1, 2.2, 6.1; MAP 1.1, 3.5; MEASURE 2.3, 2.4, 2.11, 3.1, 3.3; MANAGE 1.1, 2.4, 3.1, 4.1, 4.3). NIST. 2023-01-26.",
        "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf",
        "verified": "primary"
      },
      {
        "n": 7,
        "title": "Model AI Governance Framework for Agentic AI, v1.5",
        "text": "Model AI Governance Framework for Agentic AI, v1.5 (published 2026-05-20, updated 2026-06-05; four dimensions: assess and bound the risks upfront, make humans meaningfully accountable, implement technical controls and processes, enable end-user responsibility). IMDA. 2026-06-05.",
        "url": "https://www.imda.gov.sg/-/media/imda/files/about/emerging-tech-and-research/artificial-intelligence/mgf-for-agentic-ai.pdf",
        "verified": "primary"
      }
    ],
    "implementationNotes": [
      "Allocate as chapter 23 sketches it: leaders set the goals, the permitted use cases and the limits on data access; product teams design, test, roll out, monitor and educate users; security teams set baseline guardrails and run red teaming and threat modelling; users follow the usage policies and report issues.",
      "Start from the lifecycle RACI template and keep one allocation per agent."
    ],
    "openQuestions": [
      "Verification procedure to be specified: the source material states what the control produces, not how a third party checks it; requires technical review.",
      "The agent register entry has an owner field but no field for the allocation itself; whether it belongs in the entry or in an extension awaits review."
    ],
    "observation": null,
    "observationSchema": "https://aigovernanceengineer.com/schemas/control-observation.v1.json",
    "examples": []
  }
}