Agent Runtime Control Profile

Scope

Agents that call tools, in production and in evaluation harnesses, from registration to retirement: their identity, tools, memory, delegation, checkpoints, stop handles and telemetry. The environment an agent is evaluated in is covered by the evaluation environment profile.

31 controls, AIGE-CTL-AGENT-001 to AIGE-CTL-AGENT-031. Each one is anchored to a layer of the five-layer stack and to the patterns that implement it.

How to read a control

Every control has a stable id that never changes and is never reused, and the same record:

• Objective: the outcome the control secures, in one sentence.
• Failure modes: observable events that mean the control failed.
• Scope, enforcement points (on a pull request, at deploy, at runtime or on a schedule) and the failure response (deny, hold for approval or alert).
• Verification: how a third party would check it (inspect, test, observe or attest).
• Evidence: the artefact it leaves and the stack layer that keeps it.
• Mappings: obligations, ISO/IEC 42001 Annex A, the NIST AI RMF, OWASP and other references, each id checked against the site's registers.

Depth says how far a control is written. Specified: a verification procedure, evidence, implementation notes, two example observations and a page of its own. Derived from site material: restates existing site material (an agent control of chapter 23, a pattern, a record schema or a chapter, named on each control) and adds nothing that material does not say. Draft outline: objective, failure modes, scope and open questions only. This profile: 31 derived from chapter 23.

An observation is what a check of a control would emit: the control id, the subject checked, what was expected, what was observed, a status (pass, fail or not_applicable), a timestamp and the evidence behind it.

Mappings

Every control against the obligations, standards and threats it answers. Mappings are illustrative, not a claim of conformity; an empty cell means no mapping has been verified yet. AIUC-1 ids point at the public requirement index of the Artificial Intelligence Underwriting Company, cited here as a reference; this project is not affiliated with AIUC, and each mapping is our own reading of the requirement text. The same mappings, read from the framework side and across every profile, are in the controls crosswalk.

Open questions

The questions this draft leaves open, with the controls that raise each one.

• Verification procedure and evidence schema to be specified; requires technical review. (001, 002, 003, 004, 005, 006, 007, 008, 009, 010, 011, 012, 013, 014, 015, 016, 017, 018, 019, 020, 021, 022, 023, 024, 025, 026, 027, 028, 029, 030, 031)
• Chapter 23 ties this control to the EU AI Act articles it names; the derivation carries obligations only through mapped OWASP Agentic threats, so the obligation mapping awaits review. (030, 031)

Changelog

• v0.1 (2026-09-26): First draft: 31 controls derived from the agent controls of chapter 23, open for technical review.

Sources

Machine-readable

• Each control as JSON, for example AIGE-CTL-AGENT-001: the link sits at the foot of every control above.
• All controls as JSON: every control of every profile, in the envelope of the open data API.
• JSON Schema of the controls dataset: generated from the same registry.
• Control observation schema: the record a check of a control emits: control_id, subject, expected, observed, status, timestamp, evidence.
• Observation example: a filled record that validates against the schema.
• Observation template: the same fields in Markdown, with short guidance.
• This page as Markdown: /controls/agent-runtime.md. Every dataset of the site is in the open data API.

Review this profile

Review happens in the open, on GitHub. Pick a control, check it against a system you run or know, and say what is wrong or missing: an objective that cannot be verified, a failure mode that is not observable, a mapping that does not hold. Each control has its own button above; this one reviews the profile as a whole, through the control review form.

@misc{aige2026page,
  author       = {Jorge García Aibar},
  title        = {{Agent Runtime Control Profile v0.1 (draft)}},
  howpublished = {In AI Governance Engineering: The Thesis \& Body of Knowledge},
  year         = {2026},
  version      = {0.5.0},
  doi          = {10.5281/zenodo.22857084},
  url          = {https://aigovernanceengineer.com/controls/agent-runtime},
  note         = {Version 0.5.0}
}