OpenChainGraph Suite · CONTRACT A3 · arch #5

AI Agent Incident Across Regimes

A seven-stage review of one caller-declared agent incident across three regulatory regimes. Step 1 composes a structured incident record from the declared agent identity, incident description with its severity class, session evidence digests and remediation status (art-379). Step 2 then classifies the autonomy tier and the in-force AI Act obligations the declared deployment carries (art-67). Step 3 then applies the DORA major-incident numeric criteria to the declared impact figures and reports a major or non-major classification with the reporting clock a major finding starts (art-467). Step 4 then scores the declared disruption, affected-user and loss figures against the NIS2 significance criteria and reports a significance verdict (art-144). Step 5 then starts the clock obligations for the regimes the caller declares applicable from one determination timestamp (art-428). Step 6 then builds the post-market monitoring, logging and oversight plan for the declared high-risk deployment as a decision-support draft (art-66). Step 7 then validates the declared agent audit-trail records and returns a conformance result (art-237). Each step computes from its own declared inputs; the order is a review sequence, not a statutory one, and the chain determines no reporting obligation.

OpenChainGraph · 7 Steps compliance mandate Hash-Anchored §4 chain_depth:7 Client-Side · Zero PII
Chain Topology: Agent Incident Record Composer → Agentic AI Risk & GPAI Governance Classifier → DORA ICT Incident Classifier & Reporting Clock → NIS2 Incident Significance Scorer (Art. 23 Reporting Threshold) → Cyber Incident Notification Clock → FRIA & Post-Market Monitoring Plan Builder → Agent Audit Trail Conformance Validator (IETF AAT)
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 7 Steps
1 ROOT node
Agent Incident Record Composer art-379-agent-incident-record-composer
Composes a structured incident record from the declared agent identity, incident description with its severity class, session evidence digests and remediation status, degrading claim strength when identity is missing and flagging a malformed cross-link rather than hiding it; step 2 then classifies the agentic-AI risk the declared deployment carries. Stage 1 of 7.
MCP Call · build_agent_incident_record
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "build_agent_incident_record",
    "arguments": {}
  },
  "id": 1
}
↓
2 STAGE 2 node
Agentic AI Risk & GPAI Governance Classifier art-67-agentic-ai-risk-classifier
Classifies the autonomy tier and the in-force AI Act obligations the declared deployment carries, mapping transparency, literacy, oversight and systemic-risk duties; step 3 then applies the DORA major-incident criteria to the declared impact figures. Stage 2 of 7.
MCP Call · classify_agentic_ai_risk
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "classify_agentic_ai_risk",
    "arguments": {}
  },
  "id": 1
}
↓
3 STAGE 3 node
DORA ICT Incident Classifier & Reporting Clock art-467-dora-incident-classifier
Applies the DORA Art. 18 numeric criteria over clients affected, duration, geographical spread, data losses, economic impact, critical services and reputational impact to the declared figures and reports a major or non-major classification with the reporting clock a major finding starts; step 4 then scores the same incident against the NIS2 significance criteria. Stage 3 of 7.
MCP Call · classify_dora_ict_incident_and_clock_deadlines
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "classify_dora_ict_incident_and_clock_deadlines",
    "arguments": {}
  },
  "id": 1
}
↓
4 STAGE 4 node
NIS2 Incident Significance Scorer (Art. 23 Reporting Threshold) art-144-nis2-incident-significance-scorer
Scores the declared disruption, affected-user and loss figures against the NIS2 significance criteria and reports a significance verdict with the authorities it names; step 5 then starts the clock obligations for the regimes the caller declares applicable. Stage 4 of 7.
MCP Call · score_nis2_incident_significance
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "score_nis2_incident_significance",
    "arguments": {}
  },
  "id": 1
}
↓
5 STAGE 5 node
Cyber Incident Notification Clock art-428-cyber-incident-clock
Starts the clock obligations for the regimes the caller declares applicable from one hash-anchored determination timestamp, giving each obligation its own attestation slot and stable obligation id; step 6 then builds the post-market monitoring plan for the declared deployment. Stage 5 of 7.
MCP Call · compute_cyber_incident_notification_clock
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "compute_cyber_incident_notification_clock",
    "arguments": {}
  },
  "id": 1
}
↓
6 STAGE 6 node
FRIA & Post-Market Monitoring Plan Builder art-66-fria-postmarket-monitoring-builder
Builds the post-market monitoring, logging, human-oversight and serious-incident reporting path plan for the declared high-risk deployment as a decision-support draft; step 7 then validates the declared audit-trail records. Stage 6 of 7.
MCP Call · build_fria_monitoring_plan
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "build_fria_monitoring_plan",
    "arguments": {}
  },
  "id": 1
}
↓
7 TERMINAL node
Agent Audit Trail Conformance Validator (IETF AAT) art-237-validate-agent-audit-trail
Validates the declared agent audit-trail records, checking required fields, chain-link format, signature presence and enum conformance, and returns a conformance result with a completeness score. Final stage.
MCP Call · validate_agent_audit_trail
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_agent_audit_trail",
    "arguments": {}
  },
  "id": 1
}
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition. Available after hash computation.

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.

Question: An agent outage disrupted service for four hours and hit 5,000 users. Does the NIS2 scorer call the incident significant, and do reporting clocks start?
Run the AINumbers MCP tool `run_chain` with {"chain":"ai-agent-incident-multi-regime"} and read `art-144-nis2-incident-significance-scorer.significance_verdict`.
Re-run with `inputs` for `art-144-nis2-incident-significance-scorer`, reusing the values that result echoed, with `service_disruption_hours` set to 0.5. Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/ai-agent-incident-multi-regime.html