Model-Based Layer
type: Control Layer
comment: Enforcement via a model-based safeguard, most effective where risks are hard to define through fixed rules, e.g. harmful-content detection.

Agent Robustness
comment: The agent's response to errors and edge cases as it reacts and adapts to real-world situations.
type: Testing Dimension

CE Marking Record
has applicability condition: ApplicabilityCondition
  for risk level: RiskLevelHigh
  at lifecycle stage: DeploymentStage
  type: Applicability Condition
  for actor: AIProvider
comment: Documents that the CE conformity marking has been affixed to the AI system, as required by Article 48.
type: Class
subclass of: Compliance Record
evidences obligation: CEMarking

Annual
type: NamedIndividual

Oversight Effectiveness Record
subclass of: Compliance Record
comment: Documents measures ensuring that human oversight of an agentic system remains effective over time, notwithstanding automation bias and alert fatigue: measured human override rates, review response times, outlier-reviewer analysis, and overseer training (MGF §2.2.2). Evidences the Article 14(4) requirement that oversight measures enable persons to remain aware of automation bias, and its operational counterpart in Article 26(2).
type: Class
subclass of: Human Oversight Record
has applicability condition: ApplicabilityCondition
  for risk level: RiskLevelHigh
  for system type: Agentic AI System
  for actor: AIDeployer
  type: Applicability Condition
  at lifecycle stage: OperationStage
  for actor: AIProvider
pending article: Articles 14(4), 26(2)

pending article
comment: The EU AI Act article(s) this record type evidences, recorded as a string pending the availability of a machine-readable eu-aiact concept. Tooling can query for records with this property to identify gaps in eu-aiact coverage.
range: string
type: DatatypeProperty

Remote Biometric Identification Notification
has applicability condition: ApplicabilityCondition
  for system type: BiometricCategorisationSystem
  for risk level: RiskLevelHigh
  at lifecycle stage: OperationStage
  type: Applicability Condition
  for actor: AIDeployer
pending article: Article 26(11)
comment: Deployers using post-remote biometric identification systems must comply with additional notification and authorisation requirements, as required by Article 26(11). Includes notification to relevant authorities and compliance with national law restrictions.
type: Process Obligation
type: NamedIndividual

GPAI Technical Documentation Record
has applicability condition: ApplicabilityCondition
  for actor: AIProvider
  for system type: GPAIModel
  at lifecycle stage: DesignStage
  at lifecycle stage: DevelopmentStage
  type: Applicability Condition
pending article: Article 53(1)(b)
comment: Documents the technical documentation for a GPAI model, including training methodologies, data sources, computational resources, and evaluation results, as required by Article 53(1)(b). Must be kept up to date and made available to the AI Office and national authorities upon request.
subclass of: Compliance Record
type: Class

GPAI Transparency Record
subclass of: Compliance Record
pending article: Article 53(1)(a)
type: Class
has applicability condition: ApplicabilityCondition
  at lifecycle stage: DevelopmentStage
  at lifecycle stage: DesignStage
  for system type: GPAIModel
  for actor: AIProvider
  at lifecycle stage: DeploymentStage
  type: Applicability Condition
comment: Documents the information and documentation made available to downstream AI system providers to allow them to understand the capabilities and limitations of the GPAI model, as required by Article 53(1)(a). Includes model capabilities, limitations, intended and foreseeable misuse, and integration guidance.

Non-Conformity Register
type: Class
has applicability condition: ApplicabilityCondition
  type: Applicability Condition
  for risk level: RiskLevelHigh
  at lifecycle stage: OperationStage
  for actor: AIImporter
pending article: Articles 23(6), 23(7)
subclass of: Compliance Record
comment: Documents the register of non-conforming AI systems, complaints, and recalls maintained by the importer, including investigations conducted and notifications to distributors, as required by Articles 23(6)–(7).

Deployer Registration Verification
type: NamedIndividual
pending article: Articles 27(1), 49(1), 49(3)
comment: Private-sector deployers must verify, before putting a high-risk AI system into service, that the provider has registered it in the EU AI Database as required by Article 49(1). Where the deployer is a public authority, they bear their own registration obligation under Article 49(2) — this obligation covers the non-public-sector case only. Evidence of compliance is typically a dated screenshot or confirmation from the EU AI Database, held within the Quality Management System.
has applicability condition: ApplicabilityCondition
  for risk level: RiskLevelHigh
  at lifecycle stage: DeploymentStage
  type: Applicability Condition
  for actor: AIDeployer
  comment: Applies to all non-public-sector deployers of high-risk systems at the point of deployment.
type: Process Obligation

Authorised Representative Mandate Termination
pending article: Article 22(4)
type: Process Obligation
comment: Authorised representative must terminate the mandate and immediately inform market surveillance authority if the provider acts in non-compliance with its obligations, as required by Article 22(4).
has applicability condition: ApplicabilityCondition
  for actor: AuthorisedRepresentative
  for risk level: RiskLevelHigh
  type: Applicability Condition
type: NamedIndividual

at lifecycle stage
comment: The AI lifecycle stage(s) at which this condition applies. Uses DPV ai:LifecycleStage (ISO/IEC 22989).
domain: Applicability Condition
range: LifecycleStage
type: ObjectProperty

Fundamental Rights Impact Assessment Record
subclass of: FRIA
has applicability condition: ApplicabilityCondition
  for sector: CriticalInfrastructureSector
  for actor: AIDeployer
  for sector: EmploymentSector
  for sector: EducationSector
  for risk level: RiskLevelHigh-A6-2
  for sector: JusticeSector
  for sector: LawEnforcementSector
  type: Applicability Condition
  for sector: AsylumSector
  comment: Article 27 — FRIA required for deployers of Annex III high-risk systems in specific sectors.
  for sector: MigrationSector
  for sector: BorderControlSector
  for sector: DemocraticProcessSector
type: Class
comment: Documents the FRIA conducted by a deployer, as required by Article 27. Mandatory for specific Annex III use case areas and for all Annex III systems deployed by public sector entities.
subclass of: Compliance Record
evidences obligation: FRIA
has applicability condition: ApplicabilityCondition
  comment: Article 27 — public sector deployers must conduct FRIA for all Annex III high-risk systems.
  for risk level: RiskLevelHigh-A6-2
  for entity type: PublicSector
  type: Applicability Condition
  for actor: AIDeployer

Authorised Representative Mandate Record
subclass of: Compliance Record
has applicability condition: ApplicabilityCondition
  for risk level: RiskLevelHigh
  at lifecycle stage: DeploymentStage
  type: Applicability Condition
  at lifecycle stage: InceptionStage
  for actor: AuthorisedRepresentative
type: Class
comment: Documents the written mandate from a provider to an authorised representative, covering all obligations listed in Article 22(3). The mandate must be kept up to date and made available to market surveillance authorities upon request. Required by Article 22(1)–(2).
pending article: Article 22(1), 22(2)

Transparency Record
has applicability condition: ApplicabilityCondition
  for system type: Chat Bot
  for risk level: RiskLevelTransparencyRequired
  comment: Article 50(1) — providers and deployers of chatbots must disclose to users that they are interacting with an AI system.
  for actor: AIProvider
  type: Applicability Condition
  for actor: AIDeployer
has applicability condition: ApplicabilityCondition
  at lifecycle stage: DesignStage
  type: Applicability Condition
  for risk level: RiskLevelHigh
  comment: Article 13 — providers of high-risk AI systems must supply instructions for use to deployers.
  at lifecycle stage: DeploymentStage
  at lifecycle stage: DevelopmentStage
  for actor: AIProvider
type: Class
subclass of: Compliance Record
has applicability condition: ApplicabilityCondition
  comment: Article 50(2)/(3)/(4) — providers must label AI-generated content (deepfakes, synthetic audio/video/images, AI-generated text on matters of public interest) and disclose emotion recognition or biometric categorisation use.
  type: Applicability Condition
  for actor: AIProvider
  for system type: BiometricCategorisationSystem
  for system type: AI Content Generator
  for system type: EmotionRecognitionSystem
  for actor: AIDeployer
  for risk level: RiskLevelTransparencyRequired
pending article: Article 50
comment: Documents transparency obligations. For high-risk systems (Article 13): instructions for use provided to deployers. For Article 50 systems: disclosure that users are interacting with AI (chatbots), that content is AI-generated (deepfakes), or that emotion recognition/biometric categorisation is in use.
evidences obligation: InstructionForUse

Importer Cooperation with Authorities
pending article: Article 23(8)
type: Process Obligation
type: NamedIndividual
has applicability condition: ApplicabilityCondition
  type: Applicability Condition
  for actor: AIImporter
  for risk level: RiskLevelHigh
comment: Importer must cooperate with market surveillance authorities and provide all requested information and documentation to demonstrate conformity, as required by Article 23(8).

has attestation status
type: ObjectProperty
range: Attestation Status
domain: Compliance Record

Agentic Risk
comment: A risk specific to, or significantly amplified by, agentic AI systems (IMDA MGF for Agentic AI §1.2). Use with airo:hasRisk.
type: Class
subclass of: Risk

has agent component
range: Agent Component
type: ObjectProperty
comment: Links an agentic AI system to one of its components (model, instructions, memory, planning, tools, protocols, controls, logging).
domain: Agentic AI System

for risk level
comment: The risk level(s) for which this condition applies.
type: ObjectProperty
domain: Applicability Condition

AI Literacy Record
comment: Documents that the organisation ensures sufficient AI literacy of staff and other persons dealing with the operation and use of AI systems on their behalf, as required by Article 4. Evidenced by training records, competency frameworks, assessment results, and awareness briefings. Scoped to the organisation, not individual AI systems.
subclass of: Compliance Record
pending article: Article 4
type: Class
has applicability condition: ApplicabilityCondition
  type: Applicability Condition
  for actor: AIDeployer
  for actor: AIImporter
  for actor: AIProvider
  for actor: AIDistributor

Access Control
subclass of: Agent Control
comment: Limits what an agent is allowed to see, use or change, including restricting access to sensitive data, tools and systems.
type: Class

Human Health and Social Work Activities
type: Economic Sector
comment: NACE Rev. 2 section Q. For sector-specific purposes use sector-health: terms with dpv:hasPurpose.
notation: Q

EU AI Database Registration Record
comment: Documents registration in the EU AI Database, mandatory before placing a high-risk AI system on the market, as required by Articles 49 and 71. Authorised representatives may perform registration on behalf of the provider per Article 22(3)(a). Public sector deployers must also register before putting high-risk systems into service per Article 49(2).
has applicability condition: ApplicabilityCondition
  comment: Article 49(2) — public authorities and Union institutions must register before putting high-risk systems into service.
  for risk level: RiskLevelHigh
  for entity type: PublicSector
  for actor: AIDeployer
  type: Applicability Condition
  at lifecycle stage: DeploymentStage
type: Class
has applicability condition: ApplicabilityCondition
  at lifecycle stage: DeploymentStage
  for actor: AIProvider
  type: Applicability Condition
  for risk level: RiskLevelHigh
pending article: Articles 49, 71
has applicability condition: ApplicabilityCondition
  for actor: AuthorisedRepresentative
  comment: Article 22(3)(a) — authorised representative registers on behalf of provider.
  for risk level: RiskLevelHigh
  at lifecycle stage: DeploymentStage
  type: Applicability Condition
subclass of: Compliance Record

Post-Market Monitoring Record
subclass of: Compliance Record
has applicability condition: ApplicabilityCondition
  for actor: AIProvider
  for risk level: RiskLevelHigh
  at lifecycle stage: OperationStage
  type: Applicability Condition
type: Class
comment: Documents post-market monitoring activities for a high-risk AI system, including the monitoring plan and ongoing performance tracking, as required by Article 72.
evidences obligation: PostMarketMonitoringSystem

Applicability Condition
comment: A set of conditions that determine when an EU AI Act obligation applies. Conditions can include actor role, risk level, lifecycle stage, use case category, entity type, or any combination. An obligation may have multiple ApplicabilityConditions (disjunction — any one set of conditions is sufficient).
type: Class

Read-Only Scope
type: Action Scope
comment: The agent may only read and retrieve information from the system.

Agent and Human Collaborate
comment: The agent requires human approval at significant steps (e.g. before writing to a database or making a payment); the human can intervene at any time by taking over or pausing the agent.
type: Autonomy Level

Delegation of Authority Record
comment: Records a delegation of authority from a human user or organisational role to an agent: who delegated, to which agent, the permission scope granted, and its validity window (MGF §2.1.2). The agent's permissions should not exceed those of the authorising human. Supports Article 14/26 oversight evidence and Article 12 traceability.
has applicability condition: ApplicabilityCondition
  at lifecycle stage: OperationStage
  for system type: Agentic AI System
  type: Applicability Condition
  at lifecycle stage: DeploymentStage
  for actor: AIDeployer
pending article: Articles 12, 14, 26 (agentic profile)
subclass of: Compliance Record
type: Class

Autonomy Level
type: Class
comment: The degree to which the agent decides how to act towards a goal, determined by its instructions and the level of human involvement (MGF §1.1.3, drawing on the Knight First Amendment Institute's Levels of Autonomy for AI Agents). The declared level is key evidence for how Article 14/26 human oversight is designed.

valid until
domain: Delegation of Authority Record
type: DatatypeProperty
comment: End of the delegation's validity window.
range: dateTime

Internal Processes
type: Governance Activity
type: NamedIndividual
comment: Ongoing internal governance and quality management obligations including the quality management system and corrective actions (Articles 16-17, 20).

Tool Misuse
comment: The agent calling the wrong tools, the right tools with wrong inputs, hallucinated tools, or tools in a biased manner (MGF §1.2.1).
type: Class
subclass of: Agentic Risk

Authorised Representative Documentation Provision
pending article: Article 22(3)(b)
has applicability condition: ApplicabilityCondition
  for risk level: RiskLevelHigh
  type: Applicability Condition
  for actor: AuthorisedRepresentative
type: Process Obligation
comment: Authorised representative must provide market surveillance authority with all information and documentation necessary to demonstrate conformity of the high-risk AI system, as required by Article 22(3)(b).
type: NamedIndividual

Law Enforcement and Justice
comment: NACE Rev. 2 section O (specifically O84.23 — Justice and judicial activities). For sector-specific purposes use sector-law: terms with dpv:hasPurpose.
notation: O
type: Economic Sector

registered in
comment: The centralised registry from which the agent's identity and permissions are issued and tracked, preventing agent sprawl (MGF §2.1.2).
type: ObjectProperty
domain: Agent Identity Record

PRISM — EU AI Act Compliance Record-Keeping Ontology
extends: aiact
type: Ontology
created: 2026-04-01
version IRI: https://w3id.org/prism/0.4.0
type: Vocabulary
creator: Paola Arce
version info: 0.4.0
creator: Kate Hughes
relies on: airo
preferred namespace uri: https://w3id.org/prism#
relies on: dpv
modified: 2026-07-05
relies on: aiact
description: PRISM extends AIRO (AI Risk Ontology), the W3C Data Privacy Vocabulary (DPV) 2.3, and its EU AI Act extension (eu-aiact) with structured mappings from legal obligations to compliance record types, sector-specific interpretations, and attestation workflows. It is designed to underpin audit-grade AI governance record-keeping for providers and deployers of AI systems under the EU AI Act. Version 0.4.0 adds an agentic AI profile (agent components, action-space and autonomy classifications, controls, oversight design, agent identity and delegation records, agentic risks, and agent-specific testing and change management records) whose vocabulary is drawn from IMDA (Singapore)'s Model AI Governance Framework for Agentic AI v1.5; mappings from that voluntary framework to EU AI Act articles are interpretive.
license: eupl-text-eupl-12
creator: Maria Milagros Maqueda
imports: airo
preferred namespace prefix: prism
extends: airo
extends: dpv

Emergent Behaviour
subclass of: Agentic Risk
type: Class
comment: Unpredictable behaviour arising when multiple non-deterministic agents interact, which cannot be predicted from testing each agent individually.

Input Data Quality Record
type: Class
subclass of: Compliance Record
has applicability condition: ApplicabilityCondition
  at lifecycle stage: OperationStage
  type: Applicability Condition
  for actor: AIDeployer
  for risk level: RiskLevelHigh
comment: Documents that the deployer ensures appropriate input data is fed to the AI system during operation, as required by Article 26.
pending article: Article 26

SHA-256 hash
domain: Compliance Record
type: DatatypeProperty
range: string
comment: Hash of the named graph at write time, for immutability verification.

covers testing dimension
comment: A testing dimension covered by this agentic testing record.
range: Testing Dimension
type: ObjectProperty
domain: Agentic Testing Record

Continuous
type: NamedIndividual

Regulatory Trigger
type: Change Trigger
comment: Changes in compliance requirements.

Agent Change Management Record
type: Class
has applicability condition: ApplicabilityCondition
  at lifecycle stage: OperationStage
  for actor: AIProvider
  for risk level: RiskLevelHigh
  for system type: Agentic AI System
  for actor: AIDeployer
  type: Applicability Condition
comment: Documents a change to an agentic system under a defined change review process: the trigger that initiated review and the risk category of the change (MGF §2.3.3). Material and critical changes inform the substantial-modification analysis under Articles 25(1)(b) and 43(4), and feed Article 72 post-market monitoring.
pending article: Articles 25(1)(b), 43(4), 72 (agentic profile)
subclass of: Compliance Record

Risk Management Record
type: Class
comment: Documents the risk management system for a high-risk AI system, as required by Article 9. Must cover the full lifecycle and be updated continuously. Subclass of both prism:ComplianceRecord and airo:RiskControl.
has applicability condition: ApplicabilityCondition
  at lifecycle stage: ValidationStage
  type: Applicability Condition
  at lifecycle stage: InceptionStage
  at lifecycle stage: DesignStage
  at lifecycle stage: DevelopmentStage
  at lifecycle stage: OperationStage
  at lifecycle stage: ContinuousValidationStage
  for actor: AIProvider
  at lifecycle stage: VerificationStage
  for risk level: RiskLevelHigh
  at lifecycle stage: ReevaluationStage
evidences obligation: RiskManagementSystem
subclass of: RiskControl
subclass of: Compliance Record

mean approval response time
comment: The mean time humans spend reviewing agent actions before approving, over the reporting period. Very short times may signal automation bias or review fatigue (MGF §2.2.2).
type: DatatypeProperty
range: duration
domain: Oversight Effectiveness Record

Material Change
type: Change Category
comment: E.g. model updates or autonomy adjustments; may require a full governance review and a substantial-modification assessment under Articles 25(1)(b)/43(4).

Incident Log
type: Class
comment: An append-only, cryptographically hashed log of serious incidents or malfunctions involving an AI system. Use airo:hasRisk on individual log entries to link to the airo:Risk being documented.
subclass of: Compliance Record

Runtime Layer
type: Control Layer
comment: Enforcement that monitors and intervenes during execution, e.g. rate limits on tool use or input validation before responses are acted upon.

human override rate
range: decimal
type: DatatypeProperty
comment: The measured frequency (0.0 to 1.0) at which humans reject or modify agent actions over the reporting period. A very low rate may signal rubber-stamping (automation bias); interpret alongside response times (MGF §2.2.2).
domain: Oversight Effectiveness Record

Document Retention Record
type: Class
comment: Documents that the importer maintains a copy of the EU Declaration of Conformity and has access to technical documentation for 10 years after the AI system has been placed on the market, as required by Article 23(5).
pending article: Article 23(5)
subclass of: Compliance Record
has applicability condition: ApplicabilityCondition
  at lifecycle stage: DeploymentStage
  type: Applicability Condition
  for actor: AIImporter
  for risk level: RiskLevelHigh
  at lifecycle stage: OperationStage

User-Defined Boundary
type: Checkpoint Trigger
comment: A boundary the end user defines beyond organisation-set limits, reflecting their own risk appetite, e.g. requiring approval for purchases above an amount.

Agentic Testing Record
has applicability condition: ApplicabilityCondition
  for risk level: RiskLevelHigh
  for system type: Agentic AI System
  at lifecycle stage: VerificationStage
  type: Applicability Condition
  at lifecycle stage: ValidationStage
  for actor: AIProvider
  for actor: AIDeployer
pending article: Article 15 (agentic profile)
subclass of: Compliance Record
type: Class
comment: Documents agent-specific pre-deployment testing across the MGF §2.3.2 dimensions (overall task execution, policy adherence, tool calling, robustness), including whole-workflow testing, multi-agent testing, testing in realistic environments, and repeated runs across varied datasets. Specialises the Article 15 evidence for agentic systems; declare covered dimensions with prism:coversTestingDimension.
subclass of: Accuracy, Robustness and Cybersecurity Record

Logging and Monitoring Component
comment: Records agent actions, decisions and interactions across all components to enable monitoring, debugging and accountability. For high-risk systems this component realises the Article 12 logging capability documented in a prism:LoggingRecord.
subclass of: Agent Component
type: Class

Data Governance Record
subclass of: Compliance Record
has applicability condition: ApplicabilityCondition
  type: Applicability Condition
  for risk level: RiskLevelHigh
  at lifecycle stage: DevelopmentStage
  at lifecycle stage: DesignStage
  comment: Article 10(1)–(4) — general data governance for high-risk AI systems.
  for actor: AIProvider
has applicability condition: ApplicabilityCondition
  type: Applicability Condition
  for sector: CriticalInfrastructureSector
  at lifecycle stage: DesignStage
  for sector: EducationSector
  at lifecycle stage: DevelopmentStage
  comment: Article 10(5) — bias detection and mitigation using special-category data, applicable in sectors where discriminatory outcomes are particularly harmful (employment, credit, insurance, education, essential services).
  for actor: AIProvider
  for sector: EmploymentSector
  for risk level: RiskLevelHigh
pending article: Article 10
type: Class
comment: Documents data governance and management practices for training, validation, and testing datasets, as required by Article 10. Covers relevance, representativeness, error-freeness, and bias mitigation. Article 10(5) specifically requires bias detection and mitigation measures using special-category data where strictly necessary, with appropriate safeguards.

Agent Component
type: Class
comment: A core component of an agentic AI system as taxonomised in MGF §1.1.1: model, instructions, memory, planning and reasoning, tools, protocols, controls, and logging and monitoring. Each component is a distinct source of risk (MGF §1.2.1) and a distinct locus for technical controls (MGF §2.3.1).

Chat Bot
type: Class
comment: An AI system designed to interact with natural persons via text or speech. Providers and deployers of chatbots must disclose to users that they are interacting with an AI system, as required by Article 50(1). Pending eu-aiact modelling of this system type.

has applicability condition
range: Applicability Condition
type: ObjectProperty
comment: Links a compliance record type or process obligation to the conditions under which it applies.
domain: Class
  union of: Compliance Record
  union of: Process Obligation

has action scope
type: ObjectProperty
range: Action Scope
comment: Read-only or read-write scope. Declare on each tool component; may also summarise the widest scope at system level.

Supply Chain Verification Record
type: Class
has applicability condition: ApplicabilityCondition
  type: Applicability Condition
  for risk level: RiskLevelHigh
  for actor: AIDistributor
  at lifecycle stage: DeploymentStage
comment: Documents that an importer or distributor has verified the AI system's compliance with the AI Act before placing it on the market, as required by Articles 23(1)–(2) and 24(1)–(2).
subclass of: Compliance Record
has applicability condition: ApplicabilityCondition
  for actor: AIImporter
  at lifecycle stage: DeploymentStage
  type: Applicability Condition
  for risk level: RiskLevelHigh
evidences obligation: ConformityAssessment

implemented at layer
domain: Agent Control
range: Control Layer
comment: The enforcement layer of a control (structural, model-based, prompt, runtime). Queryable proxy for control strength: prefer structural for higher-risk actions.
type: ObjectProperty

for actor
domain: Applicability Condition
type: ObjectProperty
comment: The actor role(s) for which this condition applies.

Human Oversight Record
has applicability condition: ApplicabilityCondition
  for actor: AIDeployer
  for risk level: RiskLevelHigh
  at lifecycle stage: OperationStage
  type: Applicability Condition
comment: Documents the human oversight measures in place for a high-risk AI system. For providers (Article 14): design measures enabling effective human control. For deployers (Article 26): operational implementation of oversight. Must identify the named overseer, their authority, and any intervention events.
evidences obligation: ProviderHumanOversightMeasure
subclass of: Compliance Record
has applicability condition: ApplicabilityCondition
  at lifecycle stage: DesignStage
  at lifecycle stage: DevelopmentStage
  for actor: AIProvider
  type: Applicability Condition
  for risk level: RiskLevelHigh
evidences obligation: DeployerHumanOversightMeasure
type: Class

Corrective Action Record
subclass of: Compliance Record
pending article: Article 20
type: Class
comment: Documents corrective actions taken to address non-compliance, including notifications to authorities, as required by Article 20.
has applicability condition: ApplicabilityCondition
  for actor: AIProvider
  for risk level: RiskLevelHigh
  type: Applicability Condition

Supply Chain Verification
type: NamedIndividual
comment: The AI Act procedure in which importers and distributors verify that an AI system complies before placing it on the market (Articles 43-44).
occurs at stage: DeploymentStage
type: Regulatory Process

for entity type
domain: Applicability Condition
comment: The type of entity (e.g., public body) for which this condition applies. Only present when the obligation has entity-specific triggers.
type: ObjectProperty

Logging Record
subclass of: Compliance Record
type: Class
comment: Documents the automatic logging capabilities designed into a high-risk AI system and the retention of those logs, as required by Articles 12 and 19. Article 12 requires logging capabilities to be designed in; Article 19 requires retention of logs during operation.
has applicability condition: ApplicabilityCondition
  at lifecycle stage: OperationStage
  type: Applicability Condition
  for risk level: RiskLevelHigh
  at lifecycle stage: DesignStage
  at lifecycle stage: DevelopmentStage
  for actor: AIProvider
pending article: Articles 12, 19

Agent Sprawl
type: Class
subclass of: Agentic Risk
comment: Uncontrolled proliferation of agents without centralised management, causing provenance, compatibility and manageability issues. Mitigated by central identity cataloguing (prism:AgentIdentityRecord).

Internal System Access
type: System Access Type
comment: Tools internal to the organisation, such as searching and updating the organisation's databases.

Adversarial Testing Record
pending article: Article 55(1)(a)
subclass of: Compliance Record
has applicability condition: ApplicabilityCondition
  at lifecycle stage: VerificationStage
  for system type: HighImpactCapabilityGPAIModel
  type: Applicability Condition
  at lifecycle stage: ValidationStage
  at lifecycle stage: ContinuousValidationStage
  for actor: AIProvider
comment: Documents adversarial testing and model evaluation (red-teaming) conducted on a GPAI model with systemic risk, including testing methodologies, identified vulnerabilities, and mitigation measures, as required by Article 55(1)(a). Must include state-of-the-art evaluation tools and methodologies.
type: Class

EU Declaration of Conformity Record
comment: Documents the formal EU Declaration of Conformity statement, as required by Article 47.
subclass of: Compliance Record
evidences obligation: EUDeclarationOfConformity
has applicability condition: ApplicabilityCondition
  for risk level: RiskLevelHigh
  at lifecycle stage: DeploymentStage
  for actor: AIProvider
  type: Applicability Condition
type: Class

comprises agent
type: ObjectProperty
range: Agentic AI System
domain: Multi-Agent System
comment: Links a multi-agent system to a member agent.

Structural Layer
type: Control Layer
comment: Deterministic, system-level enforcement through predefined logic, e.g. access controls at the tool layer that prevent a tool from being called at all.

Miscoordination
subclass of: Agentic Risk
comment: Agents working together failing through bad communication or diverging interpretations of user intent.
type: Class

has architecture
type: ObjectProperty
comment: The coordination pattern of a multi-agent system (sequential, supervisor, swarm).
range: Agent Architecture
domain: Multi-Agent System

Overall Task Execution
type: Testing Dimension
comment: Whether the agent can complete its task accurately.

permission scope
domain: Delegation of Authority Record
comment: Human-readable statement of the scoped, least-privilege permissions granted, including any escalation paths.
type: DatatypeProperty
range: string

Checkpoint Trigger
comment: The category of action boundary that makes a checkpoint significant (MGF §2.2.2).
type: Class

Outlier or Atypical Behaviour
comment: The agent accessing a system outside its work scope or selecting an action far outside historical norms.
type: Checkpoint Trigger

Distributor Storage and Transport Conditions
has applicability condition: ApplicabilityCondition
  at lifecycle stage: DeploymentStage
  type: Applicability Condition
  for actor: AIDistributor
  for risk level: RiskLevelHigh
comment: Distributor must ensure appropriate storage and transport conditions while the system is under their responsibility, as required by Article 24(3).
pending article: Article 24(3)
type: Process Obligation
type: NamedIndividual

Accuracy, Robustness and Cybersecurity Record
subclass of: Compliance Record
type: Class
pending article: Article 15
has applicability condition: ApplicabilityCondition
  type: Applicability Condition
  at lifecycle stage: DesignStage
  at lifecycle stage: DevelopmentStage
  for actor: AIProvider
  for risk level: RiskLevelHigh
comment: Documents the measures ensuring accuracy, robustness, and cybersecurity of a high-risk AI system, as required by Article 15.

attested by
type: ObjectProperty
domain: Compliance Record

GPAI Registration Record
type: Class
has applicability condition: ApplicabilityCondition
  for actor: AIProvider
  at lifecycle stage: DeploymentStage
  type: Applicability Condition
  for system type: GPAIModel
subclass of: Compliance Record
comment: Documents registration of the GPAI model in the EU AI Database, as required by Article 53(1)(d).
pending article: Article 53(1)(d)

Right to Explanation Record
subclass of: Compliance Record
has applicability condition: ApplicabilityCondition
  type: Applicability Condition
  for actor: AIDeployer
  at lifecycle stage: OperationStage
  for risk level: RiskLevelHigh
comment: Documents the deployer's mechanism for providing affected persons with a meaningful explanation of the role the AI system played in a decision, as required by Article 86. Evidenced by explanation templates, documented explanation procedures, or logs of explanations provided to individuals.
pending article: Article 86
type: Class

High-Stakes Action
type: Checkpoint Trigger
comment: Actions such as editing sensitive data, final decisions in high-risk domains, or actions that may trigger liability.

has oversight checkpoint
type: ObjectProperty
comment: Links an agentic AI system, or the prism:HumanOversightRecord documenting its oversight design, to a defined human-approval checkpoint.
range: Oversight Checkpoint

Human Approval Control
type: Class
subclass of: Agent Control
comment: A requirement for a human to review or approve agent actions. Its placement is designed through prism:OversightCheckpoint definitions.

has compliance record
range: Compliance Record
sub property of: hasDocumentation
comment: Links an AI system to a compliance record. Subproperty of airo:hasDocumentation.
domain: AISystem
type: ObjectProperty

Tooling Provider
subclass of: Entity
comment: An entity providing tools or protocol infrastructure that agents rely on, e.g. hosts of MCP servers or third-party APIs (MGF §2.2.1). Not an EU AI Act actor; obligations towards it are contractual and should be recorded per MGF §2.2.1 (distribution of obligations, third-party opacity).
type: Class

Swarm Architecture
type: Agent Architecture
comment: Agents work at the same time, handing off to another agent when needed.

Prompt Injection
type: Class
subclass of: Agentic Risk
comment: Adversarial instructions embedded in content the agent processes (documents, web pages, tool outputs) redirecting it towards harmful actions, including data exfiltration through its tool access.

Agent Identity Record
comment: Documents the unique identity of a deployed agent, the party accountable for it, the capacity in which it acts, and its entry in a central agent registry (MGF §2.1.2). Supports Article 12 traceability and helps prevent agent sprawl. Best-practice record derived from the IMDA MGF; not itself an EU AI Act obligation.
type: Class
pending article: Article 12 (traceability, agentic profile)
subclass of: Compliance Record
has applicability condition: ApplicabilityCondition
  type: Applicability Condition
  for actor: AIDeployer
  for system type: Agentic AI System
  for actor: AIProvider

Economic Sector
subclass of: Sector
type: Class
comment: An economic sector classification based on NACE Rev. 2, identifying where an AI system operates. Distinct from eu-aiact Annex III sectors, which determine which obligations apply.

Provider Obligations Compliance List
comment: Article 16 lists the full set of provider obligations for high-risk AI systems (Arts. 9–49). Compliance is evidenced by having all required ComplianceRecords in place — this is a meta-obligation, not a standalone record. Gap analysis queries against this obligation should check for completeness of all provider record types.
pending article: Article 16
has applicability condition: ApplicabilityCondition
  for risk level: RiskLevelHigh
  type: Applicability Condition
  at lifecycle stage: InceptionStage
  for actor: AIProvider
type: Process Obligation
type: NamedIndividual

delegated to
range: Agentic AI System
comment: The agentic AI system receiving the delegated authority.
type: ObjectProperty
domain: Delegation of Authority Record

Technical Documentation Record
has applicability condition: ApplicabilityCondition
  at lifecycle stage: DevelopmentStage
  for actor: AIProvider
  at lifecycle stage: DesignStage
  for risk level: RiskLevelHigh
  type: Applicability Condition
comment: Documents the technical documentation demonstrating compliance, as required by Article 11 and specified in Annex IV.
subclass of: Compliance Record
type: Class
evidences obligation: TechnicalDocumentation

ontology version
type: DatatypeProperty
domain: Compliance Record
range: string
comment: The PRISM version under which this record was attested. Used to flag records for re-review when the ontology updates.

extraction confidence
type: DatatypeProperty
domain: Compliance Record
comment: Confidence score (0.0–1.0) assigned by the AI connector at extraction time.
range: decimal

Use per Instructions Record
pending article: Article 26
subclass of: Compliance Record
comment: Documents that the deployer is using the AI system in accordance with the provider's Instructions for Use, as required by Article 26.
type: Class
has applicability condition: ApplicabilityCondition
  at lifecycle stage: OperationStage
  type: Applicability Condition
  for risk level: RiskLevelHigh
  for actor: AIDeployer

has organisational record
comment: Links an actor (provider, deployer, importer, distributor) to an organisation-level compliance record that is not specific to a single AI system. Used for cross-cutting obligations such as AI literacy (Art. 4).
type: ObjectProperty
range: Compliance Record

Agent Operates, Human Approves
type: Autonomy Level
comment: The agent requires human approval only at critical steps or failures, such as deleting a database or making a payment above a predefined amount.

evidences obligation
comment: Links a compliance record type to the eu-aiact concept(s) it provides evidence for. Where no eu-aiact concept exists yet, this property is omitted and the applicable article is noted via prism:pendingArticle.
type: ObjectProperty

GPAI Incident Reporting Record
comment: Documents the reporting of serious incidents involving a GPAI model with systemic risk to the AI Office and relevant national authorities, as required by Article 55(1)(b). Includes incident description, corrective measures taken, and communication with downstream providers.
subclass of: Compliance Record
pending article: Article 55(1)(b)
has applicability condition: ApplicabilityCondition
  for actor: AIProvider
  at lifecycle stage: OperationStage
  for system type: HighImpactCapabilityGPAIModel
  type: Applicability Condition
type: Class

Governance Activity
comment: An ongoing governance activity that spans multiple AI lifecycle stages. Not bound to a single stage.
type: Class

has system access
range: System Access Type
comment: The kind of system reachable (sandboxed, internal, external). Declare on each tool component; may also summarise the widest access at system level.
type: ObjectProperty

has agent control
sub property of: has agent component
domain: Agentic AI System
range: Agent Control
comment: Links an agentic AI system to a control bounding its action-space or autonomy.
type: ObjectProperty

occurs at stage
range: LifecycleStage
comment: Links a regulatory process to the AI lifecycle stage(s) at which it occurs. Uses DPV ai:LifecycleStage (ISO/IEC 22989).
domain: Regulatory Process
type: ObjectProperty

Incident Reporting Record
type: Class
comment: Documents the reporting of serious incidents to authorities within the required 15-day window, as required by Article 73 (providers, importers, distributors) and Article 26 (deployers). Links to eu-aiact:SeriousIncident which models the incident event itself.
has applicability condition: ApplicabilityCondition
  for risk level: RiskLevelHigh
  comment: Article 73 — importers must report serious incidents to market surveillance authorities.
  at lifecycle stage: OperationStage
  type: Applicability Condition
  for actor: AIImporter
evidences obligation: SeriousIncident
has applicability condition: ApplicabilityCondition
  type: Applicability Condition
  for actor: AIDeployer
  comment: Article 26 — deployers must report serious incidents to provider and market surveillance authorities.
  at lifecycle stage: OperationStage
  for risk level: RiskLevelHigh
has applicability condition: ApplicabilityCondition
  for actor: AIProvider
  for risk level: RiskLevelHigh
  at lifecycle stage: OperationStage
  type: Applicability Condition
subclass of: Compliance Record

Compliance Record
type: Class
comment: A structured record that provides evidence of compliance with one or more EU AI Act obligations. Records must be attested by a named individual to be considered evidential. Subclass of airo:Documentation.
subclass of: Documentation

Sandboxed Access
comment: Sandboxed tools (e.g. for code execution or data analysis) that cannot affect any other system.
type: System Access Type

Environmental Trigger
comment: Domain shifts, business context changes.
type: Change Trigger

Public Administration and Defence
notation: O
type: Economic Sector
comment: NACE Rev. 2 section O (broad public administration). sector-publicservices is a draft DPV module — use the versioned URI. For sector-specific purposes use sector-pub: terms with dpv:hasPurpose when stable.

Sequential Architecture
type: Agent Architecture
comment: Agents work one after another in a linear or otherwise structured workflow; each agent's output becomes the next agent's input.

Memory Poisoning
type: Class
subclass of: Agentic Risk
comment: An attacker inserting content into an agent's persistent memory to influence later decisions (MGF §2.1.1 threat modelling).

Agent Platform Provider
type: Class
comment: An entity providing the platform on which agentic systems are built or operated (MGF §2.2.1). Distinct from the eu-aiact:AIProvider of the resulting system; the platform relationship affects visibility and control and belongs in the risk assessment (MGF §2.1.1, third-party solutions factor).
subclass of: Entity

Copyright and Training Data Policy Record
has applicability condition: ApplicabilityCondition
  at lifecycle stage: InceptionStage
  at lifecycle stage: DesignStage
  at lifecycle stage: DevelopmentStage
  for actor: AIProvider
  for system type: GPAIModel
  type: Applicability Condition
subclass of: Compliance Record
type: Class
comment: Documents the policy for complying with Union copyright law, including the identification and respect of opt-out rights under Article 4(3) of Directive (EU) 2019/790, and a sufficiently detailed summary of training data content, as required by Article 53(1)(c).
pending article: Article 53(1)(c)

Oversight Checkpoint
type: Class
comment: A defined point or action boundary in an agentic workflow at which human approval is required before the agent proceeds (MGF §2.2.2). Attach to the system or to a prism:HumanOversightRecord via prism:hasOversightCheckpoint; classify the boundary with prism:hasCheckpointTrigger.

Oversight Intervention
comment: A timestamped, append-only record of a named individual overriding or modifying an AI system's output. Cryptographically hashed at write time.
type: Class
subclass of: Human Oversight Record

delegated by
domain: Delegation of Authority Record
type: ObjectProperty
comment: The human user or organisational role delegating authority to the agent. The agent's permissions should not exceed this party's own.

Planning and Reasoning Component
subclass of: Agent Component
comment: The capability to output and follow a series of steps needed for a task. Plans can drift from user intent through hallucination or semantic misalignment (MGF §1.2.1).
type: Class

Importer Storage and Transport Conditions
pending article: Article 23(4)
type: Process Obligation
comment: Importer must ensure appropriate storage and transport conditions do not jeopardise the AI system's compliance, as required by Article 23(4).
has applicability condition: ApplicabilityCondition
  for risk level: RiskLevelHigh
  at lifecycle stage: DeploymentStage
  type: Applicability Condition
  for actor: AIImporter
type: NamedIndividual

Quality Management System Record
subclass of: Compliance Record
comment: Documents the quality management system covering governance, testing, incident handling processes, and procedures for cooperation with competent authorities, as required by Article 17. Includes documented procedures for responding to authority requests per Art. 22(8), 23(8), 24(5), 26(4).
evidences obligation: QualityManagementSystem
has applicability condition: ApplicabilityCondition
  for risk level: RiskLevelHigh
  type: Applicability Condition
  for actor: AIProvider
type: Class

Testing Dimension
type: Class
comment: A dimension of agent-specific testing (MGF §2.3.2).

Risk Assessment
type: Governance Activity
type: NamedIndividual
comment: Risk assessment activities including the Fundamental Rights Impact Assessment (FRIA) for Annex III high-risk use cases (Article 27).

Cascading Failure
comment: A mistake in one step propagating and amplifying across later steps of a multi-step workflow, resulting in outsized impact.
type: Class
subclass of: Agentic Risk

Operational Monitoring Record
type: Class
subclass of: Compliance Record
has applicability condition: ApplicabilityCondition
  for actor: AIDeployer
  for risk level: RiskLevelHigh
  at lifecycle stage: OperationStage
  type: Applicability Condition
comment: Documents the deployer's ongoing monitoring of AI system performance during use, as required by Article 26.
pending article: Article 26

Agent Architecture
type: Class
comment: A coordination pattern for a multi-agent system (MGF §1.1.2).

Agent Control
comment: A control limiting an agent's action-space or autonomy (MGF §1.1.1). Declare the enforcement layer with prism:implementedAtLayer; prefer structural over prompt-layer enforcement for higher-risk actions (MGF §2.3.1).
subclass of: RiskMitigationMeasure
subclass of: Agent Component
type: Class

Multi-Agent System
subclass of: Agentic AI System
comment: An agentic AI system in which multiple agents work together, whether sequentially, under a supervisor, or as a swarm (MGF §1.1.2). Member agents are linked with prism:comprisesAgent; the coordination pattern with prism:hasArchitecture. Multi-agent setups increase exposure to the systemic risks in Section 9e (miscoordination, conflict, collusion, emergent behaviour).
type: Class

Market Entry
occurs at stage: DeploymentStage
type: Regulatory Process
comment: The AI Act procedure covering formal market placement: EU Declaration of Conformity, CE marking, and EU AI Database registration (Articles 47-49).
type: NamedIndividual

has change trigger
range: Change Trigger
comment: The event category that initiated this change review.
domain: Agent Change Management Record
type: ObjectProperty

Instruction Component
comment: Natural language commands defining the agent's role, capabilities and behavioural constraints, e.g. a system prompt. The level of instruction detail (detailed SOP vs own judgment) is a primary determinant of autonomy.
type: Class
subclass of: Agent Component

has change category
comment: The risk categorisation assigned to the reviewed change.
range: Change Category
domain: Agent Change Management Record
type: ObjectProperty

Model Component
comment: The SLM, LLM or MLLM serving as the central reasoning and planning engine of the agent.
subclass of: Agent Component
type: Class

System Access Type
comment: The kind of system a tool, or an agent through its tools, can reach (MGF §1.1.3, action-space). One axis of the action-space; the other is prism:ActionScope.
type: Class

attested at
type: DatatypeProperty
domain: Compliance Record
range: dateTime

Worker Notification Record
has applicability condition: ApplicabilityCondition
  type: Applicability Condition
  at lifecycle stage: OperationStage
  for risk level: RiskLevelHigh
  for actor: AIDeployer
subclass of: Compliance Record
type: Class
pending article: Article 26
comment: Documents that employees and their representatives have been informed where AI systems are used in decisions affecting them, as required by Article 26.

Memory Component
comment: Short or long-term information storage accessible to the agent. Persistent memory that can store sensitive data across sessions increases the impact of data-related risks (MGF §2.1.1) and is the target of memory poisoning attacks.
subclass of: Agent Component
type: Class

Conformity Assessment Record
subclass of: Compliance Record
evidences obligation: ConformityAssessment
has applicability condition: ApplicabilityCondition
  at lifecycle stage: VerificationStage
  at lifecycle stage: ValidationStage
  comment: Self-assessment (Module A) — applies to most high-risk systems.
  for actor: AIProvider
  type: Applicability Condition
  for risk level: RiskLevelHigh
type: Class
has applicability condition: ApplicabilityCondition
  for actor: AIProvider
  for system type: BiometricCategorisationSystem
  for risk level: RiskLevelHigh-A6-2
  at lifecycle stage: VerificationStage
  type: Applicability Condition
  at lifecycle stage: ValidationStage
  comment: Third-party assessment required for biometric identification/categorisation systems (Article 43(1)).
comment: Documents the conformity assessment process — either self-assessment (Module A) for most systems, or third-party assessment for biometric and Annex I systems — as required by Articles 43–44.
has applicability condition: ApplicabilityCondition
  for risk level: RiskLevelHigh-A6-1
  at lifecycle stage: VerificationStage
  at lifecycle stage: ValidationStage
  comment: Third-party assessment required for biometric systems and Annex I safety components (Article 43(1)).
  for actor: AIProvider
  type: Applicability Condition

Tool Component
subclass of: Agent Component
comment: A tool enabling the agent to take actions and interact with other systems (files, databases, devices, transactions). The tools an agent may call, and the permissions on those tools, determine its action-space. Declare prism:hasSystemAccess and prism:hasActionScope on each tool.
type: Class

Irreversible Action
comment: Actions that cannot easily be undone, e.g. permanently deleting data, sending communications, making payments.
type: Checkpoint Trigger

Financial and Insurance Activities
comment: NACE Rev. 2 section K. For sector-specific purposes use sector-finance: terms with dpv:hasPurpose.
notation: K
type: Economic Sector

Distributor Non-Conformity Notification
has applicability condition: ApplicabilityCondition
  type: Applicability Condition
  for actor: AIDistributor
  for risk level: RiskLevelHigh
  at lifecycle stage: OperationStage
type: Process Obligation
type: NamedIndividual
comment: Distributor must inform provider or importer and market surveillance authority if the AI system presents a serious risk or is non-conforming, as required by Article 24(4).
pending article: Article 24(4)

Distributor Cooperation with Authorities
comment: Distributor must cooperate with market surveillance authorities and provide all requested information and documentation, as required by Article 24(5).
type: Process Obligation
type: NamedIndividual
pending article: Article 24(5)
has applicability condition: ApplicabilityCondition
  for risk level: RiskLevelHigh
  for actor: AIDistributor
  type: Applicability Condition

accountable party
domain: Agent Identity Record
comment: The supervising agent, human user, or organisational department to which this agent's identity is tied for accountability and tracking (MGF §2.1.2).
type: ObjectProperty

Agent Proposes, Human Operates
type: Autonomy Level
comment: The human reviews and approves every agent action.

Agentic AI System
subclass of: AISystem
type: Class
comment: An AI system consisting of one or more AI agents that possess some degree of independent planning, decision-making, and action-taking over multiple steps to achieve a user-defined goal (IMDA MGF for Agentic AI §1.1). Describe its bounds with prism:hasAutonomyLevel, prism:hasAgentComponent and prism:hasAgentControl.

has autonomy level
comment: The declared level of human involvement in the agent's decision-making. Key evidence for Article 14/26 oversight design.
type: ObjectProperty
domain: Agentic AI System
range: Autonomy Level

Change Category
comment: The risk categorisation of a reviewed change (MGF §2.3.3).
type: Class

Privilege Compromise
comment: An attacker exploiting the agent's credentials or permissions to act beyond the intended authorisation (MGF §2.1.1 threat modelling).
type: Class
subclass of: Agentic Risk

has checkpoint trigger
type: ObjectProperty
range: Checkpoint Trigger
domain: Oversight Checkpoint
comment: The category of action boundary the checkpoint guards (high-stakes, irreversible, outlier, user-defined).

Protocol Component
type: Class
subclass of: Agent Component
comment: A standardised way for the agent to communicate with tools or other agents, e.g. MCP or A2A. Poorly deployed or compromised protocol endpoints (such as untrusted MCP servers) are an agent-specific attack surface (MGF §1.2.1).

for sector
domain: Applicability Condition
type: ObjectProperty
range: Sector
comment: The Annex III sector for which this condition applies (e.g., eu-aiact:EmploymentSector). Uses eu-aiact sector concepts, which are subclasses of dpv:Sector. Distinct from dpv:hasSector on the AI system, which identifies the operational industry via NACE codes.

agent identifier
comment: The agent's unique identifier, ideally cryptographically verifiable (MGF §2.1.2).
type: DatatypeProperty
domain: Agent Identity Record
range: string

Appointment of Authorised Representative
type: Process Obligation
type: NamedIndividual
has applicability condition: ApplicabilityCondition
  at lifecycle stage: InceptionStage
  for risk level: RiskLevelHigh
  type: Applicability Condition
  for actor: AIProvider
comment: Providers established outside the EU must appoint an authorised representative by written mandate before placing a high-risk AI system on the EU market, as required by Article 22. Evidence of compliance is the ARMandateRecord held by the appointed representative.
pending article: Article 22

Guardrail
type: Class
comment: Monitors and constrains an agent's behaviour before, during or after it acts; can detect unsafe instructions, policy violations, or actions inconsistent with user intent.
subclass of: Agent Control

valid from
type: DatatypeProperty
range: dateTime
domain: Delegation of Authority Record
comment: Start of the delegation's validity window. Authorisations should be time- or session-bound (MGF §2.1.2).

Technical Trigger
comment: Model updates, tool modifications.
type: Change Trigger

review cadence
type: ObjectProperty

Education
notation: P
type: Economic Sector
comment: NACE Rev. 2 section P. For sector-specific purposes use sector-education: terms with dpv:hasPurpose.

for system type
domain: Applicability Condition
comment: The AI system type classification for which this condition applies (e.g., eu-aiact:BiometricCategorisationSystem, eu-aiact:EmotionRecognitionSystem, prism:ChatBot, prism:AIContentGenerator). Only present when the obligation is triggered by a specific system type. May reference prism-local types where eu-aiact has not yet modelled the concept.
type: ObjectProperty

External System Access
type: System Access Type
comment: Tools that reach external services, e.g. third-party APIs or the open web. Raises both impact (data can leak to third parties) and likelihood (exposure to prompt injection from untrusted content) of risks (MGF §2.1.1).

Infrastructure
type: Economic Sector
comment: NACE Rev. 2 sections D (Energy), E (Water/waste), F (Construction), H (Transport). For sector-specific purposes use sector-infra: terms with dpv:hasPurpose.
notation: F
notation: D
notation: H
notation: E

Critical Change
comment: Changes affecting high-stakes decisions; may mandate an immediate re-risk assessment.
type: Change Category

Conformity Assessment
occurs at stage: VerificationStage
type: Regulatory Process
comment: The AI Act procedure in which conformity is formally assessed, either through self-assessment (Module A) or third-party assessment for biometric and Annex I systems (Articles 43-44).
occurs at stage: ValidationStage
type: NamedIndividual

Performance Trigger
comment: Anomalous behaviour, degraded performance.
type: Change Trigger

Importer Contact Information
has applicability condition: ApplicabilityCondition
  for risk level: RiskLevelHigh
  at lifecycle stage: DeploymentStage
  type: Applicability Condition
  for actor: AIImporter
pending article: Article 23(3)
type: Process Obligation
type: NamedIndividual
comment: Importer must indicate their name, registered trade name or registered trade mark, and the address at which they can be contacted on the AI system or its packaging, as required by Article 23(3).

AI Content Generator
type: Class
comment: An AI system that generates synthetic images, audio, video, or text. Providers must label AI-generated content (deepfakes) under Article 50(3), and AI-generated text on matters of public interest under Article 50(4). Pending eu-aiact modelling of this system type.

Agent Collusion
subclass of: Agentic Risk
comment: Agents developing behaviours that appear coordinated without explicit instruction, e.g. pricing agents converging on higher prices rather than competing.
type: Class

Process Obligation
type: Class
comment: An EU AI Act obligation that is behavioural or operational in nature and does not produce a standalone compliance record. Tracked for completeness and queryability. Evidence of compliance is typically subsumed by the Quality Management System or demonstrated through operational procedures.

Change Trigger
type: Class
comment: The kind of event that initiates a change review (MGF §2.3.3).

Deemed Provider Obligation
has applicability condition: ApplicabilityCondition
  type: Applicability Condition
  for risk level: RiskLevelHigh
  for actor: AuthorisedRepresentative
  for actor: AIDistributor
  for actor: AIImporter
type: Process Obligation
type: NamedIndividual
comment: Where an importer, distributor, or authorised representative places an AI system on the market under their own name or trade mark, or makes a substantial modification, they assume full provider obligations under Chapter 3, as required by Article 25(1). This is a role transition trigger, not a standalone record.
pending article: Article 25(1)

Supervisor Architecture
type: Agent Architecture
comment: One supervising agent coordinates specialised agents under it, calling specific agents as tools when required.

Action Scope
type: Class
comment: Whether the agent can only read from, or can also modify, the systems it has access to (MGF §1.1.3).

Tool Calling Accuracy
comment: Whether the agent calls the right tools, with the right permissions, with the right inputs, in the right order.
type: Testing Dimension

Agent Conflict
type: Class
subclass of: Agentic Risk
comment: Agents optimising different goals coming into conflict, e.g. a support agent offering refunds a revenue-protection agent blocks.

Read-Write Scope
comment: The agent may write to and modify data in the system. Consider the reversibility of those modifications when assessing impact (MGF §2.1.1).
type: Action Scope

Control Layer
comment: The layer at which a control is enforced (MGF §2.3.1). Structural controls are deterministic and cannot be bypassed by the model; prompt-layer controls are inconsistently defined across users and may be bypassed or forgotten.
type: Class

Prompt Layer
type: Control Layer
comment: Enforcement via instructions in the agent's prompt. Weakest layer: may be bypassed or inconsistently applied; avoid as the sole control for higher-risk actions.

Policy Adherence
comment: Whether the agent follows defined SOPs and routes for human approval when required.
type: Testing Dimension

Attested
type: Attestation Status
comment: Reviewed and signed off by a named individual. Only attested records count as evidential coverage in gap analysis.

Authorised Representative Cooperation with Authorities
pending article: Article 22(3)(c)
comment: Authorised representative must cooperate with competent authorities upon reasoned request and carry out tasks to ensure compliance, as required by Article 22(3)(c).
has applicability condition: ApplicabilityCondition
  type: Applicability Condition
  for risk level: RiskLevelHigh
  for actor: AuthorisedRepresentative
type: Process Obligation
type: NamedIndividual

Candidate
type: Attestation Status
comment: Extracted by the AI connector but not yet reviewed. Does not count as evidential coverage.

Attestation Status
comment: The lifecycle status of a compliance record — Candidate (AI-extracted, unreviewed) or Attested (reviewed and signed off by a named individual).
type: Class

Minor Change
type: Change Category
comment: E.g. prompt refinements; follows a lighter review process.

Regulatory Process
type: Class
comment: An AI Act-specific procedure that occurs at one or more AI lifecycle stages. Not a lifecycle stage itself.

Agent Operates, Human Observes
type: Autonomy Level
comment: The agent does not require human approval as it completes its task; its actions may be audited after the fact.