# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T12:23:06Z", "synthesisSha256": "ab1383a7360c2b19f1f6402abdb7b6a58c4e179b878f9c53faf93066c7ae7283", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-AI-010", "registryId": "vr.wm-ai-010", "name": "AI Incident Report", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Information and virtual systems", "industry": [ "Cross-industry" ], "domain": [ "INF.AI.INC" ], "tags": [ "ai", "incident", "report", "inf.ai.inc" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-ai-010-ai-incident-report/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/publications/wm-ai-010-ai-incident-report", "model": { "registry_id": "vr.wm-ai-010", "model_id": "WM-AI-010", "name": "AI Incident Report", "entry_kind": "aggregate", "purpose": "Represent one governed, versioned AI incident reporting case that makes facts, timeline, affected systems, classification, impact, causal assessments, response, obligations, submissions and corrections machine-readable without absorbing the incident or authority masters.", "scope_statement": "Owns report-case identity, version and status; issuer, jurisdiction, legal basis, recipient and reportability assertions; incident, affected-system and party bindings; facts, timeline, context, classification, severity, impact, harm, causal, security and privacy assessments; response and remediation summaries; notification duties, deadlines, submissions, receipts and authority exchanges; approval, confidentiality, communication, evidence, correction, retention, audit and projections. Incident, AI system, model, deployment, investigation, regulatory case, remediation work, harm, vulnerability, evidence, audit and records masters remain external.", "in_scope": [ "Report identity, version, jurisdiction, legal basis, recipient, affected systems, responsible parties, facts, timeline, context, classification, severity, impact and causal assessments", "Security and privacy links, response and remediation summaries, obligations, deadlines, submissions, receipts, authority exchanges, disclosure, lifecycle, evidence, retention, audit and projections" ], "out_of_scope": [ "Owning the incident, affected AI system, model, deployment, person, organization, harm, investigation, regulatory case, remediation action, vulnerability, evidence, audit or records masters", "Treating report receipt, mitigation deployment, system recovery or closure as proof of causality, acceptance, effectiveness, compliance or absence of harm", "Autonomous legal classification, regulatory submission, public disclosure, liability admission, attribution, access expansion, evidence destruction or closure" ], "boundary_notes": [ { "neighbor": "WM-AI-001 AI System", "distinction": "The unified parent signal and candidate reference identify affected-system context but grant no inheritance or ownership. The report binds source-qualified system, model and deployment versions without mutating their masters.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-007" ] }, { "neighbor": "WM-ACT-019 Incident", "distinction": "The general incident master owns occurrence, operational state and response history. The report owns a versioned communication and submission case about that incident.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008", "SRC-012" ] }, { "neighbor": "Investigation, remediation and regulatory case", "distinction": "Investigations own methods and findings, remediation work owns actions and verification, and authorities own their cases and decisions. The report stores non-owning summaries, submissions, receipts and exchanges.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008", "SRC-014" ] }, { "neighbor": "Security incident and personal-data breach", "distinction": "Cybersecurity and privacy regimes may overlap an AI incident but use independent applicability, risk, notification and authority semantics.", "source_refs": [ "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012" ] }, { "neighbor": "EU AI Act, OECD, NIST, FIRST, ISO, PROV and RFC profiles", "distinction": "These legal, reporting, risk, incident-response, management, provenance and timestamp sources have distinct scopes. No mapping is assumed binding or lossless outside its profile.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Regulation (EU) 2024/1689 Artificial Intelligence Act, consolidated text", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/reg/2024/1689/2026-07-27/eng", "version_or_date": "Consolidated 27 July 2026", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T12:19:00Z", "relevance": "Defines serious incident and jurisdiction-qualified reporting, timing, investigation and corrective-action duties." }, { "id": "SRC-002", "title": "Draft guidance and reporting template on serious AI incidents", "organization": "European Commission", "url": "https://digital-strategy.ec.europa.eu/en/consultations/ai-act-commission-issues-draft-guidance-and-reporting-template-serious-ai-incidents-and-seeks", "version_or_date": "Consultation package 26 September 2025; draft at access", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T12:19:00Z", "relevance": "Provides a non-final Article 73 guidance and high-risk-system report-template profile." }, { "id": "SRC-003", "title": "Defining AI incidents and related terms", "organization": "Organisation for Economic Co-operation and Development", "url": "https://www.oecd.org/en/publications/defining-ai-incidents-and-related-terms_d1a8d965-en.html", "version_or_date": "OECD AI Paper 16, 6 May 2024", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T12:19:00Z", "relevance": "Distinguishes actual-harm incidents from potential-harm hazards and supports interoperable terminology." }, { "id": "SRC-004", "title": "Towards a common reporting framework for AI incidents", "organization": "Organisation for Economic Co-operation and Development", "url": "https://www.oecd.org/en/publications/towards-a-common-reporting-framework-for-ai-incidents_f326d4ac-en.html", "version_or_date": "OECD AI Paper 34, 28 February 2025", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T12:19:00Z", "relevance": "Provides 29 common reporting criteria with jurisdictional and sectoral tailoring." }, { "id": "SRC-005", "title": "AI Incidents and Hazards Monitor", "organization": "Organisation for Economic Co-operation and Development", "url": "https://oecd.ai/en/incidents/", "version_or_date": "Beta monitor current at access", "source_type": "registry", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T12:19:00Z", "relevance": "Provides a public-source incident and hazard observation profile, not authoritative findings." }, { "id": "SRC-006", "title": "Artificial Intelligence Risk Management Framework (AI RMF 1.0)", "organization": "National Institute of Standards and Technology", "url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10", "version_or_date": "NIST AI 100-1, 26 January 2023; revision in progress", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T12:19:00Z", "relevance": "Frames AI governance, measurement, risk response, monitoring and documentation." }, { "id": "SRC-007", "title": "Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile", "organization": "National Institute of Standards and Technology", "url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence", "version_or_date": "NIST AI 600-1, July 2024", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T12:19:00Z", "relevance": "Adds GenAI incident, provenance, misuse, privacy, security and disclosure considerations." }, { "id": "SRC-008", "title": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management", "organization": "National Institute of Standards and Technology", "url": "https://csrc.nist.gov/pubs/sp/800/61/r3/final", "version_or_date": "NIST SP 800-61 Revision 3, April 2025", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T12:19:00Z", "relevance": "Provides preparation, detection, response, recovery, communication and improvement context." }, { "id": "SRC-009", "title": "Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations", "organization": "National Institute of Standards and Technology", "url": "https://www.nist.gov/publications/adversarial-machine-learning-taxonomy-and-terminology-attacks-and-mitigations-0", "version_or_date": "NIST AI 100-2e2025, March 2025", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T12:19:00Z", "relevance": "Provides terminology for poisoning, evasion, privacy and misuse attacks." }, { "id": "SRC-010", "title": "Regulation (EU) 2016/679 General Data Protection Regulation", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/reg/2016/679/oj", "version_or_date": "27 April 2016; applicable from 25 May 2018", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T12:19:00Z", "relevance": "Provides an EU profile for personal-data breach documentation, authority notification and affected-person communication." }, { "id": "SRC-011", "title": "Guidelines 9/2022 on personal data breach notification under GDPR", "organization": "European Data Protection Board", "url": "https://www.edpb.europa.eu/our-work-tools/our-documents/guidelines/guidelines-92022-personal-data-breach-notification-under_en", "version_or_date": "Final version 2.0, adopted 28 March 2023", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T12:19:00Z", "relevance": "Clarifies EU personal-data breach detection, documentation, risk assessment and notification." }, { "id": "SRC-012", "title": "CSIRT Services Framework", "organization": "Forum of Incident Response and Security Teams", "url": "https://www.first.org/standards/frameworks/csirts/csirt_services_framework_v2.1", "version_or_date": "Version 2.1", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T12:19:00Z", "relevance": "Defines technology-neutral incident-management services, functions, roles and outcomes." }, { "id": "SRC-013", "title": "ISO/IEC 42001 AI management systems", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/42001", "version_or_date": "ISO/IEC 42001:2023 public catalogue metadata only", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T12:19:00Z", "relevance": "Supports management-system governance, traceability and continual improvement without inferring access-restricted clauses." }, { "id": "SRC-014", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T12:19:00Z", "relevance": "Defines entity, activity, agent, attribution, derivation, revision and time for report provenance." }, { "id": "SRC-015", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/info/rfc3339/", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T12:19:00Z", "relevance": "Defines interoperable timestamps with seconds and explicit UTC relationship." } ], "structure": { "bundles": [ { "id": "report-identity-scope-jurisdiction-and-parties", "name": "Report identity, scope, jurisdiction and parties", "description": "Groups governed report context for report identity, scope, jurisdiction and parties.", "rationale": "The reporting-case record is distinct from the incident and every authority case.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-014" ], "layers": [ { "id": "report-root-version-status-and-authority", "name": "Report root, version, status and authority", "description": "Groups source-qualified report context for report root, version, status and authority.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-014" ], "findings": [ { "id": "report-case-identity-type-version-issuer-and-current-head", "name": "Report case identity, type, version, issuer and current head", "description": "Records report case identity, type, version, issuer and current head as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-014" ], "questions": [ { "id": "report-case-identity-type-version-issuer-and-current-head-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish report case identity, type, version, issuer and current head?", "kind": "identity", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "report-case-identity-type-version-issuer-and-current-head-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on report case identity, type, version, issuer and current head, under which authority and limits?", "kind": "event", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "report-case-identity-type-version-issuer-and-current-head-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify report case identity, type, version, issuer and current head?", "kind": "process", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "report-case-identity-type-version-issuer-and-current-head-data", "name": "Report case identity, type, version, issuer and current head data", "description": "Typed incident-report data for report case identity, type, version, issuer and current head, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-014" ] } ], "artifacts": [ { "id": "report-case-identity-type-version-issuer-and-current-head-record", "name": "Report case identity, type, version, issuer and current head record", "description": "Immutable or successor-versioned report evidence for report case identity, type, version, issuer and current head.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for report-case-identity-type-version-issuer-and-current-head; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "jurisdiction-legal-basis-recipient-reportability-and-authority", "name": "Jurisdiction, legal basis, recipient, reportability and authority", "description": "Records jurisdiction, legal basis, recipient, reportability and authority as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-014" ], "questions": [ { "id": "jurisdiction-legal-basis-recipient-reportability-and-authority-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish jurisdiction, legal basis, recipient, reportability and authority?", "kind": "authority", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "jurisdiction-legal-basis-recipient-reportability-and-authority-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on jurisdiction, legal basis, recipient, reportability and authority, under which authority and limits?", "kind": "temporal", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "jurisdiction-legal-basis-recipient-reportability-and-authority-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify jurisdiction, legal basis, recipient, reportability and authority?", "kind": "validation", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "jurisdiction-legal-basis-recipient-reportability-and-authority-data", "name": "Jurisdiction, legal basis, recipient, reportability and authority data", "description": "Typed incident-report data for jurisdiction, legal basis, recipient, reportability and authority, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-014" ] } ], "artifacts": [ { "id": "jurisdiction-legal-basis-recipient-reportability-and-authority-record", "name": "Jurisdiction, legal basis, recipient, reportability and authority record", "description": "Immutable or successor-versioned report evidence for jurisdiction, legal basis, recipient, reportability and authority.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for jurisdiction-legal-basis-recipient-reportability-and-authority; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-014" ] } ], "inline_only_rationale": null } ] }, { "id": "incident-system-and-party-bindings", "name": "Incident, system and party bindings", "description": "Groups source-qualified report context for incident, system and party bindings.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "incident-related-report-affected-system-deployment-model-and-version", "name": "Incident, related report, affected system, deployment, model and version", "description": "Records incident, related report, affected system, deployment, model and version as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "incident-related-report-affected-system-deployment-model-and-version-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish incident, related report, affected system, deployment, model and version?", "kind": "relationship", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "incident-related-report-affected-system-deployment-model-and-version-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on incident, related report, affected system, deployment, model and version, under which authority and limits?", "kind": "composition", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "incident-related-report-affected-system-deployment-model-and-version-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify incident, related report, affected system, deployment, model and version?", "kind": "privacy", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "incident-related-report-affected-system-deployment-model-and-version-data", "name": "Incident, related report, affected system, deployment, model and version data", "description": "Typed incident-report data for incident, related report, affected system, deployment, model and version, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "incident-related-report-affected-system-deployment-model-and-version-record", "name": "Incident, related report, affected system, deployment, model and version record", "description": "Immutable or successor-versioned report evidence for incident, related report, affected system, deployment, model and version.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for incident-related-report-affected-system-deployment-model-and-version; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "reporter-provider-deployer-operator-contact-and-responsibility", "name": "Reporter, provider, deployer, operator, contact and responsibility", "description": "Records reporter, provider, deployer, operator, contact and responsibility as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "reporter-provider-deployer-operator-contact-and-responsibility-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish reporter, provider, deployer, operator, contact and responsibility?", "kind": "ownership", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "reporter-provider-deployer-operator-contact-and-responsibility-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on reporter, provider, deployer, operator, contact and responsibility, under which authority and limits?", "kind": "evidence", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "reporter-provider-deployer-operator-contact-and-responsibility-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify reporter, provider, deployer, operator, contact and responsibility?", "kind": "lifecycle", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "reporter-provider-deployer-operator-contact-and-responsibility-data", "name": "Reporter, provider, deployer, operator, contact and responsibility data", "description": "Typed incident-report data for reporter, provider, deployer, operator, contact and responsibility, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "reporter-provider-deployer-operator-contact-and-responsibility-record", "name": "Reporter, provider, deployer, operator, contact and responsibility record", "description": "Immutable or successor-versioned report evidence for reporter, provider, deployer, operator, contact and responsibility.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for reporter-provider-deployer-operator-contact-and-responsibility; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "occurrence-observation-context-and-timeline", "name": "Occurrence, observation, context and timeline", "description": "Groups governed report context for occurrence, observation, context and timeline.", "rationale": "Source-qualified observations preserve what happened and when it became known.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015" ], "layers": [ { "id": "event-clock-location-and-evidence-source", "name": "Event clock, location and evidence source", "description": "Groups source-qualified report context for event clock, location and evidence source.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-015" ], "findings": [ { "id": "occurrence-detection-discovery-awareness-notification-and-report-time", "name": "Occurrence, detection, discovery, awareness, notification and report time", "description": "Records occurrence, detection, discovery, awareness, notification and report time as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-015" ], "questions": [ { "id": "occurrence-detection-discovery-awareness-notification-and-report-time-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish occurrence, detection, discovery, awareness, notification and report time?", "kind": "temporal", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "occurrence-detection-discovery-awareness-notification-and-report-time-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on occurrence, detection, discovery, awareness, notification and report time, under which authority and limits?", "kind": "ownership", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "occurrence-detection-discovery-awareness-notification-and-report-time-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify occurrence, detection, discovery, awareness, notification and report time?", "kind": "quality", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "occurrence-detection-discovery-awareness-notification-and-report-time-data", "name": "Occurrence, detection, discovery, awareness, notification and report time data", "description": "Typed incident-report data for occurrence, detection, discovery, awareness, notification and report time, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-015" ] } ], "artifacts": [ { "id": "occurrence-detection-discovery-awareness-notification-and-report-time-record", "name": "Occurrence, detection, discovery, awareness, notification and report time record", "description": "Immutable or successor-versioned report evidence for occurrence, detection, discovery, awareness, notification and report time.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for occurrence-detection-discovery-awareness-notification-and-report-time; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "location-channel-source-observer-confidence-gap-and-unavailability", "name": "Location, channel, source, observer, confidence, gap and unavailability", "description": "Records location, channel, source, observer, confidence, gap and unavailability as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-015" ], "questions": [ { "id": "location-channel-source-observer-confidence-gap-and-unavailability-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish location, channel, source, observer, confidence, gap and unavailability?", "kind": "evidence", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "location-channel-source-observer-confidence-gap-and-unavailability-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on location, channel, source, observer, confidence, gap and unavailability, under which authority and limits?", "kind": "measurement", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "location-channel-source-observer-confidence-gap-and-unavailability-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify location, channel, source, observer, confidence, gap and unavailability?", "kind": "security", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "location-channel-source-observer-confidence-gap-and-unavailability-data", "name": "Location, channel, source, observer, confidence, gap and unavailability data", "description": "Typed incident-report data for location, channel, source, observer, confidence, gap and unavailability, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-015" ] } ], "artifacts": [ { "id": "location-channel-source-observer-confidence-gap-and-unavailability-record", "name": "Location, channel, source, observer, confidence, gap and unavailability record", "description": "Immutable or successor-versioned report evidence for location, channel, source, observer, confidence, gap and unavailability.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for location-channel-source-observer-confidence-gap-and-unavailability; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-015" ] } ], "inline_only_rationale": null } ] }, { "id": "behavior-sequence-and-operating-context", "name": "Behavior, sequence and operating context", "description": "Groups source-qualified report context for behavior, sequence and operating context.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ], "findings": [ { "id": "behavior-failure-malfunction-output-action-outcome-and-sequence", "name": "Behavior, failure, malfunction, output, action, outcome and sequence", "description": "Records behavior, failure, malfunction, output, action, outcome and sequence as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ], "questions": [ { "id": "behavior-failure-malfunction-output-action-outcome-and-sequence-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish behavior, failure, malfunction, output, action, outcome and sequence?", "kind": "event", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "behavior-failure-malfunction-output-action-outcome-and-sequence-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on behavior, failure, malfunction, output, action, outcome and sequence, under which authority and limits?", "kind": "exception", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "behavior-failure-malfunction-output-action-outcome-and-sequence-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify behavior, failure, malfunction, output, action, outcome and sequence?", "kind": "retention", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "behavior-failure-malfunction-output-action-outcome-and-sequence-data", "name": "Behavior, failure, malfunction, output, action, outcome and sequence data", "description": "Typed incident-report data for behavior, failure, malfunction, output, action, outcome and sequence, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "behavior-failure-malfunction-output-action-outcome-and-sequence-record", "name": "Behavior, failure, malfunction, output, action, outcome and sequence record", "description": "Immutable or successor-versioned report evidence for behavior, failure, malfunction, output, action, outcome and sequence.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for behavior-failure-malfunction-output-action-outcome-and-sequence; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "lifecycle-stage-environment-data-input-output-human-and-tool-context", "name": "Lifecycle stage, environment, data, input, output, human and tool context", "description": "Records lifecycle stage, environment, data, input, output, human and tool context as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ], "questions": [ { "id": "lifecycle-stage-environment-data-input-output-human-and-tool-context-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish lifecycle stage, environment, data, input, output, human and tool context?", "kind": "composition", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "lifecycle-stage-environment-data-input-output-human-and-tool-context-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on lifecycle stage, environment, data, input, output, human and tool context, under which authority and limits?", "kind": "provenance", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "lifecycle-stage-environment-data-input-output-human-and-tool-context-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify lifecycle stage, environment, data, input, output, human and tool context?", "kind": "interoperability", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "lifecycle-stage-environment-data-input-output-human-and-tool-context-data", "name": "Lifecycle stage, environment, data, input, output, human and tool context data", "description": "Typed incident-report data for lifecycle stage, environment, data, input, output, human and tool context, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "lifecycle-stage-environment-data-input-output-human-and-tool-context-record", "name": "Lifecycle stage, environment, data, input, output, human and tool context record", "description": "Immutable or successor-versioned report evidence for lifecycle stage, environment, data, input, output, human and tool context.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for lifecycle-stage-environment-data-input-output-human-and-tool-context; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "classification-severity-impact-and-harm", "name": "Classification, severity, impact and harm", "description": "Groups governed report context for classification, severity, impact and harm.", "rationale": "Classifications remain regime-qualified assessments rather than universal legal findings.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-010", "SRC-011" ], "layers": [ { "id": "incident-class-severity-and-causal-threshold", "name": "Incident class, severity and causal threshold", "description": "Groups source-qualified report context for incident class, severity and causal threshold.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005" ], "findings": [ { "id": "incident-hazard-near-miss-serious-criterion-category-and-severity", "name": "Incident, hazard, near miss, serious criterion, category and severity", "description": "Records incident, hazard, near miss, serious criterion, category and severity as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005" ], "questions": [ { "id": "incident-hazard-near-miss-serious-criterion-category-and-severity-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish incident, hazard, near miss, serious criterion, category and severity?", "kind": "classification", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "incident-hazard-near-miss-serious-criterion-category-and-severity-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on incident, hazard, near miss, serious criterion, category and severity, under which authority and limits?", "kind": "process", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "incident-hazard-near-miss-serious-criterion-category-and-severity-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify incident, hazard, near miss, serious criterion, category and severity?", "kind": "decision", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "incident-hazard-near-miss-serious-criterion-category-and-severity-data", "name": "Incident, hazard, near miss, serious criterion, category and severity data", "description": "Typed incident-report data for incident, hazard, near miss, serious criterion, category and severity, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "incident-hazard-near-miss-serious-criterion-category-and-severity-record", "name": "Incident, hazard, near miss, serious criterion, category and severity record", "description": "Immutable or successor-versioned report evidence for incident, hazard, near miss, serious criterion, category and severity.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for incident-hazard-near-miss-serious-criterion-category-and-severity; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null }, { "id": "causal-link-likelihood-attribution-scope-confidence-and-uncertainty", "name": "Causal link, likelihood, attribution, scope, confidence and uncertainty", "description": "Records causal link, likelihood, attribution, scope, confidence and uncertainty as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005" ], "questions": [ { "id": "causal-link-likelihood-attribution-scope-confidence-and-uncertainty-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish causal link, likelihood, attribution, scope, confidence and uncertainty?", "kind": "decision", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "causal-link-likelihood-attribution-scope-confidence-and-uncertainty-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on causal link, likelihood, attribution, scope, confidence and uncertainty, under which authority and limits?", "kind": "validation", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "causal-link-likelihood-attribution-scope-confidence-and-uncertainty-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify causal link, likelihood, attribution, scope, confidence and uncertainty?", "kind": "state", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "causal-link-likelihood-attribution-scope-confidence-and-uncertainty-data", "name": "Causal link, likelihood, attribution, scope, confidence and uncertainty data", "description": "Typed incident-report data for causal link, likelihood, attribution, scope, confidence and uncertainty, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "causal-link-likelihood-attribution-scope-confidence-and-uncertainty-record", "name": "Causal link, likelihood, attribution, scope, confidence and uncertainty record", "description": "Immutable or successor-versioned report evidence for causal link, likelihood, attribution, scope, confidence and uncertainty.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for causal-link-likelihood-attribution-scope-confidence-and-uncertainty; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "affected-subjects-rights-assets-and-consequences", "name": "Affected subjects, rights, assets and consequences", "description": "Groups source-qualified report context for affected subjects, rights, assets and consequences.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-011" ], "findings": [ { "id": "person-group-right-health-safety-property-infrastructure-and-environment", "name": "Person, group, right, health, safety, property, infrastructure and environment", "description": "Records person, group, right, health, safety, property, infrastructure and environment as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-011" ], "questions": [ { "id": "person-group-right-health-safety-property-infrastructure-and-environment-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish person, group, right, health, safety, property, infrastructure and environment?", "kind": "measurement", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "person-group-right-health-safety-property-infrastructure-and-environment-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on person, group, right, health, safety, property, infrastructure and environment, under which authority and limits?", "kind": "privacy", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "person-group-right-health-safety-property-infrastructure-and-environment-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify person, group, right, health, safety, property, infrastructure and environment?", "kind": "identity", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "person-group-right-health-safety-property-infrastructure-and-environment-data", "name": "Person, group, right, health, safety, property, infrastructure and environment data", "description": "Typed incident-report data for person, group, right, health, safety, property, infrastructure and environment, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "person-group-right-health-safety-property-infrastructure-and-environment-record", "name": "Person, group, right, health, safety, property, infrastructure and environment record", "description": "Immutable or successor-versioned report evidence for person, group, right, health, safety, property, infrastructure and environment.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for person-group-right-health-safety-property-infrastructure-and-environment; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "geography-system-service-scale-duration-persistence-and-reversibility", "name": "Geography, system, service, scale, duration, persistence and reversibility", "description": "Records geography, system, service, scale, duration, persistence and reversibility as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-011" ], "questions": [ { "id": "geography-system-service-scale-duration-persistence-and-reversibility-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish geography, system, service, scale, duration, persistence and reversibility?", "kind": "measurement", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "geography-system-service-scale-duration-persistence-and-reversibility-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on geography, system, service, scale, duration, persistence and reversibility, under which authority and limits?", "kind": "lifecycle", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "geography-system-service-scale-duration-persistence-and-reversibility-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify geography, system, service, scale, duration, persistence and reversibility?", "kind": "classification", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "geography-system-service-scale-duration-persistence-and-reversibility-data", "name": "Geography, system, service, scale, duration, persistence and reversibility data", "description": "Typed incident-report data for geography, system, service, scale, duration, persistence and reversibility, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "geography-system-service-scale-duration-persistence-and-reversibility-record", "name": "Geography, system, service, scale, duration, persistence and reversibility record", "description": "Immutable or successor-versioned report evidence for geography, system, service, scale, duration, persistence and reversibility.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for geography-system-service-scale-duration-persistence-and-reversibility; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "cause-security-privacy-investigation-and-evidence", "name": "Cause, security, privacy, investigation and evidence", "description": "Groups governed report context for cause, security, privacy, investigation and evidence.", "rationale": "Causal and control claims preserve hypotheses, evidence and independent authority.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014" ], "layers": [ { "id": "cause-contributor-investigation-and-assessment", "name": "Cause, contributor, investigation and assessment", "description": "Groups source-qualified report context for cause, contributor, investigation and assessment.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-013", "SRC-014" ], "findings": [ { "id": "model-data-software-hardware-supplier-human-process-and-organization-factor", "name": "Model, data, software, hardware, supplier, human, process and organization factor", "description": "Records model, data, software, hardware, supplier, human, process and organization factor as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-013", "SRC-014" ], "questions": [ { "id": "model-data-software-hardware-supplier-human-process-and-organization-factor-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish model, data, software, hardware, supplier, human, process and organization factor?", "kind": "provenance", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "model-data-software-hardware-supplier-human-process-and-organization-factor-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on model, data, software, hardware, supplier, human, process and organization factor, under which authority and limits?", "kind": "quality", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "model-data-software-hardware-supplier-human-process-and-organization-factor-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify model, data, software, hardware, supplier, human, process and organization factor?", "kind": "relationship", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "model-data-software-hardware-supplier-human-process-and-organization-factor-data", "name": "Model, data, software, hardware, supplier, human, process and organization factor data", "description": "Typed incident-report data for model, data, software, hardware, supplier, human, process and organization factor, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-013", "SRC-014" ] } ], "artifacts": [ { "id": "model-data-software-hardware-supplier-human-process-and-organization-factor-record", "name": "Model, data, software, hardware, supplier, human, process and organization factor record", "description": "Immutable or successor-versioned report evidence for model, data, software, hardware, supplier, human, process and organization factor.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for model-data-software-hardware-supplier-human-process-and-organization-factor; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-013", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "root-contributing-factor-hypothesis-investigation-method-finding-and-review", "name": "Root or contributing factor, hypothesis, investigation method, finding and review", "description": "Records root or contributing factor, hypothesis, investigation method, finding and review as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-013", "SRC-014" ], "questions": [ { "id": "root-contributing-factor-hypothesis-investigation-method-finding-and-review-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish root or contributing factor, hypothesis, investigation method, finding and review?", "kind": "validation", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "root-contributing-factor-hypothesis-investigation-method-finding-and-review-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on root or contributing factor, hypothesis, investigation method, finding and review, under which authority and limits?", "kind": "security", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "root-contributing-factor-hypothesis-investigation-method-finding-and-review-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify root or contributing factor, hypothesis, investigation method, finding and review?", "kind": "authority", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "root-contributing-factor-hypothesis-investigation-method-finding-and-review-data", "name": "Root or contributing factor, hypothesis, investigation method, finding and review data", "description": "Typed incident-report data for root or contributing factor, hypothesis, investigation method, finding and review, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-013", "SRC-014" ] } ], "artifacts": [ { "id": "root-contributing-factor-hypothesis-investigation-method-finding-and-review-record", "name": "Root or contributing factor, hypothesis, investigation method, finding and review record", "description": "Immutable or successor-versioned report evidence for root or contributing factor, hypothesis, investigation method, finding and review.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for root-contributing-factor-hypothesis-investigation-method-finding-and-review; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-008", "SRC-013", "SRC-014" ] } ], "inline_only_rationale": null } ] }, { "id": "security-adversarial-and-personal-data-breach", "name": "Security, adversarial and personal-data breach", "description": "Groups source-qualified report context for security, adversarial and personal-data breach.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012" ], "findings": [ { "id": "threat-actor-vulnerability-attack-technique-poisoning-evasion-privacy-and-misuse", "name": "Threat actor, vulnerability, attack technique, poisoning, evasion, privacy and misuse", "description": "Records threat actor, vulnerability, attack technique, poisoning, evasion, privacy and misuse as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012" ], "questions": [ { "id": "threat-actor-vulnerability-attack-technique-poisoning-evasion-privacy-and-misuse-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish threat actor, vulnerability, attack technique, poisoning, evasion, privacy and misuse?", "kind": "security", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "threat-actor-vulnerability-attack-technique-poisoning-evasion-privacy-and-misuse-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on threat actor, vulnerability, attack technique, poisoning, evasion, privacy and misuse, under which authority and limits?", "kind": "retention", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "threat-actor-vulnerability-attack-technique-poisoning-evasion-privacy-and-misuse-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify threat actor, vulnerability, attack technique, poisoning, evasion, privacy and misuse?", "kind": "requirement", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "threat-actor-vulnerability-attack-technique-poisoning-evasion-privacy-and-misuse-data", "name": "Threat actor, vulnerability, attack technique, poisoning, evasion, privacy and misuse data", "description": "Typed incident-report data for threat actor, vulnerability, attack technique, poisoning, evasion, privacy and misuse, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012" ] } ], "artifacts": [ { "id": "threat-actor-vulnerability-attack-technique-poisoning-evasion-privacy-and-misuse-record", "name": "Threat actor, vulnerability, attack technique, poisoning, evasion, privacy and misuse record", "description": "Immutable or successor-versioned report evidence for threat actor, vulnerability, attack technique, poisoning, evasion, privacy and misuse.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for threat-actor-vulnerability-attack-technique-poisoning-evasion-privacy-and-misuse; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "personal-data-breach-confidentiality-integrity-availability-risk-and-notification", "name": "Personal-data breach, confidentiality, integrity, availability, risk and notification", "description": "Records personal-data breach, confidentiality, integrity, availability, risk and notification as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012" ], "questions": [ { "id": "personal-data-breach-confidentiality-integrity-availability-risk-and-notification-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish personal-data breach, confidentiality, integrity, availability, risk and notification?", "kind": "privacy", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "personal-data-breach-confidentiality-integrity-availability-risk-and-notification-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on personal-data breach, confidentiality, integrity, availability, risk and notification, under which authority and limits?", "kind": "interoperability", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "personal-data-breach-confidentiality-integrity-availability-risk-and-notification-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify personal-data breach, confidentiality, integrity, availability, risk and notification?", "kind": "constraint", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "personal-data-breach-confidentiality-integrity-availability-risk-and-notification-data", "name": "Personal-data breach, confidentiality, integrity, availability, risk and notification data", "description": "Typed incident-report data for personal-data breach, confidentiality, integrity, availability, risk and notification, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012" ] } ], "artifacts": [ { "id": "personal-data-breach-confidentiality-integrity-availability-risk-and-notification-record", "name": "Personal-data breach, confidentiality, integrity, availability, risk and notification record", "description": "Immutable or successor-versioned report evidence for personal-data breach, confidentiality, integrity, availability, risk and notification.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for personal-data-breach-confidentiality-integrity-availability-risk-and-notification; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "response-remediation-notification-and-authority-exchange", "name": "Response, remediation, notification and authority exchange", "description": "Groups governed report context for response, remediation, notification and authority exchange.", "rationale": "Operational response and reporting obligations keep separate ownership and states.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ], "layers": [ { "id": "containment-recovery-corrective-and-preventive-action", "name": "Containment, recovery, corrective and preventive action", "description": "Groups source-qualified report context for containment, recovery, corrective and preventive action.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-013" ], "findings": [ { "id": "immediate-containment-safeguard-continuity-recovery-and-residual-risk", "name": "Immediate containment, safeguard, continuity, recovery and residual risk", "description": "Records immediate containment, safeguard, continuity, recovery and residual risk as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-013" ], "questions": [ { "id": "immediate-containment-safeguard-continuity-recovery-and-residual-risk-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish immediate containment, safeguard, continuity, recovery and residual risk?", "kind": "process", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "immediate-containment-safeguard-continuity-recovery-and-residual-risk-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on immediate containment, safeguard, continuity, recovery and residual risk, under which authority and limits?", "kind": "decision", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "immediate-containment-safeguard-continuity-recovery-and-residual-risk-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify immediate containment, safeguard, continuity, recovery and residual risk?", "kind": "event", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "immediate-containment-safeguard-continuity-recovery-and-residual-risk-data", "name": "Immediate containment, safeguard, continuity, recovery and residual risk data", "description": "Typed incident-report data for immediate containment, safeguard, continuity, recovery and residual risk, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "immediate-containment-safeguard-continuity-recovery-and-residual-risk-record", "name": "Immediate containment, safeguard, continuity, recovery and residual risk record", "description": "Immutable or successor-versioned report evidence for immediate containment, safeguard, continuity, recovery and residual risk.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for immediate-containment-safeguard-continuity-recovery-and-residual-risk; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "corrective-preventive-action-owner-due-date-verification-and-effectiveness", "name": "Corrective or preventive action, owner, due date, verification and effectiveness", "description": "Records corrective or preventive action, owner, due date, verification and effectiveness as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-013" ], "questions": [ { "id": "corrective-preventive-action-owner-due-date-verification-and-effectiveness-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish corrective or preventive action, owner, due date, verification and effectiveness?", "kind": "lifecycle", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "corrective-preventive-action-owner-due-date-verification-and-effectiveness-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on corrective or preventive action, owner, due date, verification and effectiveness, under which authority and limits?", "kind": "state", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "corrective-preventive-action-owner-due-date-verification-and-effectiveness-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify corrective or preventive action, owner, due date, verification and effectiveness?", "kind": "temporal", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "corrective-preventive-action-owner-due-date-verification-and-effectiveness-data", "name": "Corrective or preventive action, owner, due date, verification and effectiveness data", "description": "Typed incident-report data for corrective or preventive action, owner, due date, verification and effectiveness, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "corrective-preventive-action-owner-due-date-verification-and-effectiveness-record", "name": "Corrective or preventive action, owner, due date, verification and effectiveness record", "description": "Immutable or successor-versioned report evidence for corrective or preventive action, owner, due date, verification and effectiveness.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for corrective-preventive-action-owner-due-date-verification-and-effectiveness; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null } ] }, { "id": "obligation-deadline-submission-and-authority-response", "name": "Obligation, deadline, submission and authority response", "description": "Groups source-qualified report context for obligation, deadline, submission and authority response.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-010", "SRC-011" ], "findings": [ { "id": "recipient-regime-trigger-awareness-clock-deadline-exception-and-extension", "name": "Recipient, regime, trigger, awareness clock, deadline, exception and extension", "description": "Records recipient, regime, trigger, awareness clock, deadline, exception and extension as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-010", "SRC-011" ], "questions": [ { "id": "recipient-regime-trigger-awareness-clock-deadline-exception-and-extension-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish recipient, regime, trigger, awareness clock, deadline, exception and extension?", "kind": "requirement", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "recipient-regime-trigger-awareness-clock-deadline-exception-and-extension-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on recipient, regime, trigger, awareness clock, deadline, exception and extension, under which authority and limits?", "kind": "identity", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "recipient-regime-trigger-awareness-clock-deadline-exception-and-extension-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify recipient, regime, trigger, awareness clock, deadline, exception and extension?", "kind": "composition", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "recipient-regime-trigger-awareness-clock-deadline-exception-and-extension-data", "name": "Recipient, regime, trigger, awareness clock, deadline, exception and extension data", "description": "Typed incident-report data for recipient, regime, trigger, awareness clock, deadline, exception and extension, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "recipient-regime-trigger-awareness-clock-deadline-exception-and-extension-record", "name": "Recipient, regime, trigger, awareness clock, deadline, exception and extension record", "description": "Immutable or successor-versioned report evidence for recipient, regime, trigger, awareness clock, deadline, exception and extension.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for recipient-regime-trigger-awareness-clock-deadline-exception-and-extension; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "initial-intermediate-final-submission-receipt-question-response-and-status", "name": "Initial, intermediate or final submission, receipt, question, response and status", "description": "Records initial, intermediate or final submission, receipt, question, response and status as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-010", "SRC-011" ], "questions": [ { "id": "initial-intermediate-final-submission-receipt-question-response-and-status-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish initial, intermediate or final submission, receipt, question, response and status?", "kind": "relationship", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "initial-intermediate-final-submission-receipt-question-response-and-status-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on initial, intermediate or final submission, receipt, question, response and status, under which authority and limits?", "kind": "classification", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "initial-intermediate-final-submission-receipt-question-response-and-status-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify initial, intermediate or final submission, receipt, question, response and status?", "kind": "evidence", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "initial-intermediate-final-submission-receipt-question-response-and-status-data", "name": "Initial, intermediate or final submission, receipt, question, response and status data", "description": "Typed incident-report data for initial, intermediate or final submission, receipt, question, response and status, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "initial-intermediate-final-submission-receipt-question-response-and-status-record", "name": "Initial, intermediate or final submission, receipt, question, response and status record", "description": "Immutable or successor-versioned report evidence for initial, intermediate or final submission, receipt, question, response and status.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for initial-intermediate-final-submission-receipt-question-response-and-status; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "governance-disclosure-lifecycle-records-and-projections", "name": "Governance, disclosure, lifecycle, records and projections", "description": "Groups governed report context for governance, disclosure, lifecycle, records and projections.", "rationale": "Append-only governance protects accountability, confidentiality and interoperability.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ], "layers": [ { "id": "approval-confidentiality-communication-and-public-summary", "name": "Approval, confidentiality, communication and public summary", "description": "Groups source-qualified report context for approval, confidentiality, communication and public summary.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-010", "SRC-011", "SRC-012" ], "findings": [ { "id": "author-approver-legal-review-attestation-conflict-and-accountability", "name": "Author, approver, legal review, attestation, conflict and accountability", "description": "Records author, approver, legal review, attestation, conflict and accountability as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-010", "SRC-011", "SRC-012" ], "questions": [ { "id": "author-approver-legal-review-attestation-conflict-and-accountability-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish author, approver, legal review, attestation, conflict and accountability?", "kind": "authority", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "author-approver-legal-review-attestation-conflict-and-accountability-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on author, approver, legal review, attestation, conflict and accountability, under which authority and limits?", "kind": "relationship", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "author-approver-legal-review-attestation-conflict-and-accountability-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify author, approver, legal review, attestation, conflict and accountability?", "kind": "ownership", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "author-approver-legal-review-attestation-conflict-and-accountability-data", "name": "Author, approver, legal review, attestation, conflict and accountability data", "description": "Typed incident-report data for author, approver, legal review, attestation, conflict and accountability, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-010", "SRC-011", "SRC-012" ] } ], "artifacts": [ { "id": "author-approver-legal-review-attestation-conflict-and-accountability-record", "name": "Author, approver, legal review, attestation, conflict and accountability record", "description": "Immutable or successor-versioned report evidence for author, approver, legal review, attestation, conflict and accountability.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for author-approver-legal-review-attestation-conflict-and-accountability; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-010", "SRC-011", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "confidentiality-privilege-trade-secret-minimization-public-summary-and-notice", "name": "Confidentiality, privilege, trade secret, minimization, public summary and notice", "description": "Records confidentiality, privilege, trade secret, minimization, public summary and notice as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-010", "SRC-011", "SRC-012" ], "questions": [ { "id": "confidentiality-privilege-trade-secret-minimization-public-summary-and-notice-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish confidentiality, privilege, trade secret, minimization, public summary and notice?", "kind": "privacy", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "confidentiality-privilege-trade-secret-minimization-public-summary-and-notice-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on confidentiality, privilege, trade secret, minimization, public summary and notice, under which authority and limits?", "kind": "authority", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "confidentiality-privilege-trade-secret-minimization-public-summary-and-notice-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify confidentiality, privilege, trade secret, minimization, public summary and notice?", "kind": "measurement", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "confidentiality-privilege-trade-secret-minimization-public-summary-and-notice-data", "name": "Confidentiality, privilege, trade secret, minimization, public summary and notice data", "description": "Typed incident-report data for confidentiality, privilege, trade secret, minimization, public summary and notice, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-010", "SRC-011", "SRC-012" ] } ], "artifacts": [ { "id": "confidentiality-privilege-trade-secret-minimization-public-summary-and-notice-record", "name": "Confidentiality, privilege, trade secret, minimization, public summary and notice record", "description": "Immutable or successor-versioned report evidence for confidentiality, privilege, trade secret, minimization, public summary and notice.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for confidentiality-privilege-trade-secret-minimization-public-summary-and-notice; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-010", "SRC-011", "SRC-012" ] } ], "inline_only_rationale": null } ] }, { "id": "evidence-correction-retention-audit-and-interoperability", "name": "Evidence, correction, retention, audit and interoperability", "description": "Groups source-qualified report context for evidence, correction, retention, audit and interoperability.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ], "findings": [ { "id": "attachment-evidence-digest-chain-of-custody-source-and-provenance", "name": "Attachment, evidence, digest, chain of custody, source and provenance", "description": "Records attachment, evidence, digest, chain of custody, source and provenance as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ], "questions": [ { "id": "attachment-evidence-digest-chain-of-custody-source-and-provenance-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish attachment, evidence, digest, chain of custody, source and provenance?", "kind": "evidence", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "attachment-evidence-digest-chain-of-custody-source-and-provenance-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on attachment, evidence, digest, chain of custody, source and provenance, under which authority and limits?", "kind": "requirement", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "attachment-evidence-digest-chain-of-custody-source-and-provenance-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify attachment, evidence, digest, chain of custody, source and provenance?", "kind": "exception", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "attachment-evidence-digest-chain-of-custody-source-and-provenance-data", "name": "Attachment, evidence, digest, chain of custody, source and provenance data", "description": "Typed incident-report data for attachment, evidence, digest, chain of custody, source and provenance, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "attachment-evidence-digest-chain-of-custody-source-and-provenance-record", "name": "Attachment, evidence, digest, chain of custody, source and provenance record", "description": "Immutable or successor-versioned report evidence for attachment, evidence, digest, chain of custody, source and provenance.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for attachment-evidence-digest-chain-of-custody-source-and-provenance; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "draft-submitted-accepted-amended-superseded-closed-reopened-retained-and-projected", "name": "Draft, submitted, accepted, amended, superseded, closed, reopened, retained and projected", "description": "Records draft, submitted, accepted, amended, superseded, closed, reopened, retained and projected as source-qualified report context while incident, system, investigation, authority, remediation, evidence and records masters remain external.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ], "questions": [ { "id": "draft-submitted-accepted-amended-superseded-closed-reopened-retained-and-projected-q01", "text": "What stable identity, report version, jurisdiction-qualified value and explicit unknown establish draft, submitted, accepted, amended, superseded, closed, reopened, retained and projected?", "kind": "lifecycle", "answer_data": [ "report, incident and external master identifiers", "typed value, source and applicable regime", "unknown, withheld, disputed and not-applicable states" ] }, { "id": "draft-submitted-accepted-amended-superseded-closed-reopened-retained-and-projected-q02", "text": "Who observed, asserted, reviewed, approved, received or may rely on draft, submitted, accepted, amended, superseded, closed, reopened, retained and projected, under which authority and limits?", "kind": "constraint", "answer_data": [ "actor, role, organization and contact", "authority, mandate, purpose, policy and access", "conflict, contest, exception and escalation" ] }, { "id": "draft-submitted-accepted-amended-superseded-closed-reopened-retained-and-projected-q03", "text": "Which occurrence, awareness, effective, submitted, recorded, ingested and knowledge times, evidence and uncertainty qualify draft, submitted, accepted, amended, superseded, closed, reopened, retained and projected?", "kind": "provenance", "answer_data": [ "distinct event and knowledge times", "evidence, method, confidence and uncertainty", "successor, correction, retention and audit" ] } ], "data_elements": [ { "id": "draft-submitted-accepted-amended-superseded-closed-reopened-retained-and-projected-data", "name": "Draft, submitted, accepted, amended, superseded, closed, reopened, retained and projected data", "description": "Typed incident-report data for draft, submitted, accepted, amended, superseded, closed, reopened, retained and projected, qualified by report version, jurisdiction, source, authority, time, evidence and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "draft-submitted-accepted-amended-superseded-closed-reopened-retained-and-projected-record", "name": "Draft, submitted, accepted, amended, superseded, closed, reopened, retained and projected record", "description": "Immutable or successor-versioned report evidence for draft, submitted, accepted, amended, superseded, closed, reopened, retained and projected.", "media_or_form": [ "logical AI incident report assertion", "fact, assessment, impact, response, submission, correction or evidence record" ], "serial": true, "identity_strategy": "Report-case ID plus independent assertion, submission, decision, event or artifact ID for draft-submitted-accepted-amended-superseded-closed-reopened-retained-and-projected; incident title, date, URL and digest never identify the report alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "open-report-case", "name": "Open an AI incident report case", "description": "Governed operation to open an ai incident report case without autonomous legal classification, regulatory submission, public disclosure, liability admission, attribution, access expansion, evidence destruction or closure.", "inputs": [ "reporting mandate", "incident reference", "reporter" ], "outputs": [ "stable report case" ], "preconditions": [ "identity, jurisdiction, role and duplicate checks pass" ], "effects": [ "a report head exists without creating or deciding the incident master" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-014" ] }, { "id": "bind-affected-systems-and-parties", "name": "Bind affected systems and responsible parties", "description": "Governed operation to bind affected systems and responsible parties without autonomous legal classification, regulatory submission, public disclosure, liability admission, attribution, access expansion, evidence destruction or closure.", "inputs": [ "report", "system and deployment references", "party roles" ], "outputs": [ "version-qualified bindings" ], "preconditions": [ "identity, version, role, source and authority checks pass" ], "effects": [ "external masters remain independent and unmodified" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "record-facts-and-timeline", "name": "Record source-qualified facts and timeline", "description": "Governed operation to record source-qualified facts and timeline without autonomous legal classification, regulatory submission, public disclosure, liability admission, attribution, access expansion, evidence destruction or closure.", "inputs": [ "report", "observations", "evidence" ], "outputs": [ "append-only fact assertions" ], "preconditions": [ "source, observer, confidence and time-basis checks pass" ], "effects": [ "facts preserve uncertainty and knowledge time" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008", "SRC-014", "SRC-015" ] }, { "id": "assess-classification-impact-and-causality", "name": "Assess classification, impact and causality", "description": "Governed operation to assess classification, impact and causality without autonomous legal classification, regulatory submission, public disclosure, liability admission, attribution, access expansion, evidence destruction or closure.", "inputs": [ "report", "facts", "applicable criteria" ], "outputs": [ "qualified assessment assertions" ], "preconditions": [ "regime, method, evidence, reviewer and uncertainty checks pass" ], "effects": [ "assessment does not become an autonomous legal or authority finding" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "link-security-privacy-and-investigation", "name": "Link security, privacy and investigation records", "description": "Governed operation to link security, privacy and investigation records without autonomous legal classification, regulatory submission, public disclosure, liability admission, attribution, access expansion, evidence destruction or closure.", "inputs": [ "report", "external findings", "applicable profiles" ], "outputs": [ "non-owning control and investigation view" ], "preconditions": [ "identity, access, source and status checks pass" ], "effects": [ "cyber incident, privacy breach and AI incident remain distinct" ], "source_refs": [ "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012" ] }, { "id": "record-response-and-remediation", "name": "Record response and remediation summaries", "description": "Governed operation to record response and remediation summaries without autonomous legal classification, regulatory submission, public disclosure, liability admission, attribution, access expansion, evidence destruction or closure.", "inputs": [ "report", "external actions", "outcome evidence" ], "outputs": [ "source-qualified response view" ], "preconditions": [ "owner, authorization, status, effectiveness and residual-risk checks pass" ], "effects": [ "the report does not execute, close or own remediation work" ], "source_refs": [ "SRC-001", "SRC-006", "SRC-008", "SRC-012", "SRC-013" ] }, { "id": "calculate-obligation-and-deadline", "name": "Calculate a reporting obligation and deadline", "description": "Governed operation to calculate a reporting obligation and deadline without autonomous legal classification, regulatory submission, public disclosure, liability admission, attribution, access expansion, evidence destruction or closure.", "inputs": [ "report", "jurisdiction profile", "awareness and severity facts" ], "outputs": [ "explainable obligation assessment" ], "preconditions": [ "legal basis, applicability, clock, exception and reviewer checks pass" ], "effects": [ "calculation remains advice until accountable approval" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-010", "SRC-011" ] }, { "id": "submit-or-update-report", "name": "Submit an initial, intermediate, final or corrected report", "description": "Governed operation to submit an initial, intermediate, final or corrected report without autonomous legal classification, regulatory submission, public disclosure, liability admission, attribution, access expansion, evidence destruction or closure.", "inputs": [ "approved report version", "recipient", "authorized channel" ], "outputs": [ "submission reference and receipt" ], "preconditions": [ "authority, completeness, deadline, confidentiality and channel checks pass" ], "effects": [ "submitted content becomes immutable and later changes create successors" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-010", "SRC-011" ] }, { "id": "amend-supersede-close-or-reopen", "name": "Amend, supersede, close or reopen a report", "description": "Governed operation to amend, supersede, close or reopen a report without autonomous legal classification, regulatory submission, public disclosure, liability admission, attribution, access expansion, evidence destruction or closure.", "inputs": [ "current head", "authorized decision", "reason and successor" ], "outputs": [ "successor lifecycle assertion" ], "preconditions": [ "expected revision, authority, affected scope, notification and retention checks pass" ], "effects": [ "prior submissions and evidence remain reconstructable" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-008", "SRC-014" ] }, { "id": "disclose-project-retain-and-audit", "name": "Disclose, project, retain and audit", "description": "Governed operation to disclose, project, retain and audit without autonomous legal classification, regulatory submission, public disclosure, liability admission, attribution, access expansion, evidence destruction or closure.", "inputs": [ "report", "target view", "access and records policy" ], "outputs": [ "filtered disclosure, projection or audit event" ], "preconditions": [ "purpose, authority, minimization, mapping, loss, hold and idempotency checks pass" ], "effects": [ "restricted context stays protected and projection loss stays explicit" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015" ] } ], "composition": [ { "target": "WM-AI-001 AI System", "relation": "REFERENCE", "purpose": "Represent the unfrozen parent and affected-system boundary without inheritance, composition, mutation, release or cascade authority.", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-007" ] }, { "target": "WM-ACT-019 Incident", "relation": "REFERENCE", "purpose": "Resolve the underlying general incident while preserving a separate reporting-case identity and lifecycle.", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-008", "SRC-012" ] }, { "target": "Investigation, regulatory case, remediation, harm, vulnerability, evidence, audit and records models", "relation": "REFERENCE", "purpose": "Resolve authoritative findings, actions, decisions and evidence without absorbing their ownership.", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-014" ] }, { "target": "EU AI Act, OECD AI incident framework, NIST AI RMF and SP 800-61r3, FIRST CSIRT, ISO/IEC 42001, PROV-O and RFC 3339", "relation": "ALIGN", "purpose": "Project version-pinned legal, reporting, risk, response, management, provenance and timestamp views with declared loss.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-013", "SRC-014", "SRC-015" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension owner, incident-reporting mandate and accountable AI system owner", "Authoritative incident, AI system, model, deployment, person, organization, harm, investigation, risk, vulnerability, remediation, regulatory-case, evidence, audit and records registries", "Approved jurisdiction, sector, seriousness, causality, privacy-breach, security, safety, deadline, disclosure, privilege, access, retention and interoperability profiles", "Role, delegation, legal review, submission, authority-cooperation, affected-person communication and agent-operation policies" ], "namespace_guidance": "Mint report-case, version, assertion, assessment, submission, receipt, authority-exchange, correction, disclosure and projection IDs; preserve every external master identifier.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize one reporting case by authoritative report-case identifier and issuer namespace, never by incident title, date, system name, recipient or submission number alone.", "Keep incident, report case, report version, submission, receipt, investigation, finding, remediation action, authority case and public summary independently identifiable." ], "patch_rules": [ "Extensions declare jurisdiction, sector, incident class, reporting duty, deadline, privacy, security, safety, disclosure, retention and interoperability effects.", "Submitted report versions, facts, decisions and receipts are immutable; amendments and corrections create linked successors.", "Never silently change affected system, severity, causal claim, impact scope, legal basis, deadline, recipient, confidentiality or evidence." ], "compatibility_rules": [ "Ignore additive fields only when report and incident identity, version, jurisdiction, source, authority, time, uncertainty, access and provenance survive.", "Every projection pins law, guidance, standard, schema, vocabulary, template and mapping versions and declares information loss." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier for each report case, version, submission, assertion, decision or projection, qualified by issuer, namespace and record kind.", "Governed globally resolvable report-case IRI.", "Dimension UUID or ULID when neither preceding identifier exists." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z; distinguish occurrence, detection, discovery, awareness, notification, submission, receipt, correction, closure, recorded, ingested and knowledge times whenever they differ.", "serial_naming_rule": "Use {report-case-id}--{report-version-or-submission-id}--{assertion-decision-event-or-artifact-id}--{artifact-kind}--{revision-id}.", "integrity_rule": "Store digest, media type, record kind, report and incident scope, system and regime versions, actor, event and knowledge times, confidentiality marking and provenance." }, "policies": [ "The report owns its reporting-case record and version lineage but not Incident, AI System, Model, Deployment, Investigation, Regulatory Case, Remediation, Harm, Vulnerability, Evidence, Audit or Records masters.", "Observed fact, reporter statement, hypothesis, causal assessment, authority finding, impact estimate and verified outcome are distinct assertion classes.", "An AI incident, security incident, personal-data breach, hazard, defect, complaint and regulatory nonconformity are not automatically equivalent.", "Agents cannot make binding legal classification, submit to authorities, disclose restricted material, admit liability, attribute blame, widen access, destroy evidence or close a case without delegated authority." ], "crud": { "read": [ "Resolve current head, incident and system bindings, jurisdiction, facts, timeline, classification, impact, causes, security, privacy, response, obligation, submissions, authority exchanges, confidentiality, lifecycle and projection loss under the permitted view." ], "create": [ "Bind stable report identity, issuer, jurisdiction, incident, affected system, reporter, legal basis, source, authority and initial state before report content." ], "update": [ "Append successor facts, assessments, impact, causal, response, obligation, submission, authority-exchange, correction, disclosure and lifecycle assertions with reason, authority, expected revision, event time and knowledge time." ], "delete": [ "Apply legal hold, investigation, rights, privacy, security and adopting-Dimension records policy; withdraw or tombstone only the report view without cascading to incident, system, authority, evidence or records masters, and let authoritative systems execute physical disposition." ] }, "roles": [ { "name": "AI system owner and accountable deployer", "responsibilities": [ "Own reporting readiness, accountable assessment, response coordination and use of incident reports." ] }, { "name": "Incident reporter and case coordinator", "responsibilities": [ "Maintain report identity, source-qualified facts, timeline, versions, submissions and authority exchanges." ] }, { "name": "Technical investigator and AI specialist", "responsibilities": [ "Supply bounded system, model, data, failure, causal and corrective evidence with uncertainty." ] }, { "name": "Safety, security and privacy responder", "responsibilities": [ "Assess harm, threat, vulnerability, privacy-breach, containment, notification and residual risk profiles." ] }, { "name": "Legal, compliance and regulatory liaison", "responsibilities": [ "Determine applicable regimes, deadlines, recipients, privilege, confidentiality and approved submissions." ] }, { "name": "Independent reviewer and approval authority", "responsibilities": [ "Review evidence, conflicts, classifications, causal claims, completeness and release decisions within mandate." ] }, { "name": "Records and disclosure steward", "responsibilities": [ "Own access, minimization, public summaries, legal hold, retention, disposition and projection policy." ] } ], "access": { "default_rule": "Deny personal or sensitive data, trade secrets, privileged analysis, security details, protected evidence, reporter identities and unpublished authority exchanges unless a purpose-bound policy permits the minimum necessary view.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Declared safety, emergency, investigation, regulator, legal, audit or subject-rights access must cite authority, scope, purpose and time limit and must be logged." ], "audit_requirements": [ "Log actor, agent, role, purpose, report case and version, operation, authority, policy, RFC 3339 time, affected fields, source revision and outcome without unnecessary restricted-content duplication." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension AI, incident, reporting, jurisdiction, safety, security, privacy, disclosure, access, retention and agent policies.", "Read this report and linked incident, system, deployment, investigation, remediation, authority, evidence and records models before mutation." ] } }, "coverage": { "claim": "WM-AI-010 covers one governed AI incident reporting case from identity and affected-system bindings through source-qualified facts, timeline, classification, impact, causal, security, privacy, response, remediation, obligation, submission, authority exchange, disclosure, lifecycle, evidence, retention and projections. Jurisdiction and sector profiles, final EU guidance and independent external review remain deferred.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Identity is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." }, { "dimension": "classification and direct properties", "status": "covered", "notes": "Classification and direct properties is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Recognition and observation is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Capabilities and possible actions is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." }, { "dimension": "composition", "status": "covered", "notes": "Composition is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." }, { "dimension": "lifecycle", "status": "covered", "notes": "Lifecycle is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." }, { "dimension": "relationships", "status": "covered", "notes": "Relationships is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." }, { "dimension": "temporal", "status": "covered", "notes": "Temporal is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." }, { "dimension": "spatial", "status": "covered", "notes": "Spatial is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." }, { "dimension": "provenance", "status": "covered", "notes": "Provenance is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Ownership and stewardship is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." }, { "dimension": "validation and quality", "status": "covered", "notes": "Validation and quality is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." }, { "dimension": "access and privacy", "status": "covered", "notes": "Access and privacy is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Retention and deletion is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." }, { "dimension": "interoperability", "status": "covered", "notes": "Interoperability is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." }, { "dimension": "authority and ethics", "status": "covered", "notes": "Authority and ethics is explicit; jurisdiction, sector, incident class, template, deadline, restricted evidence and independent external review remain held where applicable." } ], "known_omissions": [ "Claude and Grok each timed out on one bounded attempt; no independent external result was admitted.", "The unified parent WM-AI-001 and candidate references to WM-AI-001 and WM-ACT-019 are not approved frozen composition edges.", "The European Commission Article 73 guidance and high-risk-system template inspected here remain draft.", "Sector, jurisdiction, system-class and regulator-specific notification forms and deadlines require separate profiles." ], "conflicts": [ "Incident event, report case, report version, submission, receipt, authority case, investigation, remediation and public summary are not interchangeable identities.", "Actual harm, potential hazard, near miss, defect, security incident, personal-data breach and serious incident use different thresholds.", "Observed fact, reporter statement, hypothesis, causal assessment, authority finding and verified outcome require distinct provenance and authority." ], "regional_assumptions": [ "Incident definitions, reportability, seriousness, causal threshold, deadlines, recipients, privilege, disclosure, privacy and retention depend on jurisdiction and sector.", "The EU AI Act, GDPR and EDPB guidance are European Union profiles; NIST publications are voluntary United States guidance unless adopted.", "OECD, FIRST, ISO, PROV and RFC sources are versioned profiles and are not assumed binding, lossless or universally applicable." ], "adversarial_checks": [ "Reject a report without stable case and version identity, issuer, jurisdiction, incident and affected-system bindings, reporter, source, authority, state and current head.", "Reject silent overwrites of submitted facts, classification, causal claims, impact scope, deadline, recipient or evidence.", "Reject autonomous legal classification, authority submission, public disclosure, liability admission, attribution, access expansion, evidence destruction or closure.", "Reject causality, severity, remediation effectiveness or closure inferred only from correlation, system status, mitigation deployment or authority receipt.", "Reject a projection that collapses incident, report, submission, investigation, remediation and authority-case identities or hides information loss." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "aggregate", "status": "accepted", "rationale": "The root is a versioned reporting-case aggregate containing multiple assertions, submissions and authority exchanges. It is distinct from the incident event, affected AI system, investigation, remediation work, authority case and public summary. The frozen catalogue standalone-mm kind is a separate axis." }, "decisions": [ { "concept": "Report versus incident", "disposition": "accepted", "rationale": "The report owns case identity, versions, submissions and communication lineage; the incident owns occurrence and operational history." }, { "concept": "WM-AI-001 parent and candidate reference", "disposition": "accepted-as-unapproved-reference", "rationale": "The unified parent signal and candidate relation identify affected-system context but no approved frozen edge grants inheritance, mutation or cascade authority." }, { "concept": "WM-ACT-019 candidate reference", "disposition": "accepted-as-unapproved-reference", "rationale": "The general incident is an external master. The candidate edge permits only a non-owning boundary reference until approved." }, { "concept": "Fact, statement, hypothesis and finding", "disposition": "accepted", "rationale": "Observed facts, reporter statements, causal hypotheses, reviewed assessments and authority findings retain distinct provenance, confidence and authority." }, { "concept": "Incident and hazard classifications", "disposition": "accepted-with-profile-hold", "rationale": "Actual harm, potential hazard, near miss, defect, security incident, personal-data breach and serious incident have regime-specific thresholds." }, { "concept": "Deadlines and incomplete reports", "disposition": "accepted-with-accountable-review", "rationale": "Obligation and deadline calculations expose legal basis, awareness clock, severity, exceptions and uncertainty; initial incomplete reports and successor updates remain linked and immutable." }, { "concept": "Investigation, remediation and authority case", "disposition": "accepted-external", "rationale": "The report binds source-qualified summaries and exchanges without owning investigation findings, remediation execution or authority decisions." }, { "concept": "Confidentiality, privilege and disclosure", "disposition": "accepted-with-mandatory-hold", "rationale": "Personal data, trade secrets, privileged material, security details, evidence and public summaries require purpose-bound policy and accountable release authority." }, { "concept": "Interoperability profiles", "disposition": "accepted-with-validation-hold", "rationale": "EU, OECD, NIST, FIRST, ISO, PROV and RFC sources have different scopes and every mapping must pin versions and declare loss." }, { "concept": "Single-provider waiver and no-tools audit", "disposition": "accepted-with-mandatory-hold", "rationale": "One bounded Claude Sonnet and one bounded Grok attempt each timed out after 120 seconds. Codex separately audits the frozen validated result and comparison locally without tools or new research facts; assurance remains reviewable-draft." } ], "publicationHolds": [ "Absence-of-external-review hold: one Claude Sonnet and one Grok attempt for WM-AI-010 each timed out after 120 seconds; no external research result was admitted.", "Relation hold: the unified WM-AI-001 parent signal and candidate references to WM-AI-001 and WM-ACT-019 are not approved frozen composition edges and grant no ownership, mutation or cascade behavior.", "Legal-profile hold: serious-incident definition, reportability, causal threshold, awareness clock, deadline, recipient, exception and disclosure depend on jurisdiction, sector and system class.", "Draft-source hold: the inspected European Commission Article 73 guidance and high-risk-system reporting template remain draft and are not treated as binding.", "Authority hold: obligation calculations, causal assessment, regulatory submission, public disclosure, liability admission, attribution and closure require accountable human or delegated authority.", "Confidentiality hold: personal data, trade secrets, privileged analysis, security details, reporter identities and protected evidence require purpose-bound access, minimization and records policy.", "Interoperability hold: EU, OECD, NIST, FIRST, ISO, PROV and RFC projections require release pins, profile validation and information-loss declarations.", "Source-version hold: NIST AI RMF 1.0 is under revision; ISO/IEC 42001 was used only at public catalogue-metadata level.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Approve or reject the WM-AI-001 and WM-ACT-019 relationships and register investigation, remediation, authority-case, harm, vulnerability, evidence and records edges.", "Create jurisdiction, sector, AI-system-class, seriousness, causal-threshold, deadline, recipient and reporting-template profiles.", "Refresh the EU Article 73 mapping when final guidance and templates replace the inspected draft package.", "Validate organization-specific privilege, trade-secret, personal-data, security, disclosure, affected-person communication and retention policies.", "Test version-pinned EU, OECD, NIST, FIRST, ISO, PROV and RFC mappings and obtain supplemental independent external review before canonical promotion." ] }, "statistics": { "sources": 15, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }