{
    "name": "Today's AI Readiness — WIA ASSESS question–provision table",
    "license": "https://creativecommons.org/licenses/by/4.0/",
    "rightsHolder": "(주)스마일스토리",
    "scope": "Questions, answer options and explanations: written by (주)스마일스토리 (CC BY 4.0). Provision names and numbers are factual information; the original legal texts are government materials of each jurisdiction and are not covered by this licence.",
    "attribution": "Source: WIA ASSESS · The Korean Today (CC BY 4.0)",
    "disclosure": "WIA ASSESS is a service run by a company whose CEO is the publisher of The Korean Today.",
    "notLegalAdvice": "Not legal advice. Binding interpretation follows the original legal texts and review by legal professionals.",
    "version": "October 2026",
    "generated": "2026-11-21T12:55:11+09:00",
    "inLanguage": "en",
    "count": 143,
    "diagnostics": {
        "a11y": {
            "diagnostic": "AI Accessibility Inspector",
            "wia_code": "WIA-AAC-001",
            "url": "https://assess.smilestory.ai/diagnose/a11y/?lang=en",
            "law_note": "Provisions reflect the law as of October 2026 (Korea's Disability Discrimination Act, Act No. 21115, and its Enforcement Decree as in force from 2026-10-02; Digital Inclusion Act, Act No. 20672, in force 2026-01-22; AI Basic Act, Act No. 21311). Korea's web and app accessibility provisions moved from the Framework Act on Intelligent Informatization to the Digital Inclusion Act on 2026-01-22. The EU AI Act is cited as amended by Regulation (EU) 2026/1744. Standards and dates may change depending on when EN 301 549 V4.1.1 is cited in the Official Journal and whether the US Title II rule is amended further. For binding interpretation, rely on the official texts and qualified legal review.",
            "disclaimer": "This assessment does not constitute legal advice or an accessibility certification. Final determinations require legal review."
        },
        "compliance": {
            "diagnostic": "AI Compliance Check",
            "wia_code": "WIA-GDPR-001",
            "url": "https://assess.smilestory.ai/diagnose/compliance/?lang=en",
            "law_note": "Provisions follow the law as of October 2026 (AI Basic Act, Act No. 21311, current as of 2026-07-21). The amendment taking effect on 2027-04-21 (Act No. 22076) changes only the training-data provisions (Arts. 15 and 15-2) and does not affect the articles used here; details may still change with enforcement decrees and notices. For binding interpretation, rely on the statutory text and review by legal counsel.",
            "disclaimer": "This assessment does not constitute legal advice. Final determinations require legal review."
        },
        "data-quality": {
            "diagnostic": "AI Data Quality Audit",
            "wia_code": "WIA-DATA-GOV-001",
            "url": "https://assess.smilestory.ai/diagnose/data-quality/?lang=en",
            "law_note": "Provisions follow the law as of October 2026 (Korea's AI Basic Act, Act No. 21311, and its Enforcement Decree in force 2026-08-20; PIPA as in force 2026-09-11; Copyright Act as in force 2026-08-11). Under amending Act No. 22076 (promulgated 2026-10-20), from 2027-04-21 national agencies and recipients of government contributions or subsidies designated by decree must link or provide the training data built in those projects to the Ministry of Science and ICT's integrated training data system (Art. 15-2(2); exceptions for trade secrets, third-party rights and similar reasons). Under PIPA amending Act No. 21910 (promulgated 2026-09-08), a special route for using lawfully collected personal data for AI development starts on 2027-03-09 (Art. 28-12: only where anonymisation or pseudonymisation would not work, safeguards are in place, a public- or social-interest purpose is met and the PIPC has approved); details await the Enforcement Decree. The EU AI Act reflects Regulation (EU) 2026/1744 (Digital Omnibus on AI, in force 2026-07-27). Korean legislation on copyright and AI training is still under discussion, and a constitutional challenge to California AB 2013 is pending on appeal, so these may change. For binding interpretation, rely on the statutory text and review by legal counsel.",
            "disclaimer": "This assessment does not constitute legal advice. Final determinations require legal review."
        },
        "ethics": {
            "diagnostic": "AI Ethics Test",
            "wia_code": "WIA-AI-ETH-002",
            "url": "https://assess.smilestory.ai/diagnose/ethics/?lang=en",
            "law_note": "Provisions follow the law as of October 2026 (Korea's AI Basic Act, Act No. 21311, current as of 2026-07-21; Enforcement Decree, Presidential Decree No. 36580, effective 2026-08-20). Korea's AI Ethics Principles, adopted on 2026-08-21, are a non-binding norm; an explanatory guide and self-check list are still to be issued and may add items. Amending Act No. 22076 (effective 2027-04-21) changes the training-data provisions, not the ethics provisions. The EU AI Act is reflected as amended by Regulation (EU) 2026/1744 (in force 2026-07-27). For binding interpretation, rely on the statutory text and review by legal counsel.",
            "disclaimer": "This assessment does not constitute legal advice. Final determinations require legal review."
        },
        "genai-label": {
            "diagnostic": "Generative AI Labelling Audit",
            "wia_code": "WIA-AI-AUTH-001",
            "url": "https://assess.smilestory.ai/diagnose/genai-label/?lang=en",
            "law_note": "Provisions follow the law as of October 2026 (AI Basic Act, Act No. 21311, current as of 2026-07-21). The details of labeling methods are delegated to the enforcement decree and guidelines and may change (the guidelines allow invisible watermarks, but direct that deepfakes be labeled so that people can clearly recognize them). US provisions differ by state and are frequently litigated or amended. For binding interpretation, rely on the statutory text and review by legal counsel.",
            "disclaimer": "This assessment does not constitute legal advice. Final determinations require legal review."
        },
        "global": {
            "diagnostic": "Cross-Border Operator Duties",
            "wia_code": "WIA-LEGAL-003",
            "url": "https://assess.smilestory.ai/diagnose/global/?lang=en",
            "law_note": "Provisions reflect the law as of October 2026: Korea's AI Basic Act (Act No. 21311, current as of 2026-07-21; amending Act No. 22076 takes effect 2027-04-21), its Enforcement Decree (2026-08-20) and PIPA (2026-09-11); the EU AI Act as amended by the Digital Omnibus (Regulation (EU) 2026/1744, in force 2026-07-27). Proposed GDPR amendments are still under negotiation and not reflected. Korea's agent thresholds are reviewed every three years (Decree Art. 33). Utah's AI Policy Act (Title 13 Ch. 72, Office of AI Policy) is set to sunset on 2027-07-01; the AI disclosure duties in §§13-75-103/-104 have no repeal date. Chinese rules and US state laws change often; rely on official texts and local counsel.",
            "disclaimer": "This is a self-assessment and does not constitute legal advice. Final determinations require review by counsel in each jurisdiction."
        },
        "highrisk": {
            "diagnostic": "High-risk AI Identifier",
            "wia_code": "WIA-AI-SAFE-002",
            "url": "https://assess.smilestory.ai/diagnose/highrisk/?lang=en",
            "law_note": "As of October 2026: Korea's AI Basic Act (Act No. 21311, current 2026-07-21) and Enforcement Decree (No. 36580, current 2026-08-20); the 2027-04-21 amendment (Act No. 22076) touches only training-data provisions. Extra high-impact areas (Art. 2 item 4 (k)) and the Art. 33(3) guideline may change. EU AI Act as amended by Regulation (EU) 2026/1744 (in force 2026-07-27); the high-risk classification guidelines are still in draft. Colorado SB 26-189 replaced SB 24-205; AG rules are pending. Rely on the statutory text and legal counsel for binding interpretation.",
            "disclaimer": "This assessment does not constitute legal advice and does not determine the legal classification of any system. Final determinations require legal review."
        },
        "impact": {
            "diagnostic": "AI Impact Assessment Simulator",
            "wia_code": "WIA-AI-AUDIT-001",
            "url": "https://assess.smilestory.ai/diagnose/impact/?lang=en",
            "law_note": "Provisions follow the law as of October 2026 (AI Basic Act, Act No. 21311, current as of 2026-07-21). The content and method of impact assessments are delegated to the enforcement decree (Art. 35(3)) and may change. The Colorado AI Act (SB 24-205) was repealed and replaced in 2026 by SB 26-189. For binding interpretation, rely on the statutory text and review by legal counsel.",
            "disclaimer": "This assessment does not constitute legal advice. Final determinations require legal review."
        },
        "penalty": {
            "diagnostic": "AI Penalty Risk Score",
            "wia_code": "WIA-PENALTY-001",
            "url": "https://assess.smilestory.ai/diagnose/penalty/?lang=en",
            "law_note": "Citations follow the law as of October 2026 (Korea's AI Basic Act, Act No. 21311 as in force on 2026-07-21, and its Decree as in force on 2026-08-20; Korea's PIPA, Act No. 21445, in force since 2026-09-11). The AI Basic Act amendment promulgated on 2026-10-20 (Act No. 22076, in force 2027-04-21) changes the training-data provisions and leaves the fine provisions unchanged. Check government announcements for the end of the grace period. The EU AI Act reflects the amendments by Regulation (EU) 2026/1744 (in force 2026-07-27). US provisions vary by state and change often through amendments and litigation. For binding interpretation, rely on the official legal texts and review by qualified counsel.",
            "disclaimer": "This assessment does not constitute legal advice. Final determinations require legal review."
        },
        "privacy": {
            "diagnostic": "AI Privacy Audit",
            "wia_code": "WIA-GDPR-002",
            "url": "https://assess.smilestory.ai/diagnose/privacy/?lang=en",
            "law_note": "Provisions are as of October 2026. Korea's PIPA follows Act No. 21445 (in force from 2026-09-11; the mandatory certification provision from 2027-07-01) and the Enforcement Decree in force from 2026-09-11. The AI development exception (Act No. 21910) is scheduled to take effect on 2027-03-09; its detailed criteria are delegated to the Enforcement Decree and not yet final. The EU AI Act reflects Regulation (EU) 2026/1744. The proposed GDPR amendments (Digital Omnibus, proposed November 2025) are still in the legislative process as of October 2026 and are not reflected. California CCPA regulations (effective 2026-01-01); Colorado SB 26-189 (effective 2027-01-01). For binding interpretation, rely on the official texts and review by legal counsel.",
            "disclaimer": "This assessment does not constitute legal advice. Final determinations require legal review."
        },
        "sme": {
            "diagnostic": "SME AI Diagnosis",
            "wia_code": "WIA-SME-002",
            "url": "https://assess.smilestory.ai/diagnose/sme/?lang=en",
            "law_note": "Provisions follow the law as of October 2026: Korea's AI Basic Act (Act No. 21311, current as of 2026-07-21; amending Act No. 22076 scheduled to take effect 2027-04-21), its Enforcement Decree (in force 2026-08-20), and Korea's Personal Information Protection Act (Act No. 21445, in force 2026-09-11). The EU AI Act is reflected as amended by Regulation (EU) 2026/1744 (Digital Omnibus on AI), in force 2026-07-27. Notice methods and exemptions may change through the Enforcement Decree or ministry notices, and support programme names and conditions change every year. Utah's AI Policy Act is scheduled to be repealed on 2027-07-01. For binding interpretation, rely on the statutory text and review by legal counsel.",
            "disclaimer": "This assessment does not constitute legal advice. Final determinations require legal review."
        },
        "transparency": {
            "diagnostic": "AI Transparency Requirements",
            "wia_code": "WIA-AI-INTEROP-001",
            "url": "https://assess.smilestory.ai/diagnose/transparency/?lang=en",
            "law_note": "Articles reflect the law as of October 2026 (Korea's AI Basic Act, Act No. 21311, and its Enforcement Decree, Presidential Decree No. 36580; Korea's Personal Information Protection Act, Act No. 21445, and its Enforcement Decree No. 36671). The amending Act No. 22076 (in force 2027-04-21) does not change Art. 31 or 34 used here. Detailed ministerial notices for the Art. 34 measures and the handling of the grace period may change. EU AI Act dates reflect Regulation (EU) 2026/1744 (in force 2026-07-27); when the Art. 86 right to explanation takes practical effect is open to interpretation given the postponed high-risk obligations. Colorado SB 26-189's adverse-outcome explanation will be detailed in Attorney General rules, and Utah's AI disclosure duties (Utah Code §13-75-103, in force 2025-05-07) have no sunset; the separate AI Policy Act (Title 13, Chapter 72, Office of AI Policy) is set to be repealed on 2027-07-01. For binding interpretation, rely on the official legal texts and review by legal counsel.",
            "disclaimer": "This assessment does not constitute legal advice. Final determinations require legal review."
        }
    },
    "items": [
        {
            "key": "a11y:a1",
            "diagnostic": "AI Accessibility Inspector",
            "number": 1,
            "question": "Who mainly uses your AI features (chatbots, voice guidance, kiosks, AI apps)?",
            "options": [
                "Employees only",
                "Members of the public / consumers",
                "Provided by a public body, or offered to EU consumers as a banking, transport, e-commerce, telecoms or e-book service"
            ],
            "provisions": {
                "kr": "Korea's Disability Discrimination Act Art. 21(1)(2) (reasonable accommodation for electronic information and mobile apps; employers with 30+ workers included) · Korea's Digital Inclusion Act Art. 19 (mandatory for public bodies, best-efforts for businesses)",
                "eu": "EAA (Directive 2019/882) Art. 2 products and services in scope · Art. 4(5) microenterprise exemption for services",
                "us": "ADA Title II (state/local government, WCAG 2.1 AA) · Title III (private sector; no web technical rule — litigation risk)"
            },
            "why": "This question measures exposure, not control. Who uses the AI decides which laws apply and how strictly. The more customer-facing or public the service, the more likely a blocked disabled user leads to a complaint, a corrective order or a lawsuit.",
            "first_step": "List each AI feature with its users (staff, customers, public) and the countries served, on one page",
            "law_basis": "October 2026"
        },
        {
            "key": "a11y:a2",
            "diagnostic": "AI Accessibility Inspector",
            "number": 2,
            "question": "Do the release criteria for your AI screens and voice features include an accessibility standard (KWCAG 2.2 / WCAG 2.1 or 2.2 AA / EN 301 549)?",
            "options": [
                "Yes — a named standard and a pass required before release",
                "Standard named, but not a release condition",
                "No standard defined"
            ],
            "provisions": {
                "kr": "Enforcement Decree of Korea's Disability Discrimination Act Art. 14(2)(i) (accessible websites), 14(6)(i) (app verification criteria) · KWCAG 2.2 (KS X OT0003:2022)",
                "eu": "EAA Annex I Section III(c) · Art. 15 (presumption of conformity — no EAA harmonised standard cited in the OJ yet)",
                "us": "ADA Title II rule WCAG 2.1 AA (28 CFR 35.200) · Section 508 WCAG 2.0 AA (36 CFR 1194)"
            },
            "why": "Without a standard, \"accessible\" means something different to everyone, and you cannot show what you met when a complaint or regulator inquiry arrives. AI features change often through model and prompt updates; unless accessibility is a release condition, it breaks again quickly.",
            "first_step": "Name one standard per market (Korea KWCAG 2.2, EU EN 301 549, US WCAG 2.1 AA — for several markets use WCAG 2.2 AA as the common floor)",
            "law_basis": "October 2026"
        },
        {
            "key": "a11y:a3",
            "diagnostic": "AI Accessibility Inspector",
            "number": 3,
            "question": "Can your AI chatbot be used with a keyboard alone, and does a screen reader announce new replies?",
            "options": [
                "Yes — confirmed in hands-on tests with screen readers (NVDA, VoiceOver, etc.)",
                "Automated tools only, or issues from hands-on tests still open",
                "Never checked",
                "N/A — no conversational AI interface"
            ],
            "provisions": {
                "kr": "KWCAG 2.2 6.1.1 keyboard access · 6.1.2 focus order and visibility · 8.2.1 web application accessibility · Korea's Disability Discrimination Act Art. 21(1)(2)",
                "eu": "EAA Annex I Section III(c) · AI Act Art. 50(5) accessibility of AI notices (from 2026-08-02)",
                "us": "WCAG 2.1 SC 2.1.1 Keyboard · 4.1.3 Status Messages (Title II standard)"
            },
            "why": "In many chat widgets new replies appear only visually and focus does not move, so screen-reader users never learn an answer arrived. If the chatbot is your support channel, disabled customers cannot get support at all — a reasonable-accommodation issue under Art. 21 of Korea's Disability Discrimination Act. In the EU the \"you are talking to an AI\" notice must itself be accessible (Art. 50(5)).",
            "first_step": "Announce new replies through an aria-live region and fix the focus order between input, send button and replies",
            "law_basis": "October 2026"
        },
        {
            "key": "a11y:a4",
            "diagnostic": "AI Accessibility Inspector",
            "number": 4,
            "question": "Do voice-only AI features (voice guidance, voice ordering, AI call centre) offer another route such as text or on-screen input?",
            "options": [
                "Yes — text/on-screen input and captions are offered alongside voice",
                "Alternatives exist for some steps only",
                "Voice only",
                "N/A — no voice AI features"
            ],
            "provisions": {
                "kr": "Korea's Disability Discrimination Act Art. 21(1) (sign language, text and other necessary means) · Enforcement Decree Art. 14(6)(iv)(v) (apps: sign/text/voice communication, voice-command support)",
                "eu": "EAA Annex I Section III(b)(i) more than one sensory channel · Section I 2(a) (products: alternatives to vision, hearing and speech)",
                "us": "ADA effective communication (28 CFR 35.160 — public entities) · Title III litigation risk"
            },
            "why": "Deaf and speech-impaired people cannot use an AI that accepts voice alone. Speech recognition also errs more for atypical speech (speech or hearing impairments, older speakers), so without an alternative the result is effectively a refusal of service. Korea requires text and other necessary means; the EU requires more than one sensory channel for products and services in EAA scope.",
            "first_step": "Give every voice step an equivalent text-entry or button route",
            "law_basis": "October 2026"
        },
        {
            "key": "a11y:a5",
            "diagnostic": "AI Accessibility Inspector",
            "number": 5,
            "question": "Does a person review the alt text (image descriptions) and captions that AI generates automatically?",
            "options": [
                "Yes — key content is reviewed by a person and error reports are accepted",
                "Auto-generated output is published as is",
                "No alt text or captions provided",
                "N/A — no image or video content"
            ],
            "provisions": {
                "kr": "KWCAG 2.2 5.1.1 appropriate text alternatives · 5.2.1 captions · Korea's Disability Discrimination Act Art. 21(1)",
                "eu": "EAA Annex I Section III(b)(vi) alternative presentation of non-text content",
                "us": "WCAG 2.1 SC 1.1.1 Non-text Content · 1.2.2 Captions (Title II standard)"
            },
            "why": "Automatic descriptions often get text, numbers, prices and warning signs in images wrong, or leave them out. Alt text that exists but is wrong leads blind users to decide on false information, and auditors count it as an error unless it is \"appropriate\". The risk is highest for content people act on: products, terms, safety notices.",
            "first_step": "Flag images and videos about products, prices, safety and contracts as \"human review required\"",
            "law_basis": "October 2026"
        },
        {
            "key": "a11y:a6",
            "diagnostic": "AI Accessibility Inspector",
            "number": 6,
            "question": "If you operate or make kiosks with AI features (self-ordering or information terminals), are accessibility measures in place?",
            "options": [
                "Yes — terminals meeting the verification criteria + audio locator (or small-site exception measures done)",
                "Some measures only (e.g. staff assistance)",
                "No measures",
                "N/A — we do not operate, make or lease kiosks"
            ],
            "provisions": {
                "kr": "Korea's Disability Discrimination Act Art. 15(3) · Enforcement Decree Art. 10-2 and Annexed Table 2-2 (existing terminals from 2026-01-28) · Korea's Digital Inclusion Act Art. 20 (fine up to KRW 30m for ignoring a corrective order, Art. 37(1))",
                "eu": "EAA Art. 2(1)(b) self-service terminals (ATMs, ticketing, check-in, information terminals) · Art. 32(2) existing terminals up to 20 years",
                "us": "ADA Title III — no kiosk-specific technical rule (court decisions, litigation risk)"
            },
            "why": "Since 2026-01-28, Korea's Disability Discrimination Act applies the reasonable-accommodation duty to kiosks installed before that date as well. The default is a terminal meeting the Ministry of Science and ICT verification criteria plus an audio locator; sites under 50 m², small business owners and others may instead use compatible assistive devices or staff assistance with a call bell. Under the Digital Inclusion Act, ignoring a corrective order can lead to a fine of up to KRW 30m. A kiosk with AI voice ordering is still a kiosk. Under the Digital Inclusion Act Art. 20(2) and Enforcement Decree Art. 15(2)(3), makers must build terminals that meet the verification criteria (or support staff call or real-time audio guidance), and lessors may not refuse, without good reason, to lease such terminals on request. This applies from 2026-01-22, but only from 2026-07-22 for medium enterprises and from 2027-01-22 for small enterprises and small business owners (Decree Addenda Art. 3).",
            "first_step": "List kiosks by site (model, installation date, maker, AI features)",
            "law_basis": "October 2026"
        },
        {
            "key": "a11y:a7",
            "diagnostic": "AI Accessibility Inspector",
            "number": 7,
            "question": "Can users switch AI replies to plain language or a short summary, and extend time limits (session timeouts)?",
            "options": [
                "Yes — both plain-language switching and time extension",
                "Only one of the two",
                "Neither"
            ],
            "provisions": {
                "kr": "KWCAG 2.2 6.2.1 adjustable response time · 5.3.3 clear instructions · Enforcement Decree of Korea's AI Basic Act Art. 1-2 (AI-vulnerable groups: persons with disabilities, people aged 65+, etc.)",
                "eu": "EAA Annex I Section III(b)(ii) information presented in an understandable way",
                "us": "WCAG 2.1 SC 2.2.1 Timing Adjustable (Title II standard) · 3.1.5 Reading Level (AAA, recommended)"
            },
            "why": "Long, expert-style generative AI answers are a major barrier for people with cognitive or learning disabilities and older users. Slow typists lose their session and must start over. Adjustable timing is a KWCAG audit item; plain language is a quality benchmark rather than a legal duty, but it is where much of the real-world friction occurs.",
            "first_step": "Add \"Plain language\" and \"Shorter\" buttons (or an equivalent setting) next to replies",
            "law_basis": "October 2026"
        },
        {
            "key": "a11y:a8",
            "diagnostic": "AI Accessibility Inspector",
            "number": 8,
            "question": "Do users with disabilities test your AI features before launch or major updates?",
            "options": [
                "Yes — at every launch and major update, across disability types",
                "Done once",
                "Never"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 35(1) (impact assessment, best-efforts duty — reflect AI-vulnerable groups) · Enforcement Decree Art. 28(1)(i)",
                "eu": "AI Act Art. 9(9) consideration of vulnerable groups in high-risk AI risk management (Annex III from 2027-12-02, Annex I from 2028-08-02) · EAA Art. 13(3) procedures to maintain conformity",
                "us": "No rule — NIST AI RMF 'MAP 5.2' stakeholder engagement (voluntary)"
            },
            "why": "Automated checks find only part of the problems. Where real users get stuck — conversation flow, failed speech recognition, overly long replies — only shows when people use it. An AI behaves differently after a model change even on the same screen, so one test is not enough. For high-impact AI, Korea's impact assessment (a best-efforts duty) is meant to reflect AI-vulnerable groups.",
            "first_step": "Test five core tasks with one or two users each with visual, hearing, physical and cognitive disabilities (recruit via disability organisations or specialist labs)",
            "law_basis": "October 2026"
        },
        {
            "key": "a11y:a9",
            "diagnostic": "AI Accessibility Inspector",
            "number": 9,
            "question": "When the AI cannot help, can disabled users reach a person through a channel they can use (text, phone, sign language, etc.)?",
            "options": [
                "Yes — a human handoff from any screen, through two or more channels such as text and phone",
                "Handoff exists but is hard to find or offers one channel only",
                "No channel other than the AI"
            ],
            "provisions": {
                "kr": "Enforcement Decree of Korea's Disability Discrimination Act Art. 14(6)(iv) (sign/text/voice support when apps fail) · KWCAG 2.2 7.2.2 findable help · Korea's Digital Inclusion Act Art. 4 (alternatives; best-efforts duty of the state)",
                "eu": "EAA Annex I Section III(d) support services (help desks, call centres) in accessible modes",
                "us": "ADA effective communication (28 CFR 35.160 — public entities) · Title III litigation risk"
            },
            "why": "Replacing human channels with chatbots and voicebots pushes disabled and older people who struggle with AI out of the service. Korea treats sign, text and voice support when an app fails as reasonable accommodation; the EU requires support services to give information in accessible ways.",
            "first_step": "Pin a \"Talk to a person\" button in the same place on every AI screen",
            "law_basis": "October 2026"
        },
        {
            "key": "a11y:a10",
            "diagnostic": "AI Accessibility Inspector",
            "number": 10,
            "question": "Do you publish accessibility information for the AI service (supported features, known limitations) and an accessibility contact point?",
            "options": [
                "Yes — accessibility page + contact point + response time published",
                "Contact email only",
                "Not published"
            ],
            "provisions": {
                "kr": "Enforcement Decree of Korea's Disability Discrimination Act Art. 14(6)(ii)(iii) (pre-install verification label and usage information for apps) · Korea's Digital Inclusion Act Art. 22(3) (no certification mark without certification; fine up to KRW 5m, Art. 37(2))",
                "eu": "EAA Art. 13(2) and Annex V service accessibility information (written and oral, in accessible form)",
                "us": "No publication rule — an accessibility statement and contact point are common good practice"
            },
            "why": "If you provide an EAA service to EU consumers, you must publish information explaining how the service meets the accessibility requirements (Art. 13(2), Annex V). Korea treats a label showing app conformity before installation as reasonable accommodation. Conversely, using an accessibility certification mark you have not been granted can be fined (Digital Inclusion Act Art. 37(2)(iii)).",
            "first_step": "Write an accessibility page: supported features, known limitations (e.g. speech-recognition accuracy), alternative routes, last review date",
            "law_basis": "October 2026"
        },
        {
            "key": "a11y:a11",
            "diagnostic": "AI Accessibility Inspector",
            "number": 11,
            "question": "When buying third-party AI tools (chatbot widgets, voicebots, AI contact-centre software), do you check their accessibility?",
            "options": [
                "Yes — we obtain an accessibility report (VPAT/ACR, etc.) and contract for fixes",
                "Verbal assurance only",
                "Not checked"
            ],
            "provisions": {
                "kr": "Korea's Disability Discrimination Act Art. 21(1) (the provider remains responsible for third-party tools) · Korea's Digital Inclusion Act Art. 23 (public bodies' preferential purchase of accessible products)",
                "eu": "EAA Art. 13(1) service provider's duty to design and provide accessibly · AI Act Art. 16(l) accessibility requirements for high-risk AI providers (Annex III from 2027-12-02, Annex I from 2028-08-02)",
                "us": "Section 508 (federal procurement) · ADA Title II rule (covers content and apps provided through contracts)"
            },
            "why": "Even with someone else's chatbot widget, your company is the one serving the customer. If the widget does not work with screen readers, the responsibility lands on you, not the widget maker. Without a fix obligation in the contract, you have no way to get it corrected.",
            "first_step": "Request an accessibility conformance report (VPAT/ACR against EN 301 549 or KWCAG) for every new AI tool",
            "law_basis": "October 2026"
        },
        {
            "key": "a11y:a12",
            "diagnostic": "AI Accessibility Inspector",
            "number": 12,
            "question": "Do you check whether your AI (speech recognition, face recognition, screening models, etc.) makes more errors for disabled or older people?",
            "options": [
                "Yes — accuracy is measured per group and large gaps are addressed",
                "Only when complaints come in",
                "Not checked"
            ],
            "provisions": {
                "kr": "Korea's Disability Discrimination Act Art. 4(1)(ii) (indirect discrimination) · Art. 15 (goods and services) · Korea's AI Basic Act Art. 35(1) (impact assessment, best-efforts — reflect AI-vulnerable groups)",
                "eu": "AI Act Art. 10(2)(f)(g) bias examination of high-risk AI data (Annex III from 2027-12-02, Annex I from 2028-08-02) · Art. 5(1)(b) ban on exploiting disability-related vulnerabilities (since 2025-02-02)",
                "us": "ADA non-discrimination (employment, services) · NIST AI RMF 'MEASURE 2.11' fairness (voluntary)"
            },
            "why": "Speech recognition tends to fail more for speakers with speech or hearing impairments and older speakers; face and pose recognition for wheelchair users and others. Applying the same rule to everyone can still be indirect discrimination if the outcome disadvantages disabled people (Korea's Disability Discrimination Act Art. 4(1)(ii)). The risk is highest in hiring and eligibility decisions.",
            "first_step": "Obtain test data for disability and age groups for each core AI feature (voice, images, etc. collected with consent)",
            "law_basis": "October 2026"
        },
        {
            "key": "compliance:c1",
            "diagnostic": "AI Compliance Check",
            "number": 1,
            "question": "Does your organization maintain an inventory of all AI systems it operates?",
            "options": [
                "Yes — documented and refreshed quarterly",
                "Partial — fragmented across teams",
                "No"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 33(1) advance review of high-impact status · Art. 34(1) item 5 document preparation and retention (the inventory is a prerequisite for both duties)",
                "eu": "EU AI Act Art. 49 registration of high-risk AI",
                "us": "NIST AI RMF 'Map' (voluntary)"
            },
            "why": "The law does not use the word \"inventory,\" but Art. 33(1) (advance review of high-impact status) and Art. 34(1) item 5 (preparation and retention of documents on measures taken) can be performed only if you know what you are using. It is the starting point for every follow-up action. (EU: Art. 49 registration duty)",
            "first_step": "Within 2 weeks, collect from each department the systems and external services with AI features (chatbots, recommendations, automated screening, etc.)",
            "law_basis": "October 2026"
        },
        {
            "key": "compliance:c2",
            "diagnostic": "AI Compliance Check",
            "number": 2,
            "question": "Do any of your AI systems fall under 'high-impact AI' (employment, credit, healthcare, education, public services)?",
            "options": [
                "None",
                "Yes — classified and labelled",
                "Yes — but not classified"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 2 item 4 definition of high-impact AI · Art. 33(1) advance review duty",
                "eu": "EU AI Act Annex III high-risk uses",
                "us": "NYC Local Law 144 (AEDT) · Colorado SB 26-189 'consequential decisions' (effective 2027-01-01)"
            },
            "why": "Art. 33(1) requires you to review, before providing AI, whether it is high-impact (hiring, lending, healthcare, education and other areas under Art. 2 item 4). Without classification, you cannot decide where to apply the Art. 34 duties (risk management, explanation, oversight). (EU: Annex III)",
            "first_step": "Compare each system in the inventory against the 10 areas in Art. 2 item 4 and mark its high-impact status",
            "law_basis": "October 2026"
        },
        {
            "key": "compliance:c3",
            "diagnostic": "AI Compliance Check",
            "number": 3,
            "question": "Have you ever conducted an impact assessment (rights, discrimination, privacy) before deploying an AI system?",
            "options": [
                "Performed for every system",
                "High-impact only",
                "Never"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 35(1) fundamental-rights impact assessment (best-efforts duty) · Art. 35(2) priority consideration in state-agency procurement",
                "eu": "EU AI Act Art. 27 fundamental rights impact assessment (FRIA)",
                "us": "NIST AI RMF 'Map/Measure' (voluntary) — Colorado's impact-assessment duty was repealed by SB 26-189"
            },
            "why": "Art. 35(1) provides that high-impact AI operators shall endeavor to assess in advance the impact on people's fundamental rights (best-efforts duty). There is no administrative fine for breach, but state agencies must give priority consideration to products that have undergone an impact assessment (Art. 35(2)), which directly affects public-sector business. (EU: Art. 27)",
            "first_step": "Select the one high-impact system with the most users",
            "law_basis": "October 2026"
        },
        {
            "key": "compliance:c4",
            "diagnostic": "AI Compliance Check",
            "number": 4,
            "question": "Do you display a notice (label) informing users they are 'interacting with AI'?",
            "options": [
                "Persistently across all AI surfaces",
                "On some screens only",
                "Not displayed"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 31(1) advance notice duty (administrative fine up to KRW 30 million, Art. 43(1) item 1)",
                "eu": "EU AI Act Art. 50(1) notice of AI interaction",
                "us": "Utah AI Policy Act · California B.O.T. Act (SB 1001)"
            },
            "why": "Art. 31(1) requires that users be informed in advance when products or services based on high-impact or generative AI are provided, and failure to do so is subject to an administrative fine (Art. 43(1) item 1, up to KRW 30 million). A government grace period applies, but this is the item you can close at the lowest cost. (EU: Art. 50)",
            "first_step": "List every screen where AI responds, recommends or decides (chatbot, support, automated screening results, etc.)",
            "law_basis": "October 2026"
        },
        {
            "key": "compliance:c5",
            "diagnostic": "AI Compliance Check",
            "number": 5,
            "question": "Do you apply watermarks or metadata marking to AI-generated synthetic content (image / video / audio)?",
            "options": [
                "C2PA-class standard watermark",
                "Text disclosure only",
                "Not applied",
                "Not applicable — we do not generate images, video or audio"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 31(2) labeling of generative AI outputs · Art. 31(3) notice for outputs difficult to distinguish from real ones",
                "eu": "EU AI Act Art. 50(2) marking of synthetic content (systems placed on the market before 2026-08-02: by 2026-12-02)",
                "us": "California AI Transparency Act (SB 942)"
            },
            "why": "Art. 31(2) requires that generative AI outputs be labeled as AI-generated, and Art. 31(3) requires clear notice for sound, images and video that are difficult to distinguish from real ones. Violations are subject to a fact-finding investigation and corrective order (Art. 40). (EU: Art. 50(2))",
            "first_step": "Survey whether the service generates images, video or audio and where they are distributed",
            "law_basis": "October 2026"
        },
        {
            "key": "compliance:c6",
            "diagnostic": "AI Compliance Check",
            "number": 6,
            "question": "Have you established human-in-the-loop oversight procedures for your AI systems?",
            "options": [
                "Documented + training complete",
                "Informal practice",
                "None"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 34(1) item 4 human oversight (mandatory)",
                "eu": "EU AI Act Art. 14 human oversight",
                "us": "NIST AI RMF 'Manage' (voluntary)"
            },
            "why": "Art. 34(1) item 4 requires high-impact AI operators to perform human oversight. After an incident, the first question asked is \"who could have stopped it?\" (EU: Art. 14)",
            "first_step": "Designate, in a one-page document, the oversight owner for each system and the authority to halt or override",
            "law_basis": "October 2026"
        },
        {
            "key": "compliance:c7",
            "diagnostic": "AI Compliance Check",
            "number": 7,
            "question": "Do you maintain a separate security/privacy policy for AI training and operational data?",
            "options": [
                "Dedicated AI data policy",
                "Embedded in general policy",
                "None"
            ],
            "provisions": {
                "kr": "Personal Information Protection Act (PIPA) Art. 28-2 pseudonymized information · Art. 37-2 automated decisions (linked to AI Basic Act Art. 34(1) item 1 risk management)",
                "eu": "GDPR Art. 22 · EU AI Act Art. 10 data governance",
                "us": "California CCPA/CPRA automated decision-making rules · Virginia VCDPA"
            },
            "why": "Data used to train and operate AI is directly subject to the Personal Information Protection Act (PIPA) (pseudonymized information, Art. 28-2; automated decisions, Art. 37-2). Without a standard, you cannot explain the source, retention and access rights of training data. (GDPR Art. 22, AI Act Art. 10)",
            "first_step": "Tabulate the source, type, retention period and access rights of the data that goes into AI",
            "law_basis": "October 2026"
        },
        {
            "key": "compliance:c8",
            "diagnostic": "AI Compliance Check",
            "number": 8,
            "question": "Do you perform regular bias audits on your AI systems?",
            "options": [
                "Quarterly",
                "Ad-hoc",
                "Never"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 34(1) item 1 establishment and operation of a risk management plan",
                "eu": "EU AI Act Art. 9 risk management · Art. 15 accuracy",
                "us": "NYC Local Law 144 annual bias audit"
            },
            "why": "The risk management plan under Art. 34(1) item 1 includes activities to find and reduce discrimination and error risks. Discriminatory outcomes lead directly to damages claims and administrative action. (EU: Art. 9, 15; New York City: annual bias audit duty for hiring AI)",
            "first_step": "Decide the systems to be tested and the protected variables (gender, age, etc.)",
            "law_basis": "October 2026"
        },
        {
            "key": "compliance:c9",
            "diagnostic": "AI Compliance Check",
            "number": 9,
            "question": "Can users request explanations or appeal AI-driven decisions?",
            "options": [
                "Published procedure in operation",
                "Internal procedure only",
                "None"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 34(1) item 2 explanation plan · item 3 user protection · PIPA Art. 37-2 right to explanation and to refuse",
                "eu": "EU AI Act Art. 86 right to explanation",
                "us": "Colorado SB 26-189 explanation of adverse outcomes within 30 days and human review (effective 2027-01-01)"
            },
            "why": "Art. 34(1) items 2 and 3 require a plan to explain the final result and main criteria of high-impact AI and a user protection plan, and PIPA Art. 37-2 provides the right to request an explanation of, and to refuse, automated decisions. Failing to answer is a disadvantage in disputes. (EU: Art. 86)",
            "first_step": "Publish an \"AI decision inquiry and objection\" channel (email or form) on the service screens and in the terms",
            "law_basis": "October 2026"
        },
        {
            "key": "compliance:c10",
            "diagnostic": "AI Compliance Check",
            "number": 10,
            "question": "Has the organization designated a Chief AI Officer or equivalent?",
            "options": [
                "Named and announced",
                "Held alongside another role",
                "Not designated"
            ],
            "provisions": {
                "kr": "Not a statutory duty (recommended) — an officer to oversee performance of the Art. 34 duties",
                "eu": "EU AI Act Art. 17 quality management system (assignment of responsibility)",
                "us": "OMB M-25-21 federal agency CAIO (recommended benchmark for the private sector)"
            },
            "why": "The law does not require it directly, but unless it is decided who performs the Art. 33 and 34 duties, none of them will move forward. It is also the first contact point regulators and counterparties look for. (EU: Art. 17 quality management system)",
            "first_step": "Appoint one executive-level person as AI officer and announce it internally",
            "law_basis": "October 2026"
        },
        {
            "key": "compliance:c11",
            "diagnostic": "AI Compliance Check",
            "number": 11,
            "question": "Is there a reporting pipeline for AI incidents and malfunctions?",
            "options": [
                "Regulator reporting line in place",
                "Internal reporting only",
                "None"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 34(1) item 1 risk management · item 3 user protection (for large-scale computing AI, Art. 32 safety incident response and submission of results)",
                "eu": "EU AI Act Art. 73 reporting of serious incidents",
                "us": "NIST AI RMF 'Manage' incident response (voluntary)"
            },
            "why": "Ordinary operators have no separate \"incident reporting\" provision, but the risk management and user protection under Art. 34(1) include response to malfunctions. Large-scale computing AI has a safety incident response framework and a duty to submit results under Art. 32. Slow response increases both harm and liability. (EU: Art. 73)",
            "first_step": "Write a definition of \"AI incident\" (malfunction, discriminatory outcome, personal data leak, etc.) and severity criteria",
            "law_basis": "October 2026"
        },
        {
            "key": "compliance:c12",
            "diagnostic": "AI Compliance Check",
            "number": 12,
            "question": "Has the organization undergone an external AI compliance audit or certification in the last 12 months?",
            "options": [
                "Holds ISO/IEC 42001 or equivalent",
                "Internal audit only",
                "None"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 30 support for safety and reliability verification and certification (voluntary)",
                "eu": "EU AI Act Art. 43 conformity assessment",
                "us": "NIST AI RMF 1.0 · ISO/IEC 42001 (voluntary certification)"
            },
            "why": "Art. 30 leaves verification and certification voluntary, but it is the strongest trust signal in counterparty and investor due diligence. In the US, the NIST AI RMF serves as the de facto benchmark. (EU: Art. 43)",
            "first_step": "Assess the current level through one internal audit",
            "law_basis": "October 2026"
        },
        {
            "key": "data-quality:d1",
            "diagnostic": "AI Data Quality Audit",
            "number": 1,
            "question": "What will the AI trained or evaluated on this data be used for?",
            "options": [
                "General business use — no significant decisions",
                "Not yet determined",
                "Significant decisions (hiring, lending, health, education)"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 2 item 4 (high-impact AI) · Art. 34(1) item 2 overview of training data (mandatory if high-impact)",
                "eu": "EU AI Act Art. 6 · Annex III — if high-risk, Art. 10 data governance applies (from 2027-12-02; Annex I products from 2028-08-02)",
                "us": "Colorado SB 26-189 'consequential decisions' (from 2027-01-01; developers must disclose training data categories)"
            },
            "why": "The same data practices carry different legal weight depending on what the AI is used for. For high-impact AI, Korea's AI Basic Act Art. 34(1) item 2 requires a plan to explain an overview of the training data, and EU providers of high-risk AI must meet the data quality criteria in Art. 10 (from 2027-12-02; Annex I products from 2028-08-02). This question reflects exposure, not the level of control.",
            "first_step": "For each AI system, write one line on which decision it supports and compare it with the areas listed in Art. 2 item 4",
            "law_basis": "October 2026"
        },
        {
            "key": "data-quality:d2",
            "diagnostic": "AI Data Quality Audit",
            "number": 2,
            "question": "Do you keep a register recording the source of every training and evaluation dataset (where, when and on what terms it was obtained)?",
            "options": [
                "Yes — source, date, terms and owner recorded for every dataset",
                "Only for the main datasets",
                "No record"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 34(1) item 2 overview of training data · Enforcement Decree Art. 25(1) item 2 (training data overview attached to a high-impact confirmation request)",
                "eu": "EU AI Act Art. 10(2)(b) collection processes and origin of data (high-risk, from 2027-12-02; Annex I products from 2028-08-02) · Art. 53(1)(d) public summary of training content (GPAI, since 2025-08-02)",
                "us": "California AB 2013 training data disclosure (in effect 2026-01-01, generative AI developers) · FTC orders to delete models built on improperly obtained data"
            },
            "why": "Without provenance you cannot check rights (Q3) or personal data (Q5), or remove problem data. High-impact AI must be able to explain an overview of its training data (Art. 34(1) item 2), and a request to the Ministry of Science and ICT to confirm high-impact status must attach one (Enforcement Decree Art. 25(1) item 2). The US FTC has ordered companies to delete models built on improperly obtained data (Everalbum, 2021).",
            "first_step": "Data team builds a dataset register within two weeks: name, source, collection date, method, terms of use, owner",
            "law_basis": "October 2026"
        },
        {
            "key": "data-quality:d3",
            "diagnostic": "AI Data Quality Audit",
            "number": 3,
            "question": "Have you checked, dataset by dataset, the right to use the data (licence, terms of use, copyright) and whether AI training is permitted?",
            "options": [
                "Yes — rights checked and recorded per dataset; training opt-outs honoured",
                "Checked for some datasets only",
                "Not checked"
            ],
            "provisions": {
                "kr": "Korea's Copyright Act Art. 35-5 fair use (no dedicated exception for AI training) · Ministry of Culture guide on fair use in generative AI training (2026-02)",
                "eu": "DSM Copyright Directive 2019/790 Art. 4(3) rights reservation (opt-out) · AI Act Art. 53(1)(c) copyright policy (GPAI)",
                "us": "17 U.S.C. §107 fair use — courts have reached differing outcomes on AI training"
            },
            "why": "Korea's Copyright Act has no exception specifically for AI training, so unlicensed training turns on a case-by-case fair use analysis (Art. 35-5). In the EU, once a rightsholder reserves rights in machine-readable form (Art. 4(3)), the text-and-data-mining exception no longer covers that content, and you need a licence to train on it. If a rights problem surfaces late, data removal, retraining and dispute costs arrive together.",
            "first_step": "Add \"licence / terms / training permitted\" columns to the dataset register (Q2); legal to complete the review within three weeks",
            "law_basis": "October 2026"
        },
        {
            "key": "data-quality:d4",
            "diagnostic": "AI Data Quality Audit",
            "number": 4,
            "question": "If you train a general-purpose AI (GPAI) model yourself and offer it in the EU, do you have a copyright policy and a public summary of training content?",
            "options": [
                "Yes — copyright policy + public summary using the official EU template",
                "In preparation",
                "No",
                "Not applicable — we do not train GPAI models ourselves or offer them in the EU"
            ],
            "provisions": {
                "kr": "No equivalent rule — in Korea, high-impact AI must explain a training data overview (Art. 34(1) item 2)",
                "eu": "EU AI Act Art. 53(1)(c)(d) (since 2025-08-02; models placed earlier by 2027-08-02) · Commission enforcement powers from 2026-08-02",
                "us": "California AB 2013 public training data summary (generative AI, in effect 2026-01-01)"
            },
            "why": "Providers placing GPAI models on the EU market must have a copyright policy and publish a summary of training content using the Commission template (published July 2025) (Art. 53(1)(c)(d)). Open-source models are not exempt from these two duties (Art. 53(2)). The Commission's enforcement powers apply from 2026-08-02.",
            "first_step": "ML team maps training data sources to the official EU template fields (data types, main collections, scraped domains, etc.)",
            "law_basis": "October 2026"
        },
        {
            "key": "data-quality:d5",
            "diagnostic": "AI Data Quality Audit",
            "number": 5,
            "question": "If you use pseudonymised personal data for training, do you have procedures for recording the purpose, storing the additional information separately and preventing re-identification?",
            "options": [
                "Yes — purpose/period logged, extra info kept apart, re-ID tested",
                "We pseudonymise, but records and checks are incomplete",
                "Raw data used without a confirmed legal basis, or not checked",
                "Not applicable — no personal data, or consent/other legal basis verified"
            ],
            "provisions": {
                "kr": "Korea's Personal Information Protection Act (PIPA) Art. 28-2 pseudonymised data · Art. 28-4 safeguards and records (kept 3+ years after destruction) · Art. 28-5 ban on re-identification",
                "eu": "GDPR Art. 4(5) pseudonymisation · Art. 89 safeguards for research · EDPB Opinion 28/2024 (AI models)",
                "us": "No federal rule — CCPA 'deidentified' requirements · FTC Act Section 5"
            },
            "why": "Under Korea's PIPA, pseudonymised data may be processed without consent for statistics, scientific research and similar purposes (Art. 28-2), but the additional information must be kept separately and processing records maintained (Art. 28-4), and processing aimed at identifying individuals is prohibited (Art. 28-5). Training on raw data without these controls or another legal basis such as consent may be treated as use beyond the original purpose (Art. 18), in which case a fine of up to 3% of total revenue may apply (Art. 64-2(1) item 1). For intentional or grossly negligent violations repeated within three years, or affecting 10 million or more people, the cap rises to 10% (Art. 64-2(2)). The PIPC fully revised its pseudonymisation guidelines in March 2026.",
            "first_step": "Privacy officer (CPO) samples the training data for personal information (two weeks)",
            "law_basis": "October 2026"
        },
        {
            "key": "data-quality:d6",
            "diagnostic": "AI Data Quality Audit",
            "number": 6,
            "question": "Have you compared, with numbers, whether training and evaluation data sufficiently represent your real users (age, gender, region, language, etc.)?",
            "options": [
                "Yes — compared numerically; gaps filled",
                "Roughly checked, no numerical comparison",
                "Not checked"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 34(1) item 1 risk management plan (high-impact) — the Act sets no representativeness criteria",
                "eu": "EU AI Act Art. 10(3)(4) sufficiently representative, reflecting the setting of use (high-risk providers, from 2027-12-02; Annex I products from 2028-08-02)",
                "us": "NYC Local Law 144 bias audit (hiring AI) · NIST AI RMF (voluntary)"
            },
            "why": "Groups that are under-represented in the data get worse performance and less favourable outcomes. EU providers of high-risk AI must use data that is \"sufficiently representative\" and reflects the geographical and contextual setting of use (Art. 10(3)(4), from 2027-12-02; Annex I products from 2028-08-02). In Korea, high-impact AI must address this risk in its risk management plan (Art. 34(1) item 1).",
            "first_step": "Define your actual user distribution (age, gender, region, language, device, etc.) and tabulate it against the training and evaluation data",
            "law_basis": "October 2026"
        },
        {
            "key": "data-quality:d7",
            "diagnostic": "AI Data Quality Audit",
            "number": 7,
            "question": "Do you check the training data itself for bias (imbalanced samples or labels across groups, proxy variables, etc.), with rules for using sensitive data to do so?",
            "options": [
                "Yes — bias checks + sensitive-data use and deletion rules",
                "We check, but have no rules on sensitive data",
                "No data bias checks"
            ],
            "provisions": {
                "kr": "Korea's PIPA Art. 23 sensitive data (separate consent or legal basis required) · AI Basic Act Art. 34(1) item 1 (high-impact)",
                "eu": "EU AI Act Art. 10(2)(f)(g) examination and mitigation of bias (high-risk, from 2027-12-02; Annex I products from 2028-08-02) · Art. 4a special-category data for bias detection (new under the Omnibus)",
                "us": "NYC Local Law 144 impact ratios by category · NIST SP 1270 on managing bias (voluntary)"
            },
            "why": "Bias usually enters through the data before the model. EU providers of high-risk AI must examine data for possible biases and take measures to mitigate them (Art. 10(2)(f)(g), from 2027-12-02; Annex I products from 2028-08-02). Where sensitive data is needed to detect bias, the new Art. 4a permits it only under strict conditions (strictly necessary, no transfer to third parties, deletion afterwards, reasons recorded). In Korea, sensitive data may be processed only with separate consent or a legal basis (Art. 23).",
            "first_step": "ML team drafts a checklist covering sample counts and label ratios per group and candidate proxy variables",
            "law_basis": "October 2026"
        },
        {
            "key": "data-quality:d8",
            "diagnostic": "AI Data Quality Audit",
            "number": 8,
            "question": "Does your labelling (annotation) work have written guidelines, sample-based QA and inter-annotator agreement measurement?",
            "options": [
                "Yes — guidelines + sample QA + agreement measured",
                "Guidelines only",
                "No set criteria"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 34(1) item 1 risk management (high-impact) · NIA AI training data quality management guideline (voluntary) — no statutory labelling standard",
                "eu": "EU AI Act Art. 10(2)(c) data preparation such as annotation, labelling and cleaning (high-risk, from 2027-12-02; Annex I products from 2028-08-02)",
                "us": "No rule — ISO/IEC 5259 series · NIST AI RMF (voluntary)"
            },
            "why": "If labels are wrong, the AI learns wrong answers as correct. Outsourced labelling is especially prone to drift between annotators. For high-risk AI in the EU, data preparation such as labelling and cleaning must be managed as part of data governance practices (Art. 10(2)(c), from 2027-12-02; Annex I products from 2028-08-02).",
            "first_step": "Write guidelines within a week covering label definitions, edge cases and examples",
            "law_basis": "October 2026"
        },
        {
            "key": "data-quality:d9",
            "diagnostic": "AI Data Quality Audit",
            "number": 9,
            "question": "Do you write a datasheet for each dataset (purpose, composition, collection method, preprocessing, limitations) and update it with each version?",
            "options": [
                "Yes — every dataset, updated with each version",
                "Some datasets only, not kept current",
                "None"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 34(1) item 5 documentation and retention · Enforcement Decree Art. 27(2) records kept 5 years (high-impact)",
                "eu": "EU AI Act Art. 11 · Annex IV 2(d) datasheets (provenance, selection, labelling, cleaning) (high-risk, from 2027-12-02; Annex I products from 2028-08-02)",
                "us": "Colorado SB 26-189 developer-to-deployer documentation of training data categories (from 2027-01-01) · California AB 2013"
            },
            "why": "When people move on, knowledge of a dataset's limitations and preprocessing leaves with them. High-impact AI operators in Korea must keep documentary evidence of their measures for five years (Enforcement Decree Art. 27(2)), and EU technical documentation for high-risk AI includes datasheets (Annex IV 2(d), from 2027-12-02; Annex I products from 2028-08-02). Datasheets are also among the first documents customers and investors ask for in due diligence.",
            "first_step": "Create a one-page datasheet template: purpose, composition, source, collection period, preprocessing, labelling, known limitations, rights",
            "law_basis": "October 2026"
        },
        {
            "key": "data-quality:d10",
            "diagnostic": "AI Data Quality Audit",
            "number": 10,
            "question": "Is your evaluation and test data kept separate from training data, and does it include cases from the real operating environment?",
            "options": [
                "Yes — stored separately + overlap checks + real-world cases included",
                "Separated only",
                "Same data used for training and evaluation"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 34(1) item 1 risk management (high-impact) — no statutory standard for evaluation data",
                "eu": "EU AI Act Art. 10(1) training, validation and testing data sets · Art. 15 accuracy (high-risk, from 2027-12-02; Annex I products from 2028-08-02)",
                "us": "No rule — NIST AI RMF (voluntary)"
            },
            "why": "Evaluation data that overlaps with training data inflates performance. If those figures appear in customer contracts or product claims, they can lead to disputes over misleading statements. High-risk AI in the EU must be developed with training, validation and testing data sets and must declare accuracy metrics in its instructions for use (Art. 10(1), Art. 15; from 2027-12-02; Annex I products from 2028-08-02).",
            "first_step": "Move evaluation data to a separate store with separate access rights",
            "law_basis": "October 2026"
        },
        {
            "key": "data-quality:d11",
            "diagnostic": "AI Data Quality Audit",
            "number": 11,
            "question": "Do you manage, per dataset, retention periods, deletion dates and versions (which model was trained on which data)?",
            "options": [
                "Yes — retention and deletion schedule + model-to-data version links",
                "Only versions or only retention",
                "Not managed"
            ],
            "provisions": {
                "kr": "Korea's PIPA Art. 21 destruction · Art. 28-4(2) processing period for pseudonymised data · AI Basic Act Enforcement Decree Art. 27(2) 5-year retention (high-impact)",
                "eu": "GDPR Art. 5(1)(e) storage limitation · AI Act Art. 18 technical documentation kept 10 years (high-risk, from 2027-12-02; Annex I products from 2028-08-02)",
                "us": "CCPA retention-period disclosure · FTC orders (deletion of improperly obtained data and models)"
            },
            "why": "Under Korea's PIPA, personal data must be destroyed without delay once its purpose is achieved (Art. 21), while records for high-impact AI must be kept for five years (Enforcement Decree Art. 27(2)). If you cannot separate what must be deleted from what must be kept, you risk breaching both. Without model-to-data links, you cannot scope retraining when a deletion request or rights dispute arrives.",
            "first_step": "Add retention period, scheduled deletion date and legal hold columns to the dataset register",
            "law_basis": "October 2026"
        },
        {
            "key": "data-quality:d12",
            "diagnostic": "AI Data Quality Audit",
            "number": 12,
            "question": "Do you regularly monitor whether production input data is drifting away from the training data?",
            "options": [
                "Yes — metrics and alert thresholds + re-evaluation on breach",
                "Occasional manual checks",
                "Not monitored"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 34(1) item 1 — operating the risk management plan (high-impact)",
                "eu": "EU AI Act Art. 72 post-market monitoring · Art. 26(4) deployer input data relevance (high-risk, from 2027-12-02; Annex I products from 2028-08-02)",
                "us": "No rule — NIST AI RMF (voluntary)"
            },
            "why": "When your user base, seasons or products change, input data shifts and the performance measured at launch quietly erodes. EU providers of high-risk AI must run post-market monitoring (Art. 72), and deployers must ensure that input data under their control is relevant and sufficiently representative for the intended purpose (Art. 26(4)). For high-risk AI, both duties apply from 2027-12-02 (2028-08-02 for Annex I products).",
            "first_step": "Pick 5–10 key input features and compute their distribution shift against training data every week",
            "law_basis": "October 2026"
        },
        {
            "key": "ethics:e1",
            "diagnostic": "AI Ethics Test",
            "number": 1,
            "question": "Has your company set out, in writing, the ethics principles it follows when developing or using AI?",
            "options": [
                "Yes — written, approved by management, shared with all staff",
                "Only a draft or a website statement",
                "No"
            ],
            "provisions": {
                "kr": "Korea AI Basic Act Art. 27 ethics principles (issued by government; voluntary for companies) · Korea AI Ethics Principles (adopted Aug 2026, non-binding)",
                "eu": "EU AI Act Art. 95(2)(a) voluntary codes of conduct — HLEG Ethics Guidelines for Trustworthy AI (2019)",
                "us": "No statutory rule — NIST AI RMF GOVERN 1.2 (voluntary) · OECD AI Principles (updated 2024)"
            },
            "why": "Ethics principles are not a legal duty (Art. 27 of Korea's AI Basic Act is the basis for the government to issue them). But every other item here — review body, speak-up channel, training, vendor selection — is judged against them. Without principles, each team decides the same case differently. Korea's government adopted its AI Ethics Principles (3 values, 7 principles) on 21 August 2026.",
            "first_step": "Draft a one-page company policy based on the seven Korea AI Ethics Principles (OECD principles if you operate mainly abroad) — 2 weeks",
            "law_basis": "October 2026"
        },
        {
            "key": "ethics:e2",
            "diagnostic": "AI Ethics Test",
            "number": 2,
            "question": "Do you keep a list of uses for which you will never use AI (red lines), and check it when approving new AI?",
            "options": [
                "Yes — a list exists and is checked at approval",
                "A list exists but is not checked at approval",
                "No"
            ],
            "provisions": {
                "kr": "Korea Sexual Violence Punishment Act Art. 14-2 (sexual deepfakes are a crime) · AI Basic Act has no prohibited list · Ethics Principles: accountability (misuse list)",
                "eu": "EU AI Act Art. 5 prohibited practices (since 2025-02-02; non-consensual intimate deepfakes and CSAM generation from 2026-12-02)",
                "us": "No federal prohibited list — FTC Act Section 5 (unfair or deceptive practices)"
            },
            "why": "Since 2 February 2025 the EU has banned AI such as subliminal manipulation, exploitation of vulnerabilities, social scoring and emotion recognition at work or school, with the highest fine tier in Art. 99 (up to EUR 35m or 7% of worldwide turnover). From 2 December 2026 the list also covers AI that generates non-consensual intimate images or child sexual abuse material (Art. 5(1)(ba)(bb)). Korea's AI Basic Act has no banned list, but creating or distributing sexual deepfakes is a crime under Art. 14-2 of the Sexual Violence Punishment Act. Red lines are the cheapest control: you decide in advance what you will not do.",
            "first_step": "Combine the EU Art. 5 list with your own principles into a red-line list of no more than 10 items — 1 week",
            "law_basis": "October 2026"
        },
        {
            "key": "ethics:e3",
            "diagnostic": "AI Ethics Test",
            "number": 3,
            "question": "Do you have a committee or designated body that reviews AI ethics issues?",
            "options": [
                "Yes — includes outside members and an ethics expert, meets regularly",
                "Internal staff only (no outside members)",
                "No"
            ],
            "provisions": {
                "kr": "Korea AI Basic Act Art. 28 private autonomous AI ethics committee (optional — if set up: not single-gender, must include an ethics expert and an outsider)",
                "eu": "No requirement — HLEG Ethics Guidelines · ALTAI (voluntary)",
                "us": "No requirement — NIST AI RMF GOVERN 2.3 · 3.1 (voluntary)"
            },
            "why": "Art. 28 of Korea's AI Basic Act says AI businesses \"may\" set up a private autonomous AI ethics committee — it is optional. If you do set one up, it may not be single-gender and must include both a person able to assess social and ethical soundness and a person from outside the organisation (Art. 28(3)). Without a decision-maker, issues get deferred and accountability is diluted.",
            "first_step": "Form a body of about five: business, technology, legal and at least one outside ethics expert, gender-balanced",
            "law_basis": "October 2026"
        },
        {
            "key": "ethics:e4",
            "diagnostic": "AI Ethics Test",
            "number": 4,
            "question": "Must new AI pass an ethics review before launch or adoption, and can that review stop it or require changes?",
            "options": [
                "Yes — review is mandatory and can stop or change the project",
                "Reviewed, but advice only",
                "Only reviewed after something goes wrong",
                "No review"
            ],
            "provisions": {
                "kr": "Korea AI Basic Act Art. 28(2) committee tasks (checking adherence, reviewing processes and results — voluntary)",
                "eu": "For high-risk AI: Art. 9 risk management and Art. 17 quality management (from 2027-12-02 Annex III / 2028-08-02 Annex I) — an ethics gate as such is voluntary",
                "us": "NIST AI RMF GOVERN 1.3 · 4.1 (voluntary)"
            },
            "why": "A review body achieves little if nobody has to follow its findings. Put the review into the launch gate and give it the power to stop anything that crosses a red line. For EU high-risk AI, these decisions must be documented within your risk and quality management systems (from 2 December 2027 for Annex III, 2 August 2028 for Annex I products).",
            "first_step": "Add an \"ethics review passed\" step to the launch and procurement process; no sign-off, no release",
            "law_basis": "October 2026"
        },
        {
            "key": "ethics:e5",
            "diagnostic": "AI Ethics Test",
            "number": 5,
            "question": "Do you have a way to bring the views of people affected by your AI (customers, staff, older people, people with disabilities) into design and operation?",
            "options": [
                "Yes — regularly, and we record what we changed",
                "Occasional surveys or interviews",
                "No"
            ],
            "provisions": {
                "kr": "Korea AI Basic Act Art. 3(5) participation of AI-vulnerable groups (best-efforts duty of the state) · Art. 35(1) impact assessments to reflect them (best efforts)",
                "eu": "EU AI Act Art. 95(2)(d)(e) stakeholder participation and vulnerable groups (voluntary codes)",
                "us": "NIST AI RMF GOVERN 5.1 external feedback (voluntary)"
            },
            "why": "Art. 3(5) of Korea's AI Basic Act asks the government to make efforts to involve AI-vulnerable groups (including people with disabilities and people aged 65+, Enforcement Decree Art. 1-2); it does not bind companies. However, impact assessments for high-impact AI (Art. 35(1), best efforts) are meant to reflect those groups' needs, so a record of stakeholder input becomes direct evidence for that assessment.",
            "first_step": "List the groups affected by each main AI service, checking whether older people and people with disabilities are included",
            "law_basis": "October 2026"
        },
        {
            "key": "ethics:e6",
            "diagnostic": "AI Ethics Test",
            "number": 6,
            "question": "Can staff raise AI ethics or legal concerns anonymously, with written protection against retaliation?",
            "options": [
                "Yes — anonymous channel, anti-retaliation rule and response deadlines",
                "A channel exists, but no AI handling rules or protection",
                "No"
            ],
            "provisions": {
                "kr": "Korea Public Interest Whistleblower Protection Act (AI Basic Act not a listed law; PIPA breaches are) · AI Basic Act Art. 40(1) fact-finding (only for reported breaches of Arts. 31(2)–(3), 32(1)–(2), 34(1))",
                "eu": "EU AI Act Art. 87 — Whistleblower Directive (EU) 2019/1937 applies (from 2026-08-02); internal channels mandatory at 50+ workers (Directive Art. 8)",
                "us": "California SB 53 (frontier AI developers only, effective 2026-01-01) · otherwise NIST (voluntary)"
            },
            "why": "From 2 August 2026, reports of EU AI Act breaches are protected under the EU Whistleblower Directive, and legal entities with 50 or more workers must have internal reporting channels. In Korea, the AI Basic Act is not on the whistleblower-protection list, but breaches of the Personal Information Protection Act are, and a report or complaint about a breach of the AI Basic Act's labelling (Art. 31(2)–(3)), large-compute safety (Art. 32(1)–(2)) or high-impact duties (Art. 34(1)) can trigger fact-finding by the Ministry of Science and ICT (Art. 40(1)); the ethics provisions (Arts. 27–29) are not covered. Hearing it internally first is your cheapest early warning.",
            "first_step": "Add an \"AI-related\" category to your existing ethics or fraud hotline — 1 week",
            "law_basis": "October 2026"
        },
        {
            "key": "ethics:e7",
            "diagnostic": "AI Ethics Test",
            "number": 7,
            "question": "Do staff who work with AI receive role-appropriate training (limits, risks, ethics), with completion records?",
            "options": [
                "Yes — role-based, at least yearly, with records",
                "One general session for everyone",
                "No training"
            ],
            "provisions": {
                "kr": "No corporate training duty — Korea AI Basic Act Art. 28(2) item 4 committee ethics training (voluntary) · Ethics Principles: user responsibilities",
                "eu": "EU AI Act Art. 4 AI literacy (since 2025-02-02; since the July 2026 amendment, a duty to take supporting measures)",
                "us": "No requirement — NIST AI RMF GOVERN 2.2 (voluntary)"
            },
            "why": "EU AI Act Art. 4 requires providers and deployers to take measures to support their staff's AI literacy. The July 2026 amendment (Regulation (EU) 2026/1744) makes clear that no specific level must be guaranteed, but the duty to take measures remains. Korea imposes no training duty on companies, though its 2026 Ethics Principles expect users, too, to check AI output themselves. Training records are the easiest proof that you acted when something goes wrong.",
            "first_step": "Split staff into three groups (everyday users, people who make decisions with AI, developers) and set content for each",
            "law_basis": "October 2026"
        },
        {
            "key": "ethics:e8",
            "diagnostic": "AI Ethics Test",
            "number": 8,
            "question": "When choosing external AI (models, APIs, solutions), do you check the vendor's ethics and safety policies and reflect them in the contract?",
            "options": [
                "Yes — checked at selection, with information and incident-notice clauses",
                "Checked at selection only, no contract clauses",
                "Not checked",
                "Not applicable — we use no external AI; everything is built in-house"
            ],
            "provisions": {
                "kr": "No statutory rule — Ethics Principles: accountability (no accountability gaps when several parties are involved; voluntary)",
                "eu": "EU AI Act Art. 25(4) written agreement between a high-risk AI provider and its suppliers (from 2027-12-02 Annex III / 2028-08-02 Annex I)",
                "us": "NIST AI RMF GOVERN 6.1 · 6.2 third-party risk (voluntary)"
            },
            "why": "Even when an incident starts in a vendor's model, the company that offers the service answers to the customer. If you provide high-risk AI in the EU, you must agree in writing with model and component suppliers on the information and technical help you need (Art. 25(4), from 2 December 2027 for Annex III, 2 August 2028 for Annex I products). Korea's 2026 Ethics Principles (accountability) likewise call for dividing roles so that no accountability gap arises when several parties are involved.",
            "first_step": "Write a 10-question vendor checklist (training-data sources, whether your inputs are used for training, prohibited uses, incident notice)",
            "law_basis": "October 2026"
        },
        {
            "key": "ethics:e9",
            "diagnostic": "AI Ethics Test",
            "number": 9,
            "question": "Do you check that the \"ethical AI\" or \"responsible AI\" claims on your website, ads and proposals match what you actually do?",
            "options": [
                "Yes — checked against evidence before publication",
                "Sometimes",
                "No",
                "Not applicable — we make no public AI ethics claims"
            ],
            "provisions": {
                "kr": "Korea Act on Fair Labeling and Advertising Art. 3 (false, exaggerated or deceptive advertising)",
                "eu": "Unfair Commercial Practices Directive 2005/29/EC Art. 6 (misleading actions)",
                "us": "FTC Act Section 5 deception — FTC \"Operation AI Comply\" (2024)"
            },
            "why": "Unsupported \"ethical AI\" or \"bias-free\" claims are an advertising-law problem, not just an ethics one. Korea (Fair Labeling and Advertising Act Art. 3), the EU (Unfair Commercial Practices Directive) and the US (FTC Act Section 5) all sanction false or deceptive claims, and the FTC ran a dedicated sweep against deceptive AI claims in 2024. Marketing that runs ahead of practice can destroy trust overnight.",
            "first_step": "Collect every public AI ethics and safety claim into one list — 1 week",
            "law_basis": "October 2026"
        },
        {
            "key": "ethics:e10",
            "diagnostic": "AI Ethics Test",
            "number": 10,
            "question": "Do you regularly check whether your ethics principles are actually followed, and report the results to management?",
            "options": [
                "Yes — at least yearly, using a checklist, reported to management",
                "Occasionally, with no fixed cycle",
                "No"
            ],
            "provisions": {
                "kr": "Ethics Principles self-check list (to be issued by the Ministry of Science and ICT — timing unconfirmed) · Korea AI Basic Act Art. 29 support for voluntary codes",
                "eu": "HLEG ALTAI self-assessment list (2020, voluntary) · ISO/IEC 42001 (voluntary certification)",
                "us": "NIST AI RMF GOVERN 1.5 periodic review (voluntary)"
            },
            "why": "Principles, committees and training fade into formality within a year or two if nobody checks them. Korea's government has said it will publish a self-check list with concrete items, and both the EU's ALTAI and ISO/IEC 42001 assume periodic review. The results are ready-made material for customer and investor due diligence.",
            "first_step": "Save this assessment as your baseline and repeat it with the same questions every year",
            "law_basis": "October 2026"
        },
        {
            "key": "ethics:e11",
            "diagnostic": "AI Ethics Test",
            "number": 11,
            "question": "When you introduce AI that affects staff (performance evaluation, monitoring, scheduling), do you inform and consult employees or their representatives in advance?",
            "options": [
                "Yes — explained and consulted before rollout, with records",
                "Announced only after rollout",
                "Not informed",
                "Not applicable — no AI affects our staff"
            ],
            "provisions": {
                "kr": "Korea Worker Participation Act Art. 20(1) items 9 and 14: consultation on new technology and monitoring equipment (labour-management council at 30+ employees)",
                "eu": "EU AI Act Art. 26(7) inform workers' representatives and affected workers before using high-risk AI at work (from 2027-12-02)",
                "us": "NYC Local Law 144: notice and annual bias audit for automated hiring and promotion tools (AEDT)"
            },
            "why": "In Korea, workplaces with 30 or more regular employees must have a labour-management council, and introducing new technology or installing employee-monitoring equipment are matters for consultation (Worker Participation Act Arts. 4 and 20). In the EU, employers must inform workers' representatives and affected workers before using high-risk AI at work (Art. 26(7), from 2 December 2027). In New York City, automated hiring and promotion tools require an annual bias audit and advance notice.",
            "first_step": "List every AI used in HR, time and attendance, or monitoring — 1 week",
            "law_basis": "October 2026"
        },
        {
            "key": "genai-label:g1",
            "diagnostic": "Generative AI Labelling Audit",
            "number": 1,
            "question": "When users interact with a generative AI (chatbot, document, image generator), is an 'interacting with AI' notice displayed?",
            "options": [
                "Persistently on every screen",
                "Only on first entry",
                "Not displayed"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 31(1) advance notice duty (administrative fine up to KRW 30 million, Art. 43(1) item 1)",
                "eu": "EU AI Act Art. 50(1) notice of AI interaction",
                "us": "Utah AI Policy Act · California B.O.T. Act (SB 1001)"
            },
            "why": "Art. 31(1) requires that users be informed in advance when products or services based on generative or high-impact AI are provided, and failure to do so is subject to an administrative fine (Art. 43(1) item 1). If the notice appears only on the first screen, users who arrive midway (shared links, notifications, app widgets) will not know. (EU: Art. 50(1))",
            "first_step": "List every entry point where AI responds or generates (web, app, messenger bot, widget, API demo)",
            "law_basis": "October 2026"
        },
        {
            "key": "genai-label:g2",
            "diagnostic": "Generative AI Labelling Audit",
            "number": 2,
            "question": "Do you mark AI-generated text, image, video, and audio as 'AI-generated'?",
            "options": [
                "Marked across all media",
                "Only image / video",
                "Not marked"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 31(2) labeling of generative AI outputs",
                "eu": "EU AI Act Art. 50(2) marking of synthetic content",
                "us": "California AI Transparency Act (SB 942, operative 2026-08-02)"
            },
            "why": "Art. 31(2) requires that generative AI outputs be labeled as AI-generated. The guidelines accept, in addition to labels people can see, invisible watermarks that can be checked by machine. Violations are subject to a fact-finding investigation and corrective order (Art. 40). Note: this does not apply to media you do not generate (for example, if you operate only a text chatbot). (EU: Art. 50(2))",
            "first_step": "Map the media your service produces (text, images, video, audio) and the routes by which they leave your service (download, sharing, API)",
            "law_basis": "October 2026"
        },
        {
            "key": "genai-label:g3",
            "diagnostic": "Generative AI Labelling Audit",
            "number": 3,
            "question": "Do synthetic images and videos embed machine-readable metadata such as C2PA?",
            "options": [
                "C2PA across all assets",
                "Partial C2PA coverage",
                "No metadata",
                "Not applicable — we do not generate images or video"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 31(2) + guidelines (invisible watermarks and machine-readable marks accepted)",
                "eu": "EU AI Act Art. 50(2) machine-readable format (systems placed on the market before 2026-08-02: by 2026-12-02, Art. 111(4))",
                "us": "California AI Transparency Act (SB 942) latent disclosure"
            },
            "why": "EU AI Act Art. 50(2) requires synthetic outputs to be marked \"in a machine-readable format,\" and California SB 942 requires large generative AI providers to include a latent disclosure (provider name, creation time, unique identifier, etc.). A mark that people can see disappears with a single crop, so platforms and media outlets need metadata to verify provenance automatically. Note: not applicable if you do not generate images or video.",
            "first_step": "Decide on a standard method such as C2PA (Content Credentials) and the issuer of the signing certificate",
            "law_basis": "October 2026"
        },
        {
            "key": "genai-label:g4",
            "diagnostic": "Generative AI Labelling Audit",
            "number": 4,
            "question": "When generating or distributing deepfakes (synthesis of real people's faces / voices), do you apply a separate 'deepfake' label?",
            "options": [
                "Labelled + subject consent on file",
                "Label only",
                "Not labelled",
                "Not applicable — no synthesis of real people"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 31(3) notice and labeling of outputs difficult to distinguish from real ones · Sexual Violence Punishment Act Art. 14-2 (false video material) · Public Official Election Act Art. 82-8",
                "eu": "EU AI Act Art. 50(4) deepfake disclosure · Art. 5(1)(ba) ban on AI that generates realistic intimate images of an identifiable person without consent (from 2026-12-02)",
                "us": "TAKE IT DOWN Act (2025) · California AB 2355 · Tennessee ELVIS Act"
            },
            "why": "Art. 31(3) requires that when virtual sound, images or video that are difficult to distinguish from real ones are provided, users must be clearly notified and the output labeled. The guidelines direct that deepfakes be labeled in a way people can recognize immediately, rather than by an invisible watermark. Synthesizing a real person without their consent can be subject to criminal penalties whether or not a label is applied (false video material under the Sexual Violence Punishment Act, deepfakes during election periods). (EU: Art. 50(4). From 2026-12-02, Art. 5(1)(ba) also prohibits AI that generates realistic intimate images of an identifiable person without consent; a general-purpose generator is covered if such output is reasonably foreseeable and it lacks reasonable and adequate safeguards — Art. 5(1a).)",
            "first_step": "Check whether you have features that synthesize real people (face swap, voice cloning) and where they are used",
            "law_basis": "October 2026"
        },
        {
            "key": "genai-label:g5",
            "diagnostic": "Generative AI Labelling Audit",
            "number": 5,
            "question": "Are responses from text-based AI (chatbots) marked with an 'AI-generated' indicator?",
            "options": [
                "Header / footer mark on every response",
                "Disclosed once per session",
                "Not marked",
                "Not applicable — no chatbot (conversational text AI)"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 31(1) advance notice · Art. 31(2) output labeling",
                "eu": "EU AI Act Art. 50(1) · Art. 50(4) text published to inform the public on matters of public interest",
                "us": "Utah AI Policy Act · California B.O.T. Act (SB 1001)"
            },
            "why": "Chatbot answers are easily copied or captured and spread elsewhere. A small label on each response makes the Art. 31(1) notice easier to prove and reduces disputes on screens such as support or guidance, where people may mistake the answer for a human one. For AI-generated text published to inform the public on matters of public interest, EU Art. 50(4) requires separate disclosure.",
            "first_step": "Add an \"AI answer\" label under each response bubble by default",
            "law_basis": "October 2026"
        },
        {
            "key": "genai-label:g6",
            "diagnostic": "Generative AI Labelling Audit",
            "number": 6,
            "question": "Do AI text-to-speech outputs include audible or visual 'AI voice' disclosures?",
            "options": [
                "Audible + visual",
                "Visual subtitle only",
                "None",
                "Not applicable — we do not use AI voice"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 31(2) output labeling · Art. 31(3) sound difficult to distinguish from real",
                "eu": "EU AI Act Art. 50(2) and (4)",
                "us": "FCC 2024 declaratory ruling (AI-voice calls are \"artificial voice\" and require prior consent) · Tennessee ELVIS Act"
            },
            "why": "A synthetic voice that is difficult to distinguish from a real human voice is subject to the clear notice requirement of Art. 31(3). In calls and voice guidance that have no screen, the notice must be spoken for users to know. In the US, calls using an AI voice are treated as \"artificial voice\" under the TCPA and require prior consent (FCC 2024). Note: not applicable if you do not use voice synthesis.",
            "first_step": "List the places where AI voice is used (call center, announcements, video narration, in-app read-aloud)",
            "law_basis": "October 2026"
        },
        {
            "key": "genai-label:g7",
            "diagnostic": "Generative AI Labelling Audit",
            "number": 7,
            "question": "Do you operate explicit disclosure rules for AI-generated content used in election or political ads?",
            "options": [
                "Policy in operation",
                "Manual review only",
                "No policy",
                "Not applicable — the service cannot produce election or political content"
            ],
            "provisions": {
                "kr": "Public Official Election Act Art. 82-8 (deepfake campaigning) · AI Basic Act Art. 31(3)",
                "eu": "Regulation (EU) 2024/900 political advertising transparency · EU AI Act Art. 50(4)",
                "us": "California AB 2355 · Texas Election Code §255.004 · FEC 2024 interpretive rule (applies the existing fraudulent misrepresentation ban; not an AI disclosure rule)"
            },
            "why": "Public Official Election Act Art. 82-8 prohibits campaigning that uses deepfake video and similar content from 90 days before election day through election day, and requires disclosure of AI synthesis in other periods. Violations are subject to criminal penalties, and if your service was used as the tool, you as the operator will find it hard to stay out of investigations and complaints. Even if your service does not handle election content, it is safer to state in a policy that it does not.",
            "first_step": "Write a one-page policy on how election and political generation requests are handled (allow, restrict, block)",
            "law_basis": "October 2026"
        },
        {
            "key": "genai-label:g8",
            "diagnostic": "Generative AI Labelling Audit",
            "number": 8,
            "question": "Can users request 'origin verification' or 'provenance tracing' on AI outputs?",
            "options": [
                "Self-service page provided",
                "Email request only",
                "Not available"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 31(2) effectiveness of labeling (guidelines: provide a way to verify invisible marks)",
                "eu": "EU AI Act Art. 50(2) detectability",
                "us": "California AI Transparency Act (SB 942) duty to provide a free AI detection tool"
            },
            "why": "An invisible watermark is meaningful only if there is a way to check it. California SB 942 requires large generative AI providers to offer a free detection tool. If media outlets, platforms and victims have no way to verify authenticity, you will have less to stand on when you need to explain a misuse incident.",
            "first_step": "Set up a verification page that tells users whether an uploaded file carries your mark (or point users to a public C2PA verification tool)",
            "law_basis": "October 2026"
        },
        {
            "key": "genai-label:g9",
            "diagnostic": "Generative AI Labelling Audit",
            "number": 9,
            "question": "Do you disclose to users whether unlicensed training data (e.g., web scraping) is used?",
            "options": [
                "Transparency page disclosure",
                "Single line in ToS",
                "Not disclosed"
            ],
            "provisions": {
                "kr": "No statutory disclosure duty · no TDM exception under the Copyright Act (rights clearance needed)",
                "eu": "EU AI Act Art. 53(1)(d) summary of training content for general-purpose AI",
                "us": "California AB 2013 training data transparency (effective 2026-01-01)"
            },
            "why": "Korea does not legally require disclosure of training data, but the Copyright Act still has no text and data mining (TDM) exception, so the risk of rights disputes remains. The EU requires providers of general-purpose AI models to publish a summary of training content, and California AB 2013 requires generative AI developers to disclose information about their training data. Note: if you use only external models and have no model of your own, it is enough to point to the model you use and its provider's public materials.",
            "first_step": "Document the models you use (own and external) and the source categories of training data (licensed, public data, customer data)",
            "law_basis": "October 2026"
        },
        {
            "key": "genai-label:g10",
            "diagnostic": "Generative AI Labelling Audit",
            "number": 10,
            "question": "Is there a detection / response policy for circumvention attempts (removing or forging watermarks)?",
            "options": [
                "Active monitoring + reporting channel",
                "Policy text only",
                "None"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 31(2) and (4) (labeling methods set by enforcement decree and guidelines) — tamper prevention is recommended",
                "eu": "EU AI Act Art. 50(2) robustness",
                "us": "California AI Transparency Act (SB 942) duty to revoke license if the labeling capability is removed"
            },
            "why": "EU Art. 50(2) requires marks to be robust as far as technically feasible, and California SB 942 requires revoking the license of a licensee that removes the labeling capability. If marks can be erased easily, it is hard to argue that you have met the labeling duty.",
            "first_step": "State in the terms a prohibition on removing or forging marks, and a clause restricting use for violations",
            "law_basis": "October 2026"
        },
        {
            "key": "genai-label:g11",
            "diagnostic": "Generative AI Labelling Audit",
            "number": 11,
            "question": "When delivering AI outputs to downstream services via API, are labelling duties enforced through contracts / SLAs?",
            "options": [
                "Labelling clause + SLA",
                "Guidelines only",
                "None",
                "Not applicable — we do not offer an external API"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 31 duty holders = both AI developers and AI deployers (both are \"AI business operators\" under Art. 2)",
                "eu": "EU AI Act Art. 50(2) provider duty · Art. 53(1)(b) information for downstream providers",
                "us": "California AI Transparency Act (SB 942) duty to maintain labeling under license agreements"
            },
            "why": "The AI Basic Act treats both businesses that develop AI and businesses that provide services using AI as \"AI business operators.\" If an API customer strips the labeling and publishes the output, both that customer and you, as the source, are exposed. California SB 942 requires license agreements to include a duty to maintain the labeling. Note: not applicable if you do not offer an API externally.",
            "first_step": "Add to the API terms and contracts a duty to maintain labeling and a clause allowing suspension of use for violations",
            "law_basis": "October 2026"
        },
        {
            "key": "genai-label:g12",
            "diagnostic": "Generative AI Labelling Audit",
            "number": 12,
            "question": "Is your organization's 'AI labelling policy' published in multiple languages (≥ 3, e.g. KO/EN/JA)?",
            "options": [
                "Published in 3+ languages",
                "Single language only",
                "Not published"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 31 (in a manner users can easily recognize) — publishing a policy is recommended",
                "eu": "EU AI Act Art. 50(5) clear, distinguishable and accessible",
                "us": "California AI Transparency Act (SB 942) clear and conspicuous notice"
            },
            "why": "The law does not directly require publishing a policy document, but notices and labels must be easy for users to understand (EU Art. 50(5)). If you have overseas users or counterparties, a public policy in their language is the strongest trust signal, and it is an item that counterparty checklists often ask about.",
            "first_step": "Consolidate your policies on AI notice, labeling, deepfakes, elections and provenance verification into a one-page policy",
            "law_basis": "October 2026"
        },
        {
            "key": "global:o1",
            "diagnostic": "Cross-Border Operator Duties",
            "number": 1,
            "question": "Do you keep a single table of the countries where your AI is offered or its output is used, with the AI and data protection laws that apply in each?",
            "options": [
                "Yes — laws mapped per country, updated in the last 6 months",
                "Country list only; applicable laws not mapped",
                "No"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 4(1) (conduct abroad affecting Korean market or users)",
                "eu": "EU AI Act Art. 2(1)(a), (c) · GDPR Art. 3(2)",
                "us": "No federal AI statute — state laws protect their residents (e.g. Colorado SB 26-189)"
            },
            "why": "AI laws attach to where users are and where output is used, not to where the company sits. Korea's AI Basic Act (Art. 4(1)) and the EU AI Act (Art. 2(1)(c)) both reach operators established abroad. Without this map you cannot tell whether you have missed a representative, transfer or local-notice duty.",
            "first_step": "This week, pull the countries where you have users from web analytics, billing countries and API customer locations",
            "law_basis": "October 2026"
        },
        {
            "key": "global:o2",
            "diagnostic": "Cross-Border Operator Duties",
            "number": 2,
            "question": "Outside your home country, do you offer AI in markets with AI-specific obligations (Korea, the EU, China, Colorado, etc.)?",
            "options": [
                "No",
                "One market",
                "Two or more markets"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 4(1) · Art. 2 item 7 AI business operators",
                "eu": "EU AI Act Art. 2(1)(a), (c) extraterritorial scope",
                "us": "No federal AI statute — state laws (Colorado SB 26-189, California SB 942)"
            },
            "why": "This question measures exposure, not control. The more markets you serve, the more country-specific work you carry: representatives, registrations, local-language notices. Japan's AI Promotion Act (fully in force since 2025-09-01) requires businesses to cooperate with government measures but carries no penalties.",
            "first_step": "For each exposed market, flag which of questions 4 to 10 in this report apply",
            "law_basis": "October 2026"
        },
        {
            "key": "global:o3",
            "diagnostic": "Cross-Border Operator Duties",
            "number": 3,
            "question": "Have you determined and recorded your legal role in each market (Korea: developer or deployer; EU: provider, deployer, importer, distributor, etc.)?",
            "options": [
                "Yes — recorded per market and per product",
                "Only our role under home-country law",
                "Not determined"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 2 item 7(a) developers · (b) deployers",
                "eu": "EU AI Act Art. 3(3)–(8) operator roles · Art. 25 value chain",
                "us": "Colorado SB 26-189 developer vs. deployer · NYC Local Law 144"
            },
            "why": "Duties follow roles. In the EU, putting your name or trademark on another company's high-risk AI system, substantially modifying it, or changing its purpose so that it becomes high-risk makes you its provider (Art. 25(1)). In Korea both developer and user operators are AI business operators, and either may owe the Art. 31 notice when it provides a high-impact or generative AI product or service to users (exceptions in Decree Art. 23(4), e.g. internal-only use).",
            "first_step": "For each product, tabulate per country: who built it · under whose name it is sold · who operates it",
            "law_basis": "October 2026"
        },
        {
            "key": "global:o4",
            "diagnostic": "Cross-Border Operator Duties",
            "number": 4,
            "question": "(Operators with no address or place of business in Korea) Have you checked whether you meet the domestic-agent thresholds under Korea's AI Basic Act and, if so, appointed and reported an agent?",
            "options": [
                "Yes — appointed and reported, or documented that we fall below the thresholds",
                "Thresholds not yet checked",
                "We meet the thresholds but have not appointed an agent",
                "Not applicable — we have an address or place of business in Korea"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 36 · Decree Art. 29 thresholds · Art. 43(1) item 2 fine (standard KRW 20m)",
                "eu": "No equivalent — see EU authorised representative (Q5)",
                "us": "No rule — no local-agent requirement"
            },
            "why": "An operator with no address or place of business in Korea must appoint a domestic agent in writing and report it to the Ministry of Science and ICT if it meets any Decree Art. 29 threshold: KRW 1 trillion prior-year revenue · KRW 10 billion AI-service revenue · 1 million average daily users in Korea (last three months) · a prior Art. 43(1) item 3 fine (Art. 36(1)). Failure to appoint carries a fine with a standard amount of KRW 20 million (Art. 43(1) item 2; cap KRW 30 million), and the agent's violations count as the operator's own (Art. 36(3)). The government has announced a grace period of at least one year for fines.",
            "first_step": "Pull prior-year revenue (converted to KRW at the average annual exchange rate), AI-service revenue and average daily Korean users for the last three months, and compare them with the thresholds",
            "law_basis": "October 2026"
        },
        {
            "key": "global:o5",
            "diagnostic": "Cross-Border Operator Duties",
            "number": 5,
            "question": "(Non-EU operators) If you place a high-risk AI system or a general-purpose AI (GPAI) model on the EU market, have you appointed an EU authorised representative by written mandate, or planned to before the obligation applies?",
            "options": [
                "Yes — mandate in place, or open-source exemption documented",
                "Only a target date for the appointment",
                "No plan",
                "Not applicable — established in the EU, or no high-risk AI or GPAI model placed on the EU market"
            ],
            "provisions": {
                "kr": "No rule — Korean counterpart is the Art. 36 domestic agent (Q4)",
                "eu": "EU AI Act Art. 22 (Annex III from 2027-12-02, Annex I from 2028-08-02) · Art. 54 (GPAI, since 2025-08-02)",
                "us": "No rule — no representative requirement"
            },
            "why": "A non-EU provider must appoint an EU-established authorised representative by written mandate before placing a high-risk AI system on the EU market (Art. 22; after the Digital Omnibus, Regulation (EU) 2026/1744, from 2027-12-02 for Annex III and 2028-08-02 for Annex I). GPAI model providers have had this duty since 2025-08-02 (Art. 54; open-source exemption, except for models with systemic risk). Models placed on the market before 2025-08-02 have until 2027-08-02 (Art. 111(3)). The representative keeps the documentation available to authorities for 10 years and must end the mandate and alert them if the provider breaches the Regulation.",
            "first_step": "Sort the products you place on the EU market into high-risk (Annex I or III), GPAI and other, and note the date each obligation applies",
            "law_basis": "October 2026"
        },
        {
            "key": "global:o6",
            "diagnostic": "Cross-Border Operator Duties",
            "number": 6,
            "question": "If you process personal data of users abroad, have you checked each country's privacy-representative requirement (Korea PIPA domestic agent, GDPR EU representative, China PIPL representative, etc.)?",
            "options": [
                "Yes — checked per country; appointed and disclosed where required",
                "Checked or appointed for some countries only",
                "Not checked",
                "Not applicable — we do not process personal data of users outside our home country"
            ],
            "provisions": {
                "kr": "Korea's PIPA Art. 31-2 · Decree Art. 32-3 thresholds",
                "eu": "GDPR Art. 27 EU representative",
                "us": "No federal rule — state privacy laws enforced by attorneys general"
            },
            "why": "AI-law and privacy-law representatives are separate regimes. Korea's PIPA requires a processor with no Korean address or place of business to appoint a domestic agent in writing, and name it in the privacy policy, if it meets a threshold such as KRW 1 trillion total revenue or 1 million average daily data subjects in Korea (Art. 31-2). The GDPR requires non-EU controllers and processors targeting people in the EU to designate an EU representative, with narrow exceptions (Art. 27). China's PIPL requires offshore processors to have a representative or dedicated entity in China (Art. 53).",
            "first_step": "Add a 'privacy representative required?' column to the Q1 map and decide it country by country",
            "law_basis": "October 2026"
        },
        {
            "key": "global:o7",
            "diagnostic": "Cross-Border Operator Duties",
            "number": 7,
            "question": "For every flow of personal data across borders (including prompts sent to overseas AI APIs and overseas cloud training or storage), have you set and recorded the legal basis for the transfer?",
            "options": [
                "Yes — basis, country and recipient recorded for each flow",
                "Only our one or two main vendors",
                "Not recorded",
                "Not applicable — no personal data crosses borders (no overseas AI API or cloud)"
            ],
            "provisions": {
                "kr": "Korea's PIPA Arts. 28-8, 28-9 · Art. 64-2(1) item 7 (surcharge up to 3% of total revenue) · Art. 64-2(2) (up to 10% for intentional/grossly negligent repeats or large-scale harm)",
                "eu": "GDPR Arts. 44–49 · Korea adequacy decision (EU) 2022/254",
                "us": "No general federal rule — contracts and state privacy laws"
            },
            "why": "Entering customer data into an overseas AI API, or storing it in an overseas cloud, can be an overseas transfer. Korea requires one of the listed grounds: separate consent, outsourcing or storage needed for a contract and disclosed in the privacy policy, certification, or an equivalence-recognised country (Art. 28-8(1)). A breach can draw a surcharge of up to 3% of total revenue, excluding unrelated revenue (Art. 64-2(1) item 7), rising to up to 10% for intentional or grossly negligent repeat violations within 3 years or ≥10 million affected people (Art. 64-2(2)). EU-to-Korea transfers rely on an adequacy decision; onward transfers need their own basis.",
            "first_step": "List every AI tool, API and cloud service and extract each flow that carries personal data (country, recipient, data items)",
            "law_basis": "October 2026"
        },
        {
            "key": "global:o8",
            "diagnostic": "Cross-Border Operator Duties",
            "number": 8,
            "question": "Do you adapt AI-use notices and AI-generated content labels to each market's required method and local language?",
            "options": [
                "Yes — per-market method and local language, checked regularly",
                "One global wording (e.g. English only)",
                "Market methods and languages not checked"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 31(1) · Decree Art. 23(1) (notice methods) · Art. 43(1) item 1 fine (standard KRW 5m/10m/15m)",
                "eu": "EU AI Act Art. 50 (from 2026-08-02; Art. 50(2) grace to 2026-12-02) · GDPR Art. 12",
                "us": "California SB 942 (2026-08-02) · Utah Code §§13-75-103/-104 (disclose on request; proactively in regulated occupations)"
            },
            "why": "Notice duties differ by country. Korea requires prior notice when high-impact or generative AI is used, by a method set in Decree Art. 23(1): terms or contract, on-screen display, or posting at the point of supply (Art. 31(1)). Outputs hard to tell from reality must be disclosed so users clearly recognise them (Art. 31(3); Decree Art. 23(3)). EU Art. 50 notices apply from 2026-08-02. China's Measures for Labelling AI-Generated Synthetic Content (in force 2025-09-01) and national standard GB 45438-2025 require explicit and implicit labels. For an in-depth review of labels and watermarks, use the Generative AI Labelling Audit.",
            "first_step": "Build a one-page table per market: where the notice appears (screen, terms, voice) and the required wording",
            "law_basis": "October 2026"
        },
        {
            "key": "global:o9",
            "diagnostic": "Cross-Border Operator Duties",
            "number": 9,
            "question": "If you offer generative AI services to users in mainland China, have you completed the Chinese procedures (service filing or registration, content labelling, outbound data transfer)?",
            "options": [
                "Yes — completed with a local partner or entity",
                "In progress",
                "Offering the service without these procedures",
                "Not applicable — no users in mainland China"
            ],
            "provisions": {
                "kr": "No Korean rule — China's Interim Measures on Generative AI Services (2023-08-15)",
                "eu": "No EU rule — China's AI Content Labelling Measures (2025-09-01)",
                "us": "No US rule — China's PIPL Arts. 38 and 53"
            },
            "why": "China requires a security assessment and algorithm filing for generative AI services with public-opinion attributes or social-mobilisation capacity (Interim Measures Art. 17) and may take technical measures such as blocking against non-compliant services provided from abroad (Art. 20). Content labelling has been mandatory since 2025-09-01. Personal data leaving China generally needs a security assessment, standard contract or certification (PIPL Art. 38; exemptions exist). Whether a foreign company can file directly must be confirmed by local counsel.",
            "first_step": "Confirm your number of users in China and how they reach you (app stores, API, partners)",
            "law_basis": "October 2026"
        },
        {
            "key": "global:o10",
            "diagnostic": "Cross-Border Operator Duties",
            "number": 10,
            "question": "If you have US users or job applicants, do you track the AI laws of the states where they live (Colorado, New York City, California, Illinois, Texas, Utah, etc.)?",
            "options": [
                "Yes — an owner tracks each state where users live",
                "Only one or two states checked",
                "Not tracked",
                "Not applicable — no US users or job applicants"
            ],
            "provisions": {
                "kr": "No Korean rule — US state laws follow the user's residence",
                "eu": "No EU rule — US state laws follow the user's residence",
                "us": "Colorado SB 26-189 (2027-01-01) · NYC LL 144 · Illinois HB 3773 · Texas HB 149 · California SB 942 · Utah"
            },
            "why": "The US has no federal AI statute, and state rules differ. Colorado SB 26-189 (effective 2027-01-01) requires notice before consequential automated decisions, an explanation of adverse outcomes and human review; NYC Local Law 144 requires an annual bias audit of hiring tools. Illinois has required notice of AI use in employment decisions since 2026-01-01. A December 2025 executive order signalled federal pushback on state AI laws, but state laws remain enforceable unless a court holds otherwise.",
            "first_step": "Pull the states where your US users and applicants live and pick the top five",
            "law_basis": "October 2026"
        },
        {
            "key": "global:o11",
            "diagnostic": "Cross-Border Operator Duties",
            "number": 11,
            "question": "Do your contracts with local partners (importers, distributors, resellers, representatives) allocate AI-law duties (who handles notices, documentation and regulator requests)?",
            "options": [
                "Yes — every local contract has an allocation clause",
                "Only some contracts",
                "No",
                "Not applicable — we sell directly, with no local partners"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 36(3) (agent's violations attributed to the operator)",
                "eu": "EU AI Act Art. 23 (importers) · Art. 24 (distributors) (high-risk AI; Annex III from 2027-12-02, Annex I from 2028-08-02) · Art. 25(4) written agreements with suppliers of components and tools",
                "us": "No rule — indemnity and cooperation clauses"
            },
            "why": "Abroad, partners share the legal roles. An EU importer must verify that the provider has carried out the conformity assessment, drawn up the technical documentation and appointed an authorised representative (Art. 23); distributors must check markings and documents (Art. 24). Both duties apply to high-risk AI systems from 2027-12-02 (Annex III) or 2028-08-02 (Annex I). In Korea, a domestic agent's violations are deemed to be the appointing operator's (Art. 36(3)). Without contract terms, you keep the liability but lose control.",
            "first_step": "List your local contracts and flag whether each has an AI-duty allocation clause",
            "law_basis": "October 2026"
        },
        {
            "key": "global:o12",
            "diagnostic": "Cross-Border Operator Duties",
            "number": 12,
            "question": "Have you set up regulator contacts and a request-handling procedure for each country, plus monitoring of legal changes (owner and frequency)?",
            "options": [
                "Yes — named owner, reviewed quarterly",
                "Only when an issue comes up",
                "No"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 40 (fact-finding, orders) · Art. 43(1) item 3",
                "eu": "EU AI Act Art. 21 (high-risk providers, from 2027-12-02: cooperation, language) · Arts. 22(3), 54(3)",
                "us": "State attorneys general · FTC Act Section 5"
            },
            "why": "Foreign regulators' requests often come with short deadlines and must be answered in their language (for EU high-risk providers, Art. 21 from 2027-12-02). In Korea, failing to follow a corrective order after fact-finding carries a fine (Art. 43(1) item 3; standard KRW 10–30 million). The law keeps moving: the EU data protection Digital Omnibus is still under negotiation, Utah's AI Policy Act (Title 13 Ch. 72, Office of AI Policy) is scheduled to sunset on 2027-07-01 (the AI disclosure duties in §§13-75-103/-104 have no repeal date), and an amendment to Korea's AI Basic Act takes effect on 2027-04-21.",
            "first_step": "Put regulator, representative and local counsel contacts for each country on one page",
            "law_basis": "October 2026"
        },
        {
            "key": "highrisk:h1",
            "diagnostic": "High-risk AI Identifier",
            "number": 1,
            "question": "Do any of your AI systems make or substantially shape decisions about people in high-impact areas (hiring, loan screening, healthcare, student assessment, eligibility for public services), or help run or control critical facilities or products (energy, drinking water, nuclear, transport, medical devices)?",
            "options": [
                "No — not used in any high-impact area",
                "Yes — AI assists; a person makes the final decision or keeps control",
                "Yes — AI drives the decision or control, or acts automatically",
                "Don't know — never checked"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 2 item 4 (a)–(k) high-impact areas · Art. 33(1) advance review (mandatory)",
                "eu": "EU AI Act Art. 6(2) and the 8 areas of Annex III · Art. 6(1) and Annex I product safety components",
                "us": "Colorado SB 26-189 \"consequential decisions\" (from 2027-01-01) · NYC Local Law 144 hiring AEDTs"
            },
            "why": "This question measures exposure, not the level of control. High-impact AI under Korea's AI Basic Act triggers the advance notice under Art. 31(1) of that Act (fine of up to KRW 30 million if not given, Art. 43(1) item 1) and its Art. 34 duties (risk management, explanation, user protection, human oversight, records). In the EU, a system used in an Annex III area is subject to the high-risk obligations from 2027-12-02 unless the Art. 6(3) derogation applies (systems already on the market before then: only on significant design changes, Art. 111(2)).",
            "first_step": "Flag, system by system, whether each use falls in an Art. 2 item 4 area (items (a)–(k))",
            "law_basis": ""
        },
        {
            "key": "highrisk:h2",
            "diagnostic": "High-risk AI Identifier",
            "number": 2,
            "question": "Before any new AI is built, bought or rolled out, is there a mandatory step in the approval process that screens it for high-impact / high-risk status?",
            "options": [
                "Yes — a mandatory approval step",
                "Reviewed only on request",
                "No"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 33(1) advance review of high-impact status before provision (mandatory)",
                "eu": "EU AI Act Art. 6(4) assessment documented before market placement · Art. 16 provider obligations",
                "us": "Colorado SB 26-189 notice when a covered ADMT is used (from 2027-01-01) · NIST AI RMF 'Map 1' context and purpose (voluntary)"
            },
            "why": "Korea's AI Basic Act Art. 33(1) requires you to review high-impact status before you provide the AI. Discovering it after launch means rebuilding notice, documentation and oversight retroactively, and the Art. 31(1) advance notice may be missed in the meantime. In the EU, too, treating an Annex III system as not high-risk requires the assessment to be documented before it is placed on the market (Art. 6(4)).",
            "first_step": "Add five mandatory screening questions to purchase and project kick-off forms: (1) which area, (2) decisions about people or control of facilities, (3) does AI output drive the outcome, (4) any EU or US users, (5) does it profile people",
            "law_basis": ""
        },
        {
            "key": "highrisk:h3",
            "diagnostic": "High-risk AI Identifier",
            "number": 3,
            "question": "When screening, do you use a written criteria table that covers Korea's Art. 2 item 4, EU Annex III and the US state laws where you operate?",
            "options": [
                "Yes — one table covering every market we serve",
                "Criteria for one country only",
                "No written criteria (individual judgement)"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 2 item 4 · Art. 33(3) Ministry of Science and ICT guideline on criteria and examples",
                "eu": "EU AI Act Annex III · Art. 6(5) Commission classification guidelines (draft May 2026, not yet final)",
                "us": "Colorado SB 26-189 consequential-decision areas · NYC LL144 · California CCPA ADMT rules on \"significant decisions\" (from 2027-01-01)"
            },
            "why": "Each jurisdiction draws the line differently. Korea lists 10 areas in Art. 2 item 4 (more can be added by Presidential Decree), the EU uses the 8 Annex III areas plus Annex I products, and Colorado reaches \"consequential decisions\" such as housing and insurance. Without a written table, you have no basis to explain a classification.",
            "first_step": "Put Korea's Art. 2 item 4, EU Annex III and the relevant US state areas into one table (rows = areas, columns = jurisdictions)",
            "law_basis": ""
        },
        {
            "key": "highrisk:h4",
            "diagnostic": "High-risk AI Identifier",
            "number": 4,
            "question": "Have you checked that none of your features fall under the EU AI Act's prohibited practices (emotion recognition at work or school, social scoring, untargeted scraping of facial images, biometric categorisation that infers sensitive traits, etc.)?",
            "options": [
                "Yes — all systems checked and recorded",
                "Only some systems checked",
                "Not checked",
                "Not applicable — nothing offered or used in the EU, and no output used there"
            ],
            "provisions": {
                "kr": "No equivalent — Korea's AI Basic Act has no list of prohibited AI",
                "eu": "EU AI Act Art. 5 prohibited practices (since 2025-02-02) · Art. 5(1)(ba)(bb) new prohibitions (from 2026-12-02) · Art. 99(3)",
                "us": "No federal prohibited list — FTC Act Section 5 (unfair or deceptive practices), case by case"
            },
            "why": "The Art. 5 prohibitions have applied since 2025-02-02. Breaches can draw fines of up to EUR 35 million or 7% of worldwide annual turnover, whichever is higher (Art. 99(3); for SMEs, whichever is lower). From 2026-12-02, generating non-consensual intimate deepfakes and child sexual abuse material is also prohibited (Art. 5(1)(ba)(bb)). Everyday features, such as analysing facial expressions in interview videos, can be caught.",
            "first_step": "Turn the Art. 5 list (the original 8 plus the 2 added from 2026-12-02) into a questionnaire and run every AI feature through it",
            "law_basis": ""
        },
        {
            "key": "highrisk:h5",
            "diagnostic": "High-risk AI Identifier",
            "number": 5,
            "question": "For each system, do you record the high-impact / high-risk determination together with its reasoning (area, how far AI shapes the decision, human involvement, conclusion, approver)?",
            "options": [
                "Yes — a determination memo per system, approved",
                "Conclusion only (no reasoning)",
                "No record"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 33(1) advance review · Enforcement Decree Art. 25(2) item 3 (Ministry considers your own review)",
                "eu": "EU AI Act Art. 6(4) documented assessment, provided on request · Art. 80 re-evaluation by authorities",
                "us": "Colorado SB 26-189 compliance records kept for at least 3 years (from 2027-01-01)"
            },
            "why": "When the Ministry of Science and ICT confirms high-impact status, it takes into account the operator's own prior review (Enforcement Decree Art. 25(2) item 3). A reasoned memo is your first evidence in a confirmation request, an investigation or customer due diligence. In the EU, reasons for treating an Annex III system as not high-risk must be documented before launch, and misclassification to circumvent the rules is subject to fines (Art. 80(7)).",
            "first_step": "Create a one-page memo template: purpose, area, how far AI shapes the decision, human involvement, conclusion, assessor, approver, date",
            "law_basis": ""
        },
        {
            "key": "highrisk:h6",
            "diagnostic": "High-risk AI Identifier",
            "number": 6,
            "question": "If any system falls in an EU Annex III area but you treat it as not high-risk (Art. 6(3) derogation), have you recorded which condition applies, whether it profiles people, and your EU database registration plan?",
            "options": [
                "Yes — condition, profiling check and registration plan all recorded",
                "Derogation assessed but only partly recorded",
                "Treated as not high-risk without reasons",
                "Not applicable — no Annex III system relies on the derogation"
            ],
            "provisions": {
                "kr": "No equivalent — instead of a derogation, Korea offers confirmation by the Ministry under Art. 33(1)",
                "eu": "EU AI Act Art. 6(3)(a)–(d) (profiling always high-risk) · Art. 6(4), Art. 49(2) registration (simplified by the Omnibus)",
                "us": "No equivalent — Colorado SB 26-189 turns on whether the tool \"materially influences\" the decision"
            },
            "why": "An Annex III system may fall outside high-risk if it performs a narrow procedural task, improves a completed human activity, detects decision patterns, or does preparatory work, and does not materially influence the outcome (Art. 6(3)). But any system that profiles natural persons is always high-risk, and relying on the derogation requires documentation before launch and registration in the EU database (Art. 6(4), Art. 49(2)). Authorities can re-evaluate and order corrective action (Art. 80). Annex III obligations apply from 2027-12-02.",
            "first_step": "For each system relying on the derogation, record in three lines which of conditions (a)–(d) applies and why",
            "law_basis": ""
        },
        {
            "key": "highrisk:h7",
            "diagnostic": "High-risk AI Identifier",
            "number": 7,
            "question": "For each system, have you defined your role (do you build and supply it, or use someone else's AI in your service) in each jurisdiction's terms?",
            "options": [
                "Yes — role recorded per system and jurisdiction",
                "Roughly known but not recorded",
                "Never distinguished"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 2 item 7 developer / user operators · Enforcement Decree Art. 27(3) deemed compliance",
                "eu": "EU AI Act Art. 3(3)(4) provider / deployer · Art. 25 deployer becomes provider (new purpose, substantial modification)",
                "us": "Colorado SB 26-189 separate developer and deployer duties (from 2027-01-01)"
            },
            "why": "Duties depend on your role. In Korea, a user operator that deploys someone else's AI is deemed to have taken the risk-management, explanation and user-protection measures if the vendor took them and the operator has not substantially changed the original purpose (Enforcement Decree Art. 27(3)). Conversely, in the EU, repurposing a system for a high-risk use or substantially modifying it makes you the \"provider\", with all provider obligations (Art. 25).",
            "first_step": "Record each system's role in Korea (developer/user operator), the EU (provider/deployer) and the US (developer/deployer)",
            "law_basis": ""
        },
        {
            "key": "highrisk:h8",
            "diagnostic": "High-risk AI Identifier",
            "number": 8,
            "question": "Is re-classification required whenever something changes, such as a wider purpose, a new user group, a model swap or retraining, or entry into a new country?",
            "options": [
                "Yes — listed triggers + named owner",
                "Periodic (yearly) review only",
                "Classified once, never revisited"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 33(1) review on provision · Enforcement Decree Art. 27(3) substantial change of purpose",
                "eu": "EU AI Act Art. 3(23) substantial modification · Art. 25(1)(b)(c) · Art. 111(2) significant design changes",
                "us": "Colorado SB 26-189 developer notice of material updates (from 2027-01-01)"
            },
            "why": "High-impact / high-risk status depends on where a system is used, not on the technology, so the same model can change category when its use changes. In Korea, a user operator that substantially changes the original purpose can no longer rely on the vendor's measures (Enforcement Decree Art. 27(3)). In the EU, a high-risk system placed on the market before 2027-12-02 comes under the new rules if its design changes significantly afterwards (Art. 111(2)).",
            "first_step": "Add six re-classification triggers (purpose, user group, AI's weight in the decision, model, data, country) to change management",
            "law_basis": ""
        },
        {
            "key": "highrisk:h9",
            "diagnostic": "High-risk AI Identifier",
            "number": 9,
            "question": "When a classification is unclear, do you have a procedure and a ready dossier for asking the Ministry to confirm (Art. 33(1)) or for obtaining outside legal advice?",
            "options": [
                "Yes — procedure and dossier ready",
                "Worked out case by case",
                "We decide internally even when unclear"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 33(1)(2) confirmation request · Enforcement Decree Art. 25 (reply in 30 days, one 30-day extension, re-confirmation within 10 days)",
                "eu": "No formal confirmation procedure — national authority guidance (Art. 70(8)) · Commission guidelines",
                "us": "No equivalent — outside legal advice"
            },
            "why": "In Korea you can ask the Ministry of Science and ICT to confirm whether a system is high-impact. The Ministry must reply within 30 days (extendable once by 30 days; if you disagree you can request re-confirmation within 10 days of the reply — Enforcement Decree Art. 25). The request must attach a product overview, an overview of training data and material showing how the system is used and what it outputs, so a determination memo lets you file at once.",
            "first_step": "Define \"unclear\" (e.g. two assessors disagree, or a borderline area)",
            "law_basis": ""
        },
        {
            "key": "highrisk:h10",
            "diagnostic": "High-risk AI Identifier",
            "number": 10,
            "question": "For AI you source from vendors, do your contracts require the vendor to provide classification information, instructions for use and supporting material, and to give advance notice of major changes?",
            "options": [
                "Yes — contract clauses on information and change notice",
                "We get it if we ask",
                "Never received",
                "Not applicable — we use no third-party AI (all built in-house)"
            ],
            "provisions": {
                "kr": "Korea's Enforcement Decree Art. 27(4) user operator may request material · developer cooperation (best-efforts duty)",
                "eu": "EU AI Act Art. 13 instructions for use · Art. 26(1) deployers follow the instructions · Art. 25(4) written agreements in the supply chain",
                "us": "Colorado SB 26-189 developer documentation and notice of material updates (from 2027-01-01)"
            },
            "why": "A user operator may ask the vendor for the material it needs to meet the Art. 34 duties, but the vendor's cooperation is only a best-efforts duty (Enforcement Decree Art. 27(4)). Without a contract clause, you carry the classification and explanation burden without the facts. EU deployers must follow the provider's instructions (Art. 26(1)); from 2027-01-01 Colorado requires developers to document their tools for deployers.",
            "first_step": "Draft clauses for key AI contracts: classification information, instructions for use, training-data overview, advance notice of major changes",
            "law_basis": ""
        },
        {
            "key": "highrisk:h11",
            "diagnostic": "High-risk AI Identifier",
            "number": 11,
            "question": "If you use AI in the US for hiring (New York City) or for important decisions about consumers (Colorado and others), have you identified it as a regulated tool (NYC automated employment decision tool, AEDT / automated decision-making technology, ADMT, in Colorado and elsewhere) and scheduled audits and notices?",
            "options": [
                "Yes — identified, with audit and notice schedule",
                "Identified only",
                "Not checked",
                "Not applicable — no AI in US hiring or consumer decisions"
            ],
            "provisions": {
                "kr": "Not applicable (US item) — Korean hiring/lending AI: Art. 2 item 4 (g)",
                "eu": "Not applicable (US item) — EU hiring AI: Annex III point 4",
                "us": "NYC Local Law 144 (enforced since 2023-07-05: bias audit within 1 year before use, published summary, 10-business-day notice) · Colorado SB 26-189 and California CCPA ADMT rules (from 2027-01-01)"
            },
            "why": "New York City requires an employer using an automated employment decision tool (AEDT) that substantially assists or replaces hiring or promotion decisions to obtain an independent bias audit within one year before use, publish a summary of the results and notify candidates 10 business days in advance. From 2027-01-01, Colorado SB 26-189 requires notice, an explanation of adverse outcomes and human review for ADMT that materially influences consequential decisions.",
            "first_step": "Map US uses by state and city and flag those used in hiring, housing, lending, insurance, healthcare, education or public-service decisions",
            "law_basis": ""
        },
        {
            "key": "highrisk:h12",
            "diagnostic": "High-risk AI Identifier",
            "number": 12,
            "question": "Once a system is classified (high-impact / high-risk), do the resulting duties (advance notice, Art. 34 duties, website posting, EU high-risk readiness) start straight away with owners and deadlines?",
            "options": [
                "Yes — duty list, owners and deadlines per outcome",
                "Left to whoever is responsible",
                "Classification is the end of it"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 31(1) advance notice (fine, Art. 43(1) item 1) · Art. 34(1) duties · Enforcement Decree Art. 27(1) posting, 27(2) 5-year retention",
                "eu": "EU AI Act Arts. 8–17 (providers) and Art. 26 (deployers) — Annex III from 2027-12-02, Annex I from 2028-08-02",
                "us": "Colorado SB 26-189 deployer notice, explanation and human review (from 2027-01-01)"
            },
            "why": "Classification exists to start duties on time. High-impact AI under Korea's AI Basic Act requires advance notice to users (Art. 31(1); fine of up to KRW 30 million if not given), posting the key points of the risk-management, explanation and user-protection measures and the name and contact of the human overseer on your website or premises (Enforcement Decree Art. 27(1)), and keeping the supporting records for five years (Art. 27(2)). EU high-risk obligations apply from 2027-12-02 (Annex III) and 2028-08-02 (Annex I).",
            "first_step": "Build a duty table per outcome (high-impact / EU high-risk / US in scope / out of scope)",
            "law_basis": ""
        },
        {
            "key": "impact:i1",
            "diagnostic": "AI Impact Assessment Simulator",
            "number": 1,
            "question": "Can you state the AI system's 'intended purpose' in a single sentence?",
            "options": [
                "Yes — documented and shared",
                "Recognised but not formally documented",
                "Not defined"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 35(1) impact assessment (best-efforts duty) · Art. 34(1) item 1 risk management — purpose is the starting point of the assessment",
                "eu": "EU AI Act Art. 27(1)(a) process of use and intended purpose",
                "us": "NIST AI RMF 'Map 1.1' definition of purpose and context (voluntary)"
            },
            "why": "Every element of an impact assessment (people affected, risks, oversight criteria) starts from \"what is it used for.\" Without a written purpose, there is also no standard for preventing use beyond the original purpose (scope creep). (EU: Art. 27(1)(a))",
            "first_step": "Write one sentence, \"This AI helps [whom] make [which decision] by [what means],\" together with the uses it will not be put to",
            "law_basis": "October 2026"
        },
        {
            "key": "impact:i2",
            "diagnostic": "AI Impact Assessment Simulator",
            "number": 2,
            "question": "Does this AI fall in a 'high-impact' domain (employment, credit, healthcare, education, public services, law enforcement)?",
            "options": [
                "Yes — applicable",
                "Indirect impact only",
                "Not applicable"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 2 item 4 definition of high-impact AI · Art. 33(1) advance review duty",
                "eu": "EU AI Act Annex III high-risk uses",
                "us": "NYC Local Law 144 (AEDT) · Colorado SB 26-189 \"consequential decisions\" (effective 2027-01-01)"
            },
            "why": "This question looks at risk exposure, not level of control. If your AI is high-impact, the risk management, explanation, user protection, human oversight and document retention measures under Art. 34 become duties that must be performed, and under Art. 33(1) you must review whether it is high-impact before providing it. If it is unclear, you can ask the Ministry of Science and ICT for confirmation. (EU: Annex III)",
            "first_step": "Record in one page the basis of your determination against the high-impact areas in Art. 2 item 4 (if unclear, request government confirmation or obtain a legal opinion)",
            "law_basis": "October 2026"
        },
        {
            "key": "impact:i3",
            "diagnostic": "AI Impact Assessment Simulator",
            "number": 3,
            "question": "Have you identified the natural-person groups affected by the AI's decisions?",
            "options": [
                "Demographic breakdown (gender / age / minority)",
                "Single group only",
                "Not identified"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 35(1), second sentence: reflect the characteristics of AI-vulnerable groups",
                "eu": "EU AI Act Art. 27(1)(c) categories of natural persons and groups affected",
                "us": "NIST AI RMF 'Map 5' identification of impacted parties (voluntary)"
            },
            "why": "Art. 35(1) requires that an impact assessment reflect the characteristics of AI-vulnerable groups (people with disabilities, people aged 65 or over, etc.; Enforcement Decree Art. 1-2). If you look only at the average user, you miss the group most exposed to discrimination and accessibility problems. (EU: Art. 27(1)(c))",
            "first_step": "List separately the people directly subject to decisions and those indirectly affected (family, colleagues, etc.)",
            "law_basis": "October 2026"
        },
        {
            "key": "impact:i4",
            "diagnostic": "AI Impact Assessment Simulator",
            "number": 4,
            "question": "Have you analysed risks to fundamental rights (discrimination, privacy, expression) of those affected?",
            "options": [
                "Risk matrix produced",
                "Narrative analysis only",
                "None"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 35(1) fundamental-rights impact assessment (best-efforts duty) · Art. 35(2) priority consideration by state agencies",
                "eu": "EU AI Act Art. 27(1)(d) risks of harm to fundamental rights",
                "us": "NIST AI RMF 'Measure' risk assessment (voluntary)"
            },
            "why": "The core of Art. 35(1) is the assessment of impact on people's fundamental rights. It is a best-efforts duty, so there is no administrative fine, but state agencies must give priority consideration to products that have undergone an impact assessment (Art. 35(2)). In the EU, a fundamental rights impact assessment (FRIA) is mandatory in public services, credit scoring and insurance (from 2027-12-02). (EU: Art. 27(1)(d))",
            "first_step": "Prepare a \"likelihood × severity of harm\" matrix for each risk type: discrimination, privacy, expression, accessibility, safety, etc.",
            "law_basis": "October 2026"
        },
        {
            "key": "impact:i5",
            "diagnostic": "AI Impact Assessment Simulator",
            "number": 5,
            "question": "Have you verified the representativeness and bias of training / operational data?",
            "options": [
                "Statistical tests + external validation",
                "Internal analysis only",
                "Not verified"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 34(1) item 1 risk management plan",
                "eu": "EU AI Act Art. 10 data governance (providers)",
                "us": "NYC Local Law 144 bias audit (hiring AI) · NIST AI RMF 'Measure 2.11'"
            },
            "why": "If the data under-represents a particular group, the results will disadvantage that group however good the model is. This is the core of the risk management plan under Art. 34(1) item 1, and for hiring AI, New York City requires an independent bias audit once a year. (EU: Art. 10)",
            "first_step": "Compare the distribution of training and operating data by group with the distribution of your actual users",
            "law_basis": "October 2026"
        },
        {
            "key": "impact:i6",
            "diagnostic": "AI Impact Assessment Simulator",
            "number": 6,
            "question": "Are human oversight measures (approval, review, kill-switch) designed for AI decisions?",
            "options": [
                "Procedure + named owner",
                "Informal practice",
                "None"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 34(1) item 4 human oversight (mandatory)",
                "eu": "EU AI Act Art. 14 · Art. 26(2) assignment of oversight personnel by deployers · Art. 27(1)(e)",
                "us": "Colorado SB 26-189 meaningful human review (effective 2027-01-01)"
            },
            "why": "Art. 34(1) item 4 requires high-impact AI operators to perform human oversight. After an incident, the first question asked is \"who could have stopped it?\" The EU requires deployers to assign oversight personnel (Art. 26(2)), and Colorado SB 26-189 requires human review of adverse outcomes.",
            "first_step": "For each type of decision, decide whether it is \"AI only,\" \"human approval\" or \"human review\"",
            "law_basis": "October 2026"
        },
        {
            "key": "impact:i7",
            "diagnostic": "AI Impact Assessment Simulator",
            "number": 7,
            "question": "Is there a mechanism (explainability) to justify AI decisions to users?",
            "options": [
                "Automated XAI (SHAP / LIME)",
                "Human-authored explanation",
                "None"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 34(1) item 2 explanation plan · PIPA Art. 37-2 right to request an explanation",
                "eu": "EU AI Act Art. 86 right to explanation · Art. 13",
                "us": "Colorado SB 26-189 explanation of adverse outcomes within 30 days (effective 2027-01-01)"
            },
            "why": "Art. 34(1) item 2 requires a plan to explain the final result and main criteria of high-impact AI, and the Personal Information Protection Act (PIPA) Art. 37-2 guarantees the right to request an explanation of automated decisions. Colorado SB 26-189 requires adverse outcomes to be explained within 30 days. An explanation in terms users can understand matters more than a technical explanation (XAI). (EU: Art. 86)",
            "first_step": "Write standard wording that explains, in the user's language, the main factors that influenced the decision",
            "law_basis": "October 2026"
        },
        {
            "key": "impact:i8",
            "diagnostic": "AI Impact Assessment Simulator",
            "number": 8,
            "question": "Is there a published procedure for users to refuse or contest AI decisions?",
            "options": [
                "Published + SLA (response window)",
                "Internal procedure only",
                "None"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 34(1) item 3 user protection · PIPA Art. 37-2 right to refuse",
                "eu": "EU AI Act Art. 86 · GDPR Art. 22",
                "us": "Colorado SB 26-189 opportunity for human review (effective 2027-01-01)"
            },
            "why": "Personal Information Protection Act (PIPA) Art. 37-2 guarantees the right to refuse, and to request an explanation of, automated decisions, and Art. 34(1) item 3 requires user protection measures. If the procedure is not published, users go straight to complaints, disputes and reports to regulators. (EU: GDPR Art. 22)",
            "first_step": "State on decision screens and notices how to \"appeal or request human review\"",
            "law_basis": "October 2026"
        },
        {
            "key": "impact:i9",
            "diagnostic": "AI Impact Assessment Simulator",
            "number": 9,
            "question": "Do you plan post-market monitoring after AI deployment?",
            "options": [
                "Scheduled KPIs + threshold alarms",
                "Ad-hoc reviews",
                "Not planned"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 34(1) item 1 risk management (across the whole lifecycle)",
                "eu": "EU AI Act Art. 72 post-market monitoring (providers) · Art. 26(5) deployer monitoring",
                "us": "NIST AI RMF 'Manage 4' post-deployment monitoring (voluntary)"
            },
            "why": "An impact assessment is only a prediction at the time of deployment; when real data changes, performance and bias change too. Risk management (Art. 34(1) item 1) covers the whole lifecycle, and the EU separately requires post-market monitoring by providers and monitoring by deployers.",
            "first_step": "Select 3–5 key indicators, such as accuracy, outcome differences between groups and number of appeals",
            "law_basis": "October 2026"
        },
        {
            "key": "impact:i10",
            "diagnostic": "AI Impact Assessment Simulator",
            "number": 10,
            "question": "Have you defined a regulator-notification procedure for serious incidents / malfunctions?",
            "options": [
                "Trigger + form + named owner",
                "Internal reporting only",
                "None"
            ],
            "provisions": {
                "kr": "No general reporting duty for ordinary operators (large-scale compute AI: Art. 32 safety incident response and submission of results) · handling of Art. 40 fact-finding investigations",
                "eu": "EU AI Act Art. 73 serious incident reporting (providers) · Art. 26(5) deployer notification to provider",
                "us": "NIST AI RMF 'Manage 4.3' incident response (voluntary)"
            },
            "why": "Korea does not impose a separate incident reporting duty on ordinary operators, but large-scale compute AI has duties under Art. 32 to maintain a safety incident response system and submit results, and any incident can make you the subject of a fact-finding investigation under Art. 40. The EU requires providers to report serious incidents (Art. 73) and deployers to notify the provider (Art. 26(5)). Without notification criteria in advance, the response is delayed and both harm and liability grow.",
            "first_step": "Write a definition of \"serious incident\" (harm to life or property, large-scale wrong decisions, cases of discrimination, etc.) and severity levels",
            "law_basis": "October 2026"
        },
        {
            "key": "impact:i11",
            "diagnostic": "AI Impact Assessment Simulator",
            "number": 11,
            "question": "Is there a defined cadence for reviewing and updating this impact assessment?",
            "options": [
                "Annual + on material change",
                "On-demand only",
                "None"
            ],
            "provisions": {
                "kr": "AI Basic Act Art. 35(3) content and method of impact assessment delegated to enforcement decree",
                "eu": "EU AI Act Art. 27(2) update when elements change",
                "us": "NIST AI RMF 'Govern 1.5' periodic review (voluntary)"
            },
            "why": "When the purpose, data or user scope changes, the original assessment no longer holds. The EU requires an update when assessment elements change (Art. 27(2)), and the detailed method of impact assessment in Korea is to be set by enforcement decree, so it is safer to have a regular re-assessment system in place beforehand.",
            "first_step": "Set a fixed schedule for an annual re-assessment",
            "law_basis": "October 2026"
        },
        {
            "key": "impact:i12",
            "diagnostic": "AI Impact Assessment Simulator",
            "number": 12,
            "question": "Has the impact assessment result been reported and approved by the board / executive leadership?",
            "options": [
                "Board-approved + minutes",
                "Reported to executives only",
                "Not reported"
            ],
            "provisions": {
                "kr": "Not a statutory duty — linked to Art. 34(1) item 5 preparation and retention of documents on measures taken (recommended)",
                "eu": "EU AI Act Art. 17 quality management system (providers) · Art. 26 deployer obligations",
                "us": "NIST AI RMF 'Govern' executive accountability · OMB M-25-21 (federal agency standard)"
            },
            "why": "The law does not require board approval, but a record showing that executives decided whether to accept the risk makes responsibility clear when an incident occurs. \"Who approved it?\" is a frequent question in investor due diligence and public procurement, which is why this question carries the highest score weight.",
            "first_step": "Prepare a two-page summary of the impact assessment (purpose, main risks, residual risks, mitigation plan)",
            "law_basis": "October 2026"
        },
        {
            "key": "penalty:f1",
            "diagnostic": "AI Penalty Risk Score",
            "number": 1,
            "question": "Who do you provide your AI features to? (This sets which penalty regimes can reach you.)",
            "options": [
                "Internal use only — not offered to outside users",
                "Offered to users in Korea only",
                "Offered to users outside Korea (EU, US, etc.), with or without Korea"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 31(1) (prior notice for high-impact/generative AI; fine under Art. 43(1)1) · Art. 36 (foreign operators)",
                "eu": "EU AI Act Art. 2(1)(c) (applies to non-EU operators whose output is used in the EU) · Art. 99",
                "us": "No federal AI statute — FTC Act §5 · state laws follow user location (Colorado SB 26-189, Texas HB 149)"
            },
            "why": "This question measures exposure, not control. Penalties depend on which users, in which countries, receive what. Korea's AI Basic Act caps fines at KRW 30 million, but the EU AI Act allows up to EUR 35 million or 7% of worldwide turnover for prohibited practices, and the GDPR up to EUR 20 million or 4%. The wider your footprint, the more the response controls below matter.",
            "first_step": "List, country by country, which AI features you offer to whom (by user location), on one page",
            "law_basis": "October 2026"
        },
        {
            "key": "penalty:f2",
            "diagnostic": "AI Penalty Risk Score",
            "number": 2,
            "question": "How much personal data does your AI process, and how?",
            "options": [
                "No personal data (anonymous or business data only)",
                "Ordinary personal data (under 1,000 people; no sensitive data or automated decisions)",
                "1,000+ people or sensitive data, or automated decisions about people"
            ],
            "provisions": {
                "kr": "Korea's Personal Information Protection Act (PIPA) Art. 64-2 (up to 3% of total revenue; up to 10% for aggravated cases from 2026-09-11) · Art. 37-2 automated decisions",
                "eu": "GDPR Art. 83(4)(5) — up to EUR 10m/2% · EUR 20m/4% of worldwide turnover",
                "us": "No comprehensive federal privacy law — FTC Act §5 · state privacy laws (e.g., California CCPA)"
            },
            "why": "This question also measures exposure. Under Korea's PIPA, fines can reach 3% of total revenue (excluding revenue unrelated to the violation); since the amendment in force on 2026-09-11, the cap is 10% where (1) the same type of violation is repeated with intent or gross negligence within 3 years of a prior fine decision, (2) an intentional or grossly negligent violation affects 10 million or more people, or (3) a breach follows a disregarded corrective order (Art. 64-2(2)). Under the GDPR the cap is EUR 20 million or 4% of worldwide turnover.",
            "first_step": "For each AI system, tabulate the personal data items, number of people, sensitive data and automated decisions involved",
            "law_basis": "October 2026"
        },
        {
            "key": "penalty:f3",
            "diagnostic": "AI Penalty Risk Score",
            "number": 3,
            "question": "For each AI service, have you mapped on one page which duties carry which fines if breached?",
            "options": [
                "All services mapped, with an owner for each duty",
                "Only some services or some laws mapped",
                "Not mapped"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 43(1) (three fineable acts: Art. 31(1) prior notice, Art. 36 domestic agent, Art. 40(3) corrective orders) · Enforcement Decree Art. 32 & Annex 2",
                "eu": "EU AI Act Art. 99(3)–(5) three tiers (7%/3%/1%) · Art. 101 (GPAI) · GDPR Art. 83",
                "us": "No federal AI statute — FTC Act §5 · Texas HB 149 §552.105 · Colorado SB 26-189 §6-1-1706"
            },
            "why": "You cannot decide what to fix first without knowing which acts carry which caps. Under Korea's AI Basic Act, fines attach to only three acts (Art. 43(1), up to KRW 30 million); Annex 2 of the Enforcement Decree sets KRW 5 million for a first failure to give prior notice, KRW 20 million for failing to appoint a domestic agent and KRW 10 million for a first failure to follow a corrective order. The large amounts sit with turnover-based fines (EU AI Act, GDPR, PIPA).",
            "first_step": "One table per service: AI feature → applicable duty → statutory cap if breached (amounts from the legal text) → owner",
            "law_basis": "October 2026"
        },
        {
            "key": "penalty:f4",
            "diagnostic": "AI Penalty Risk Score",
            "number": 4,
            "question": "Where you offer AI in a country where you have no address or office, have you checked whether you must appoint a local representative (Korean domestic agent, EU authorised representative)?",
            "options": [
                "Thresholds checked; appointed and notified (or non-applicability recorded)",
                "Thresholds checked, but appointment or notification not finished",
                "May apply, but thresholds not checked",
                "Not applicable — we do not offer AI in any country where we have no address or office"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 36(1) & Decree Art. 29 (prior-year revenue KRW 1 trillion+, AI service revenue KRW 10 billion+, or 1 million+ average daily users in Korea, etc.) — failure fined under Art. 43(1)2 (Annex 2: KRW 20 million)",
                "eu": "EU AI Act Art. 22 (high-risk providers; Annex III from 2027-12-02, Annex I from 2028-08-02; breaches under Art. 99(4)(b)) · Art. 54 (GPAI models, since 2025-08-02; breaches fined by the Commission under Art. 101, from 2026-08-02)",
                "us": "No equivalent (no federal or state AI law requires a local representative, as checked in 2026-10)"
            },
            "why": "Appointing a representative only requires checking the thresholds, yet missing it is one of the few items that is fineable on its own (deferred during the government grace period). Korea's Decree also covers foreign operators that have been fined for ignoring a corrective order (Art. 29(1)4). The EU requires an authorised representative for high-risk AI providers (Annex III from 2027-12-02, Annex I from 2028-08-02) and for GPAI model providers.",
            "first_step": "Korea: compare prior-year revenue, AI service revenue and average daily Korean users with the Decree Art. 29 thresholds, and record the result on one page",
            "law_basis": "October 2026"
        },
        {
            "key": "penalty:f5",
            "diagnostic": "AI Penalty Risk Score",
            "number": 5,
            "question": "If a regulator asks for documents on an AI system (purpose, data, test results, notice screens, operating logs), can you supply accurate material within a week?",
            "options": [
                "A record pack exists per AI system; can submit within a week",
                "Records exist but are scattered; gathering them takes weeks",
                "Hardly any records"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 40(1)(2) (document requests, on-site inspection) · PIPA Art. 63 (failing to submit or submitting false material: fine up to KRW 30 million under Art. 75(2))",
                "eu": "EU AI Act Art. 21 (high-risk providers: information and documents on request — Annex III from 2027-12-02, Annex I from 2028-08-02) · Art. 99(5) (incorrect or incomplete information: EUR 7.5m/1%)",
                "us": "FTC Act §20 civil investigative demands · Texas HB 149 §552.103 (AG demands: purpose, data, performance metrics)"
            },
            "why": "Inquiries start with document requests. Failing to supply, or supplying wrong material, is penalised separately from the original breach (PIPA Art. 75(2): up to KRW 30 million; EU AI Act Art. 99(5): EUR 7.5 million or 1% of turnover). Conversely, cooperation and the technical and organisational measures in place are mitigating factors in EU fines (Art. 99(7)(f)(g)). The Texas AG can demand the purpose, training data and performance metrics directly.",
            "first_step": "One folder per AI system: purpose, data used, test results, screenshots of user notices, change history, incident log",
            "law_basis": "October 2026"
        },
        {
            "key": "penalty:f6",
            "diagnostic": "AI Penalty Risk Score",
            "number": 6,
            "question": "When a regulator sends an inquiry or notice of investigation, is it settled who receives it, in what order you respond, and by when?",
            "options": [
                "Named contact point + playbook (legal review, deadline tracking) + yearly drill",
                "Only a contact person named",
                "Nothing settled"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 40 (fact-finding; procedure under the Framework Act on Administrative Investigations) · Decree Annex 2, 1(c) (fine may be reduced by up to half where corrective efforts are recognised)",
                "eu": "EU AI Act Art. 99(7)(f)(h) (cooperation and self-notification weigh in fines) · GDPR Art. 83(2)(f)",
                "us": "Texas HB 149 §552.104 (60-day cure period after notice) · Colorado SB 26-189 §6-1-1706(3) (60 days; effective 2027-01-01)"
            },
            "why": "The first days after a notice change the outcome. In Texas, the AG cannot sue if you cure within 60 days of the notice and submit a written statement with supporting documents; Colorado also gives a 60-day cure period where the AG deems a cure possible (not for knowing or repeated violations; from 2027-01-01 until 2030-01-01). Korean fines can be reduced by up to half where corrective efforts are recognised, and EU fines take cooperation and self-notification into account.",
            "first_step": "Name a regulator contact point (shared mailbox, owner, deputy) and align the contact details on your website and contracts",
            "law_basis": "October 2026"
        },
        {
            "key": "penalty:f7",
            "diagnostic": "AI Penalty Risk Score",
            "number": 7,
            "question": "When a problem is confirmed, can you stop or fix the AI feature and prove that you fixed it?",
            "options": [
                "Stop/fix procedure + remediation record template + tested in practice",
                "Handled ad hoc by the engineering team",
                "No defined way to stop or fix"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 40(3) stop/corrective orders — non-compliance fined under Art. 43(1)3 (Annex 2: KRW 10m first, 20m second, 30m third and later) · PIPA Art. 64 & Art. 64-2(2)3",
                "eu": "EU AI Act Art. 20 (provider corrective actions) · Art. 26(5) (deployer suspends use) — high-risk AI, Annex III from 2027-12-02, Annex I from 2028-08-02 · Art. 99(7)(j) (harm mitigation)",
                "us": "Texas HB 149 §552.104(b)(2) (cure + written statement + supporting documents + policy changes) · Colorado SB 26-189 §6-1-1706(3)(d)"
            },
            "why": "Under Korea's AI Basic Act, failing to follow a corrective order is fined (KRW 10 million for the first time up to 30 million for the third and later), and a foreign operator fined this way must appoint a domestic agent. Under PIPA, if a breach occurs after a corrective order was ignored, the fine cap rises to 10% of total revenue (Art. 64-2(2)3, in force since 2026-09-11). In Texas, you avoid a lawsuit only by documenting the cure in a written statement with evidence.",
            "first_step": "Document on one page, per AI feature, the kill switch (disable the feature or roll back) and who decides",
            "law_basis": "October 2026"
        },
        {
            "key": "penalty:f8",
            "diagnostic": "AI Penalty Risk Score",
            "number": 8,
            "question": "If personal data leaks or a serious AI incident occurs, can you meet the statutory reporting deadlines (e.g., 72 hours)?",
            "options": [
                "Deadline table + on-call rota + yearly drill",
                "Deadlines known, but no rota or drill",
                "Deadlines not mapped"
            ],
            "provisions": {
                "kr": "PIPA Art. 34 & Decree Arts. 39–40 (report within 72 hours for leaks of 1,000+ people, sensitive data or external unlawful access; notice of possible leaks added from 2026-09-11) — failure fined under Art. 75(2)",
                "eu": "GDPR Art. 33 (72 hours) · EU AI Act Art. 73 (serious incidents with high-risk AI: 15 days; death 10 days; widespread infringement 2 days — Annex III from 2027-12-02, Annex I from 2028-08-02)",
                "us": "No general federal rule — state breach-notification laws (deadlines and scope vary; check each state)"
            },
            "why": "Missing a reporting deadline is penalised separately from the incident itself. In Korea, leaks involving 1,000+ people, sensitive data or external unlawful access must be reported within 72 hours, and failing to report or notify can be fined (Art. 75(2), up to KRW 30 million). In the EU, on top of the GDPR 72-hour rule, providers of high-risk AI must report serious incidents (Art. 73; Annex III from 2027-12-02, Annex I from 2028-08-02).",
            "first_step": "One-page table of reporting deadlines by country and incident type (authority, deadline, what the first report must contain)",
            "law_basis": "October 2026"
        },
        {
            "key": "penalty:f9",
            "diagnostic": "AI Penalty Risk Score",
            "number": 9,
            "question": "Do your contracts with AI vendors (models, APIs, cloud) and data processors include regulatory clauses (information access, incident notice, cooperation with inquiries, allocation of liability)?",
            "options": [
                "All four clauses in place",
                "Only some (e.g., security and confidentiality only)",
                "Vendor's standard terms as is"
            ],
            "provisions": {
                "kr": "PIPA Art. 26 (supervising processors — if lax supervision lets a processor breach the Act, fine under Art. 64-2(1)5) · Korea's AI Basic Act has no contract-clause rule",
                "eu": "EU AI Act Art. 25(4) (written agreement between high-risk provider and component suppliers, from 2027-12-02 for Annex III and 2028-08-02 for Annex I; breaches under Art. 99(4)(da), added by Regulation 2026/1744) · GDPR Art. 28",
                "us": "No statutory clauses — Colorado SB 26-189 §6-1-1702 (developer-to-deployer documentation, from 2027-01-01) · market practice (indemnities, cooperation)"
            },
            "why": "Inquiries come to you, but the material needed (training data, model specifications, logs) often sits with the vendor. Korea's PIPA lets the regulator fine the controller when lax supervision lets a processor breach the Act. The EU requires a written agreement between high-risk AI providers and their component suppliers (Art. 25(4)) and, once high-risk obligations apply (Annex III 2027-12-02, Annex I 2028-08-02), a breach of that duty is fineable under Art. 99(4)(da), added by Regulation 2026/1744.",
            "first_step": "List key AI vendors and processors with contract expiry dates",
            "law_basis": "October 2026"
        },
        {
            "key": "penalty:f10",
            "diagnostic": "AI Penalty Risk Score",
            "number": 10,
            "question": "Is every marketing or sales claim such as \"AI-powered\", \"99% accurate\" or \"bias-free\" backed by evidence?",
            "options": [
                "Evidence file per claim + legal review before publication",
                "Evidence for the main claims only",
                "No evidence kept",
                "Not applicable — we do not market any AI features"
            ],
            "provisions": {
                "kr": "Korea's Act on Fair Labeling and Advertising Art. 3(1) (false or exaggerated ads) & Art. 5(1) (duty to substantiate) — fine up to 2% of sales (Art. 9)",
                "eu": "Unfair Commercial Practices Directive (2005/29/EC) Arts. 6 & 13 — for widespread cross-border infringements, national caps of at least 4% of turnover (as amended by 2019/2161)",
                "us": "FTC Act §5 deception — AI-claims enforcement such as Operation AI Comply (2024); order violations up to $53,088 per violation (16 CFR 1.98)"
            },
            "why": "Exaggerated AI claims are penalised by consumer-protection law already in force, ahead of any AI statute. Korea's Fair Labeling and Advertising Act makes the company prove factual claims (Art. 5(1)) and allows fines of up to 2% of sales for false or exaggerated ads. The US FTC has targeted inflated AI claims since 2024, and breaching a consent order can cost up to $53,088 per violation.",
            "first_step": "Extract every AI-related claim from your website, sales decks and app-store listings into one list",
            "law_basis": "October 2026"
        },
        {
            "key": "penalty:f11",
            "diagnostic": "AI Penalty Risk Score",
            "number": 11,
            "question": "Have you confirmed whether damages and investigation costs arising from AI incidents are covered by insurance (or reserves)?",
            "options": [
                "Coverage and exclusions for AI incidents confirmed in the policy",
                "Insured, but unclear whether AI incidents are covered",
                "No relevant insurance or reserves"
            ],
            "provisions": {
                "kr": "PIPA Art. 39-7 & Decree Art. 48-7 (insurance, mutual aid or reserves for damages are mandatory where revenue is KRW 1 billion+ and 10,000+ data subjects on average per day) · AI-specific insurance is not mandatory",
                "eu": "Not mandatory — whether administrative fines are insurable depends on national law (to be checked)",
                "us": "Not mandatory — coverage of fines and civil penalties may be limited by state law and policy terms (to be checked)"
            },
            "why": "Insurance mainly reduces the costs around fines (damages, legal fees, investigation response) rather than the fines themselves. Korea's PIPA makes insurance, mutual aid or reserves mandatory for companies with revenue of KRW 1 billion+ and 10,000+ data subjects on average per day (Art. 39-7). Whether fines themselves can be insured varies by country, so the policy wording must be checked.",
            "first_step": "Ask your insurer or broker in writing whether AI output errors, discrimination claims, regulatory investigation costs and third-party damages are covered, and which exclusions apply",
            "law_basis": "October 2026"
        },
        {
            "key": "penalty:f12",
            "diagnostic": "AI Penalty Risk Score",
            "number": 12,
            "question": "Has management been briefed on AI penalty exposure (statutory caps, start dates, grace periods) and approved a remediation timeline and budget?",
            "options": [
                "Regular briefings + recorded approval of timeline and budget",
                "Briefed only (no approval or budget)",
                "Not briefed"
            ],
            "provisions": {
                "kr": "Not a statutory duty — grace period for fines and fact-finding under Korea's AI Basic Act (government: \"at least one year\" from 2026-01-22) · PIPA Art. 64-2(6) (fines reduced for protection investment, except intent or gross negligence)",
                "eu": "EU AI Act Art. 99(7)(g) (responsibility weighed against technical and organisational measures) · start dates: Art. 50 2026-08-02 (Art. 50(2) for systems already on the market: 2026-12-02), Art. 5(1)(ba)(bb) 2026-12-02, Annex III 2027-12-02",
                "us": "No rule — Texas HB 149 (effective 2026-01-01) · Colorado SB 26-189 (effective 2027-01-01; cure period until 2030-01-01)"
            },
            "why": "A grace period only defers penalties; it does not waive the duties. The government said \"at least one year\" and the end date must be confirmed from official announcements, so set the timeline and budget now to be ready on the day it ends. PIPA treats investment of budget and staff in protection as grounds for reducing fines (Art. 64-2(6)), and the EU also weighs the measures in place. A recorded approval is the most direct evidence of that investment.",
            "first_step": "Two-page briefing: summary of the Q3 penalty map, start dates by country, unmet items, budget required",
            "law_basis": "October 2026"
        },
        {
            "key": "privacy:p1",
            "diagnostic": "AI Privacy Audit",
            "number": 1,
            "question": "Do you have a data map showing which personal data your AI handles (training data, user inputs, AI outputs, conversation logs) and where it sits?",
            "options": [
                "Yes — training, inputs, outputs and logs all mapped",
                "Partly (e.g. training data only)",
                "No"
            ],
            "provisions": {
                "kr": "PIPA Art. 29 safeguards (internal management plan) · Art. 30 privacy policy",
                "eu": "GDPR Art. 30 records of processing activities",
                "us": "CCPA Regulations §7150 risk assessments · Civ. Code §1798.100 notice at collection"
            },
            "why": "If you do not know what personal data you hold, you cannot decide its lawful basis, retention, deletion or transfers. Conversation logs and user inputs are where unplanned personal data piles up fastest. (KR: PIPA Arts. 29–30 · EU: GDPR Art. 30)",
            "first_step": "For each AI system, build a four-column table (training / input / output / logs) listing data items, source, storage location and retention",
            "law_basis": "October 2026"
        },
        {
            "key": "privacy:p2",
            "diagnostic": "AI Privacy Audit",
            "number": 2,
            "question": "For each set of personal data used to train or fine-tune your AI, have you set a lawful basis (consent, contract, legitimate interest, pseudonymisation, etc.) and kept a record of that review?",
            "options": [
                "Yes — basis and review record for each dataset",
                "Basis chosen, but not documented",
                "We use the data we hold without any review",
                "Not applicable — we do not train or fine-tune (we only use off-the-shelf AI services)"
            ],
            "provisions": {
                "kr": "PIPA Art. 15(1) lawful basis · Art. 15(3) further use · Art. 28-2 pseudonymised data · Art. 28-12 AI exception (from 2027-03-09)",
                "eu": "GDPR Art. 6(1) lawful basis · EDPB Opinion 28/2024 (AI models)",
                "us": "CCPA Regulations §7002 purpose limitation · §7150(b)(6) risk assessment · FTC Act §5"
            },
            "why": "Reusing personal data collected for another purpose to train AI is processing beyond the original purpose; breaching PIPA Art. 15(1) can draw a penalty surcharge of up to 3% of total revenue (Art. 64-2(1)1). Current routes are consent, further use reasonably related to the original purpose (Art. 15(3)), pseudonymised data for scientific research and similar purposes (Art. 28-2), and legitimate interest for publicly available data (Art. 15(1)6, PIPC guidance of July 2024). From 2027-03-09, a further route opens: an AI development exception subject to deliberation and resolution by the PIPC (Art. 28-12). In the EU, the EDPB's view is that whether legitimate interest can support AI development or deployment must be assessed case by case using a three-step test (legitimate purpose, necessity, balancing) and documented (Opinion 28/2024).",
            "first_step": "For each training dataset, check the original purpose, basis and notice wording, and record it in a lawful-basis register",
            "law_basis": "October 2026"
        },
        {
            "key": "privacy:p3",
            "diagnostic": "AI Privacy Audit",
            "number": 3,
            "question": "Do you filter sensitive data (health, biometrics, etc.) and national ID numbers out of training and evaluation data, and control pseudonymisation (separate key data, no re-identification)?",
            "options": [
                "Yes — automated detection and removal + pseudonymisation controls",
                "Partly (e.g. sample checks)",
                "No controls",
                "Not applicable — no personal data in training or evaluation data"
            ],
            "provisions": {
                "kr": "PIPA Art. 23 sensitive data · Art. 24-2 resident registration numbers · Arts. 28-4, 28-5 pseudonymised data",
                "eu": "GDPR Art. 9 special categories · EU AI Act Art. 4a (Reg. 2026/1744, bias detection)",
                "us": "CCPA sensitive personal information (Civ. Code §1798.121) · Regulations §7150(b)(2)"
            },
            "why": "Processing sensitive data without separate consent (PIPA Art. 23(1)1) or processing pseudonymised data to identify a person (Art. 28-5(1)) can draw a penalty surcharge (Art. 64-2(1)3 and 6). Biometric features and racial or ethnic data are sensitive data under the Enforcement Decree (Art. 18). The EU allows special-category data for bias detection only under strict conditions: no workable alternative data, pseudonymisation, access control, deletion and records (AI Act Art. 4a).",
            "first_step": "Add an automated detection step at the start of the training pipeline for ID numbers, card numbers, health terms and face images",
            "law_basis": "October 2026"
        },
        {
            "key": "privacy:p4",
            "diagnostic": "AI Privacy Audit",
            "number": 4,
            "question": "Do you control, by policy and by technical means (enterprise accounts, input blocking, etc.), the personal data staff enter into external AI tools (chatbots, APIs)?",
            "options": [
                "Yes — usage policy + technical controls",
                "Usage policy (notice) only",
                "No controls"
            ],
            "provisions": {
                "kr": "PIPA Art. 26 outsourcing · Art. 17 provision to third parties · Art. 29 safeguards",
                "eu": "GDPR Art. 28 processors · Art. 32 security of processing",
                "us": "FTC Act §5 · CCPA service provider contracts (Civ. Code §1798.100(d))"
            },
            "why": "Entering customer data into an external AI tool means outsourcing processing to that vendor (PIPA Art. 26); if the vendor uses it to train its own models, it may become a provision to a third party (Art. 17). Without a written contract, disclosure and supervision, this can lead to a surcharge for failing to supervise a processor (Art. 64-2(1)5) or for provision without a lawful basis (Art. 64-2(1)1). In practice, this is the most common leakage route.",
            "first_step": "Move all work use of AI to enterprise accounts (excluded from training, with admin logs) and announce a ban on personal accounts",
            "law_basis": "October 2026"
        },
        {
            "key": "privacy:p5",
            "diagnostic": "AI Privacy Audit",
            "number": 5,
            "question": "Do your contracts with external AI vendors state no training on your data, retention periods, sub-processing and deletion?",
            "options": [
                "Yes — enterprise contract + processor (DPA) terms",
                "Standard terms reviewed only (training opt-out set)",
                "Terms not reviewed"
            ],
            "provisions": {
                "kr": "PIPA Art. 26(1) written contract · Art. 26(6) sub-outsourcing · Art. 26(4) supervision",
                "eu": "GDPR Art. 28(3) processor contract · Art. 28(2) sub-processors",
                "us": "CCPA service provider contract requirements (Regulations §7051)"
            },
            "why": "PIPA Art. 26(1) requires a written contract covering, among other things, a ban on processing beyond the outsourced purpose and protective measures, and sub-outsourcing needs your consent (Art. 26(6)). If a vendor changes its terms and starts training on your inputs, you have no basis to stop it without a contract. Enterprise customers ask about this first in due diligence.",
            "first_step": "List the AI vendors you use and tabulate four points from each vendor's terms: training use, retention, sub-processing and data location",
            "law_basis": "October 2026"
        },
        {
            "key": "privacy:p6",
            "diagnostic": "AI Privacy Audit",
            "number": 6,
            "question": "Do you know where AI processing (vendor servers, cloud regions) sends personal data abroad, and do you have a transfer basis for each country?",
            "options": [
                "Yes — routes and countries known + basis in place, disclosed in privacy policy",
                "Countries known, basis not checked",
                "We do not know which countries",
                "Not applicable — no overseas servers or foreign AI services"
            ],
            "provisions": {
                "kr": "PIPA Art. 28-8 cross-border transfer · Art. 64-2(1)7 surcharge",
                "eu": "GDPR Chapter V (Arts. 44–49) · adequacy for Korea (2021) · EU-US DPF (2023)",
                "us": "No general federal rule — DOJ bulk sensitive data rule (28 CFR Part 202)"
            },
            "why": "A transfer that breaches PIPA Art. 28-8(1) can draw a penalty surcharge (Art. 64-2(1)7). Where outsourcing or storage abroad is needed to perform a contract with the data subject, you may transfer by disclosing the countries, data items and recipients in your privacy policy or notifying individuals (Art. 28-8(1)3). On 2025-09-16 the PIPC recognised the 30 EU/EEA countries as offering an equivalent level of protection (excluding resident registration numbers and personal credit information). Sending EU users' data out of the EU needs its own GDPR Chapter V basis.",
            "first_step": "Tabulate the destination country for each AI vendor, cloud region and sub-processor",
            "law_basis": "October 2026"
        },
        {
            "key": "privacy:p7",
            "diagnostic": "AI Privacy Audit",
            "number": 7,
            "question": "Is your AI used for decisions that significantly affect people's rights or obligations (hiring, credit, insurance, healthcare, education, housing, etc.)?",
            "options": [
                "No",
                "A person decides; AI is input only",
                "AI decides, or effectively decides"
            ],
            "provisions": {
                "kr": "PIPA Art. 37-2 automated decisions · Korea's AI Basic Act Art. 2(4) high-impact AI",
                "eu": "GDPR Art. 22 automated individual decisions · EU AI Act Annex III",
                "us": "CCPA Regulations ADMT, significant decisions (2027-01-01) · Colorado SB 26-189 (2027-01-01)"
            },
            "why": "This question measures exposure, not control. PIPA Art. 37-2 gives a right to refuse fully automated decisions that significantly affect rights or obligations (except decisions based on consent, law or contract), and for automated decisions in general a right to request an explanation and a duty to publish the criteria and procedure. In the EU, GDPR Art. 22 applies; in California, ADMT pre-use notice, opt-out and access duties apply from 2027-01-01.",
            "first_step": "List every decision your AI is involved in and mark whether a person can change the outcome",
            "law_basis": "October 2026"
        },
        {
            "key": "privacy:p8",
            "diagnostic": "AI Privacy Audit",
            "number": 8,
            "question": "Have you published how your automated decisions work (in Korea, the five items in PIPA Art. 37-2 and Enforcement Decree Art. 44-4), and do you have a process and log for handling refusal and explanation requests within the legal deadline (Korea 30 days, EU one month)?",
            "options": [
                "Yes — channel, 30-day handling process and published criteria",
                "Case-by-case explanations on request only",
                "No",
                "Not applicable — AI is not used for decisions about individuals"
            ],
            "provisions": {
                "kr": "PIPA Art. 37-2 refusal, explanation, published criteria · Enforcement Decree Arts. 44-2 to 44-4",
                "eu": "GDPR Art. 22(3) human intervention · Art. 15(1)(h) logic involved (CJEU C-203/22)",
                "us": "CCPA Regulations ADMT notice, opt-out, access (2027-01-01) · Colorado SB 26-189 (2027-01-01)"
            },
            "why": "PIPA Art. 37-2 gives a right to refuse fully automated decisions with a significant effect and a right to an explanation of automated decisions generally, and requires the criteria and process to be published. The right to refuse does not apply to decisions based on consent, law or contract, but the right to an explanation remains. You must act within 30 days of a request (Enforcement Decree Art. 44-3(5), extendable twice). In the EU, the CJEU has held that individuals must receive meaningful information about the logic involved (C-203/22, 2025-02-27).",
            "first_step": "Publish on your website the fact, purpose and main data types of the automated decision and how to make a request (the five items in Enforcement Decree Art. 44-4)",
            "law_basis": "October 2026"
        },
        {
            "key": "privacy:p9",
            "diagnostic": "AI Privacy Audit",
            "number": 9,
            "question": "When someone asks to access, delete or stop processing their data, can you find it in training data, conversation logs and AI outputs and act within the legal deadline (Korea 10 days, EU one month, California 45 days)?",
            "options": [
                "Yes — source and log deletion + output blocking and retraining rules",
                "We can delete source data only",
                "No AI-specific process"
            ],
            "provisions": {
                "kr": "PIPA Arts. 35–37 access, deletion, suspension · Enforcement Decree Arts. 41, 43, 44 (10 days)",
                "eu": "GDPR Arts. 15, 17, 21 (one month, Art. 12(3)) · EDPB Opinion 28/2024",
                "us": "CCPA right to delete (Civ. Code §1798.105) · AB 1008 (2025-01-01)"
            },
            "why": "Deletion and suspension requests must be actioned, and the result notified, within 10 days of receipt (Enforcement Decree Arts. 43(3) and 44(2)). Fully removing one person's data from a trained model is technically hard, so the realistic approach is to set rules in advance: delete source data and logs, block outputs, and exclude the data from the next training run. California law states that personal information can exist in AI systems capable of outputting it (AB 1008).",
            "first_step": "Using the data map (Q1), write a search procedure to locate a person's data in sources, logs and training sets",
            "law_basis": "October 2026"
        },
        {
            "key": "privacy:p10",
            "diagnostic": "AI Privacy Audit",
            "number": 10,
            "question": "Does your privacy policy or collection notice state specifically the purposes of AI training and use, outsourcing to AI vendors and cross-border transfers?",
            "options": [
                "Yes — AI purposes, vendors and transfer countries named",
                "Only broad wording such as 'service improvement'",
                "Nothing about AI"
            ],
            "provisions": {
                "kr": "PIPA Art. 30 privacy policy · Art. 26(2) processors · Art. 28-8(2) transfers",
                "eu": "GDPR Arts. 12–14 information to data subjects",
                "us": "CCPA notice at collection (Civ. Code §1798.100(a)) · FTC Act §5"
            },
            "why": "The privacy policy is the first document an investigator reads. Processors must be disclosed so individuals can check them at any time (PIPA Art. 26(2)), and transfers abroad require information on data items, countries and recipients (Art. 28-8). From 2027-03-09, if you use personal data under the AI exception, its purpose and types must appear in the privacy policy (Art. 28-12(5)). The US FTC has warned that quietly changing terms retroactively to allow AI training may be unfair or deceptive.",
            "first_step": "Add an 'AI training and use' section to the privacy policy: purpose, data types, retention and how to object",
            "law_basis": "October 2026"
        },
        {
            "key": "privacy:p11",
            "diagnostic": "AI Privacy Audit",
            "number": 11,
            "question": "Before launching or significantly changing an AI system that uses personal data, do you carry out a privacy impact (risk) assessment?",
            "options": [
                "Yes — at every launch and change, using a set template",
                "Once, or only when needed",
                "Never"
            ],
            "provisions": {
                "kr": "PIPA Art. 33 impact assessment (mandatory for public bodies; best-efforts duty for others, Art. 33(11)) · Art. 28-12(3) (from 2027-03-09)",
                "eu": "GDPR Art. 35 DPIA · EU AI Act Art. 27(4) FRIA cross-reference (Reg. 2026/1744)",
                "us": "CCPA Regulations §§7150–7157 risk assessments (from 2026-01-01)"
            },
            "why": "In Korea, privacy impact assessments are mandatory only for public bodies (PIPA Art. 33(1)); private companies have a best-efforts duty to carry one out where there is a risk to individuals (Art. 33(11)). Using the AI exception from 2027-03-09 may require a risk factor assessment (Art. 28-12(3)). In the EU, a DPIA is in practice required when new technology is used for large-scale evaluation or sensitive data (Art. 35), and the fundamental rights impact assessment for high-risk AI can draw on the DPIA. California requires risk assessments for ADMT, sensitive data and similar processing (before starting any processing that begins on or after 2026-01-01; by 2027-12-31 for processing already under way).",
            "first_step": "Create a one- to two-page AI privacy assessment template: purpose, data, basis, risks, mitigations, residual risk, approver",
            "law_basis": "October 2026"
        },
        {
            "key": "privacy:p12",
            "diagnostic": "AI Privacy Audit",
            "number": 12,
            "question": "Do you set and enforce a retention period for prompts and conversation logs, and test before launch whether the AI reproduces personal data (memorisation or leakage)?",
            "options": [
                "Yes — retention enforced + leakage tests",
                "One of the two (retention or leakage tests)",
                "Neither"
            ],
            "provisions": {
                "kr": "PIPA Art. 21 destruction · Art. 29 safeguards · Art. 34 breach notification (likely breaches from 2026-09-11)",
                "eu": "GDPR Art. 5(1)(e) storage limitation · Art. 25 · Arts. 33–34 breach notification",
                "us": "CCPA retention disclosure (Civ. Code §1798.100(a)(3)) · §1798.150 · FTC Act §5"
            },
            "why": "Personal data must be destroyed without delay once its purpose is achieved (PIPA Art. 21), and the longer logs are kept, the larger any breach. From 2026-09-11, you must also notify individuals when you become aware of a likely breach as defined by the Enforcement Decree, not only an actual one (Art. 34(2)). A breach where safeguards were not fully in place can draw a penalty surcharge (Art. 64-2(1)9); in the EU, the supervisory authority must in principle be notified within 72 hours (GDPR Art. 33).",
            "first_step": "Set a retention period for prompts and conversation logs (for example, 30–90 days) and automate deletion",
            "law_basis": "October 2026"
        },
        {
            "key": "sme:s1",
            "diagnostic": "SME AI Diagnosis",
            "number": 1,
            "question": "How does your company use AI? (If more than one applies, pick the lowest option on the list, the one with the most impact on people.)",
            "options": [
                "Internal work only (drafting, translation, summaries, etc.)",
                "We offer AI-based features or services to customers (chatbot, AI support, apps with AI features, etc.)",
                "We use AI in important decisions about people (hiring, lending, healthcare, student assessment, etc.)"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 2 item 7 (AI business operator) and item 8 (user) · Art. 2 item 4 (high-impact areas incl. hiring and loan screening) · Enforcement Decree Art. 23(4) item 2 (internal-use exemption from notice)",
                "eu": "EU AI Act Art. 3(4) deployer · Art. 2(1)(c) non-EU operators · Annex III points 4 and 5(b) employment and creditworthiness (from 2027-12-02)",
                "us": "Colorado SB 26-189 \"consequential decisions\" (effective 2027-01-01) · NYC Local Law 144 (AEDT in hiring) · Illinois HB 3773 (AI in employment, effective 2026-01-01)"
            },
            "why": "This question measures how far the law reaches you, not your level of control. The AI Basic Act places duties on \"AI business operators\" that provide products or services using AI, not on \"users\" who simply use AI tools. Internal-only use is exempt from prior notice (Enforcement Decree Art. 23(4) item 2). Using AI for decisions such as hiring or lending puts you in a high-impact area.",
            "first_step": "List your AI uses on one page in three columns: internal / customer-facing / decisions about people",
            "law_basis": "October 2026"
        },
        {
            "key": "sme:s2",
            "diagnostic": "SME AI Diagnosis",
            "number": 2,
            "question": "Does the company keep a list of the AI tools staff use for work (ChatGPT, translators, meeting-notes apps, etc.)?",
            "options": [
                "Yes — listed with vendor, plan and team using it",
                "Partly (only the tools we approved)",
                "No — staff pick their own tools"
            ],
            "provisions": {
                "kr": "Korea's PIPA Art. 26(2) (disclosing processors) and Art. 30 (privacy policy) presuppose knowing which vendors receive data · no statutory duty to keep the list itself",
                "eu": "GDPR Art. 30 records of processing (partial exemption under 250 staff) and Art. 28 processor management presuppose it · no rule on AI tool lists as such",
                "us": "NIST AI RMF GOVERN 1.6 AI inventory (voluntary) · no federal statutory duty"
            },
            "why": "You cannot manage tools you do not know about. If customer personal data goes to an outside AI vendor, that can be outsourced processing (Korea's PIPA Art. 26) or an overseas transfer (Art. 28-8). If you do not know the vendor, you cannot list it in your privacy policy or check the contract.",
            "first_step": "Run a 5-minute staff survey: which AI tools you use for work, for what, free or paid",
            "law_basis": "October 2026"
        },
        {
            "key": "sme:s3",
            "diagnostic": "SME AI Diagnosis",
            "number": 3,
            "question": "Do you have a written rule for staff AI use (approved tools, information that must not be entered, checking results)?",
            "options": [
                "Yes — a 1–2 page policy, announced and acknowledged",
                "Verbal guidance only",
                "No rule"
            ],
            "provisions": {
                "kr": "Korea's PIPA Art. 29 safeguards (internal management plan) · evidence that information is \"managed as secret\" under the Unfair Competition Prevention Act Art. 2 item 2 · no statutory duty to have an AI policy as such",
                "eu": "EU AI Act Art. 4 AI literacy measures (amended 2026-07-27) — a practical means · GDPR Art. 24 and 32 organisational measures · no rule requiring an AI policy as such",
                "us": "NIST AI RMF GOVERN 1.2 policies (voluntary) · evidence of \"reasonable measures\" for trade secrets (18 U.S.C. §1839(3)) · no federal statutory duty"
            },
            "why": "Without a rule, people use AI however is convenient. Most leaks of customer data or confidential material into outside AI start with \"I thought it was fine.\" A written rule is also your evidence that the company exercised control if something goes wrong (trade secrets are protected only if \"managed as secret\" — Unfair Competition Prevention Act Art. 2 item 2).",
            "first_step": "Write a 1–2 page policy: approved tools, prohibited information (personal data, client files, unpublished financials, source code) and the duty to check results",
            "law_basis": "October 2026"
        },
        {
            "key": "sme:s4",
            "diagnostic": "SME AI Diagnosis",
            "number": 4,
            "question": "How do you control staff entering customer or employee personal data (names, contact details, case notes, etc.) into outside AI tools?",
            "options": [
                "Not entered, or only the minimum into business tools covered by a contract and our privacy policy",
                "We tell staff to remove names, but do not check",
                "Entered as is when needed / we don't know"
            ],
            "provisions": {
                "kr": "Korea's PIPA Art. 26 outsourced processing (written contract, disclosure, supervision) · Art. 17 provision to third parties · Art. 28-8 overseas transfer · Art. 29 safeguards",
                "eu": "GDPR Art. 6 lawful basis · Art. 28 processor contract · Art. 44 et seq. international transfers (for EU residents' data)",
                "us": "FTC Act §5 (unfair or deceptive practices) · state privacy laws (e.g. CCPA; check thresholds) · no general federal privacy law"
            },
            "why": "Entering personal data into an outside AI usually means outsourcing processing to that vendor (Korea's PIPA Art. 26); if the vendor uses it for its own purposes, such as training, it may be treated as provision to a third party (Art. 17). Servers abroad also raise overseas-transfer rules (Art. 28-8). Outsourcing requires a written contract, disclosure in your privacy policy and supervision of the vendor. A leak triggers notification duties (Art. 34) and exposure to penalty surcharges (Art. 64-2: up to 3% of revenue, excluding revenue unrelated to the violation; up to 10% for repeat or serious violations).",
            "first_step": "Add 10 examples of data that must never be entered (resident registration numbers, contact details, raw case notes, etc.) to the policy and announce it",
            "law_basis": "October 2026"
        },
        {
            "key": "sme:s5",
            "diagnostic": "SME AI Diagnosis",
            "number": 5,
            "question": "Do you have a rule for entering confidential material (unreleased plans, quotes, source code, contracts) into AI tools?",
            "options": [
                "Yes — approved tools set per confidentiality level",
                "Only a general \"be careful\" message",
                "No rule"
            ],
            "provisions": {
                "kr": "Korea's Unfair Competition Prevention and Trade Secret Protection Act Art. 2 item 2 (only information \"managed as secret\" is protected) · NDAs with clients and partners",
                "eu": "Trade Secrets Directive (EU) 2016/943 Art. 2(1)(c) \"reasonable steps\" to keep information secret",
                "us": "Defend Trade Secrets Act, 18 U.S.C. §1839(3)(A) \"reasonable measures\""
            },
            "why": "Trade secrets are protected only if the company has managed them as secret. If confidential material went into tools that train on inputs and nobody stopped it, it becomes hard to argue you kept it secret after a leak. With client material, it may also breach an NDA.",
            "first_step": "Classify information into three levels (public / internal / confidential) and set which AI tools each level may use",
            "law_basis": "October 2026"
        },
        {
            "key": "sme:s6",
            "diagnostic": "SME AI Diagnosis",
            "number": 6,
            "question": "Have you checked each AI tool's terms for whether it trains on your inputs and where it stores your data?",
            "options": [
                "Yes — all main tools checked; training switched off, company accounts in use",
                "Only some tools checked",
                "Not checked / staff use personal free accounts"
            ],
            "provisions": {
                "kr": "Korea's PIPA Art. 26(1) (required terms of an outsourcing contract) · Art. 28-8(1) (grounds for overseas transfer: separate consent, privacy-policy disclosure for outsourcing/storage needed to perform a contract, etc.)",
                "eu": "GDPR Art. 28(3) mandatory processor contract terms · Art. 46 standard contractual clauses (SCCs)",
                "us": "FTC 2024 guidance: quietly changing terms to use data for AI training may be unfair or deceptive · NIST AI RMF GOVERN 6.1 third-party risk (voluntary) · no federal statutory duty"
            },
            "why": "The same AI service can have different data terms for a personal free account and a business plan. Once inputs are used for training, they are hard to pull back. If personal data is involved, the contract must contain what PIPA Art. 26(1) requires (no processing beyond the purpose, safeguards). Storage on servers abroad is an overseas transfer (Art. 28-8) and needs a legal ground. If the outsourcing or storage is needed to perform a contract with the data subject, disclosing the destination country etc. in your privacy policy can be that ground; otherwise you need another ground, such as separate consent.",
            "first_step": "For each listed tool, record from its terms and settings: training on inputs, how to switch it off, storage country, retention period",
            "law_basis": "October 2026"
        },
        {
            "key": "sme:s7",
            "diagnostic": "SME AI Diagnosis",
            "number": 7,
            "question": "When you offer customers AI-based features or services such as a chatbot or AI support, do you tell them they are AI-based before they use them, in your terms, service description or first screen, on every channel (website, messenger, phone, email)?",
            "options": [
                "Yes — stated in advance on screen, in terms, etc.",
                "Only on some channels",
                "No notice",
                "Not applicable — we offer no AI-based features or services to customers (including where we only use AI-made material as our own content)"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 31(1) prior notice (administrative fine up to KRW 30 million under Art. 43(1) item 1) · Enforcement Decree Art. 23(1) (terms, screen, posting) and (4) (obvious cases, internal use exemptions)",
                "eu": "EU AI Act Art. 50(1) chatbot disclosure (providers) · Art. 50(4) deepfakes and public-interest text (deployers) — from 2026-08-02",
                "us": "Utah Code §13-75-103 (SB 226, in force 2025-05-07: disclose when a consumer clearly asks; proactively in regulated occupations' high-risk interactions — no repeal date) · California bot disclosure law, Bus. & Prof. Code §17941"
            },
            "why": "Korea's AI Basic Act Art. 31(1) requires operators that provide products or services using generative or high-impact AI to tell users in advance; failure is subject to an administrative fine (Art. 43(1) item 1; under Enforcement Decree Annex 2, KRW 5 million for a first violation, which may be reduced by up to half for SMEs). The government has said it will allow a grace period of at least one year, but a notice is something you can add today. Labelling of AI-generated output (Art. 31(2)–(3)) is covered in our Generative AI Labelling Audit.",
            "first_step": "Add one line to the chatbot's opening screen and support greeting: \"Replies are generated by AI (to reach a person: …)\"",
            "law_basis": "October 2026"
        },
        {
            "key": "sme:s8",
            "diagnostic": "SME AI Diagnosis",
            "number": 8,
            "question": "Does a person check AI output (customer replies, quotes, draft contracts, ad copy) before it leaves the company?",
            "options": [
                "Yes — anything going out is checked by the person responsible",
                "Only important items, occasionally",
                "Used as is, without checks"
            ],
            "provisions": {
                "kr": "Korea's Act on Fair Labeling and Advertising Art. 3(1) (the advertiser is liable for false or exaggerated ads) · for high-impact AI, human oversight under the AI Basic Act Art. 34(1) item 4 · otherwise no general duty",
                "eu": "EU AI Act Art. 50(4) exemption for public-interest text under human review and editorial responsibility · deployers of high-risk AI: human oversight under Art. 26(2) (from 2027-12-02) · otherwise no general duty",
                "us": "FTC Act §5 — deceptive claims are the company's responsibility even if AI wrote them · NIST AI 600-1 Generative AI Profile (voluntary)"
            },
            "why": "Generative AI can be convincingly wrong. If an incorrect quote, promise or ad claim goes out, your company, not the AI vendor, carries the responsibility (false or exaggerated advertising: Korea's Act on Fair Labeling and Advertising Art. 3(1)). Under most laws a human check is not a general duty, but it is the cheapest and most effective safeguard you have.",
            "first_step": "Define what must always be checked by a person (customer replies, prices, contracts, legal, medical, ad copy)",
            "law_basis": "October 2026"
        },
        {
            "key": "sme:s9",
            "diagnostic": "SME AI Diagnosis",
            "number": 9,
            "question": "When AI is used for important work (customer replies, documents, input to decisions), is there a record of what was used and how?",
            "options": [
                "Yes — tool, purpose and reviewer recorded (incl. business tool logs)",
                "Only the tools' own chat history",
                "No records"
            ],
            "provisions": {
                "kr": "For high-impact AI, documentation and retention under Korea's AI Basic Act Art. 34(1) item 5 · basis for responding to disputes and fact-finding (Art. 40) · otherwise no general duty",
                "eu": "Deployers of high-risk AI keep logs for at least six months under EU AI Act Art. 26(6) (from 2027-12-02) · otherwise no general duty",
                "us": "NIST AI RMF MANAGE function documentation (voluntary) · no federal statutory duty"
            },
            "why": "If a customer asks who produced a reply, or a dispute arises, you have nothing to show without a record. Outside high-impact AI there is no statutory record-keeping duty, but a simple log greatly shortens incident response.",
            "first_step": "For important work only (customer replies, contracts, hiring), keep a 4-column log: date, tool, purpose, reviewer",
            "law_basis": "October 2026"
        },
        {
            "key": "sme:s10",
            "diagnostic": "SME AI Diagnosis",
            "number": 10,
            "question": "Do you train staff to use AI safely (spotting wrong answers, information that must not be entered)?",
            "options": [
                "Yes — at onboarding and at least yearly",
                "Once, in the past",
                "No training"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 16(2) item 3 government support for AI training of SME staff · no statutory duty to train",
                "eu": "EU AI Act Art. 4 AI literacy — as amended 2026-07-27: take measures to support staff AI literacy (no specific level guaranteed)",
                "us": "NIST AI RMF GOVERN 2.2 training (voluntary) · no federal statutory duty"
            },
            "why": "A policy (Q3) only works if staff understand it. Companies using AI within the EU's reach must take measures to support their staff's AI literacy (Art. 4, amended 2026-07-27; no specific level has to be guaranteed). Korea has no such duty, but the AI Basic Act provides a basis for government support for SME staff training (Art. 16(2) item 3).",
            "first_step": "Prepare a 30-minute internal session (examples of wrong answers, prohibited data, checking steps, who to call after an incident)",
            "law_basis": "October 2026"
        },
        {
            "key": "sme:s11",
            "diagnostic": "SME AI Diagnosis",
            "number": 11,
            "question": "Have you checked which AI-related laws apply to your company (Korea's AI Basic Act and, if you have overseas customers, their local laws)?",
            "options": [
                "Yes — checked per market, with a named owner",
                "Korea only / roughly",
                "Never checked"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 4(1) (applies to acts abroad that affect the Korean market) · Art. 2 item 7 AI business operator · government AI Basic Act help desk (advice)",
                "eu": "EU AI Act Art. 2(1)(c) applies to non-EU deployers where output is used in the EU · GDPR Art. 3(2) (when targeting people in the EU)",
                "us": "State laws apply by user or applicant location (e.g. Colorado SB 26-189, NYC LL144, Utah) · no general federal AI law"
            },
            "why": "Even a small company can come under the EU AI Act if it supplies AI output to EU customers, or under a US state's law if it screens applicants from that state with AI. Conversely, a company using AI only internally has fewer duties than many assume. Knowing what applies lets you prepare neither too much nor too little.",
            "first_step": "List the countries (US: states) where you have customers, staff or applicants, and summarise the applicable laws in one table",
            "law_basis": "October 2026"
        },
        {
            "key": "sme:s12",
            "diagnostic": "SME AI Diagnosis",
            "number": 12,
            "question": "Have you looked into or used public support programmes for AI adoption, training or consulting?",
            "options": [
                "Yes — applied or using one",
                "Aware, but have not applied",
                "Not aware"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 16(2) (basis for consulting, training and funding support) · Art. 17 (priority for SMEs; possible support for Art. 34 and 35 measures)",
                "eu": "EU AI Act Art. 62 Member State support for SMEs (training, dedicated channels; priority sandbox access for SMEs with an office or branch in the EU)",
                "us": "Free NIST AI RMF and Playbook resources · no federal AI-specific support duty"
            },
            "why": "Korea's AI Basic Act allows the government to support SMEs with AI adoption consulting, training and funding (Art. 16(2)), and requires support schemes to give SMEs priority (Art. 17(1)). Tackling the tasks from this check (policy, training, terms review) through a programme lowers your cost. Programme names and conditions change every year, so confirm them in the official calls.",
            "first_step": "Check AI adoption and training calls from Korea's NIPA, the Ministry of SMEs and Startups and local governments once a year (outside Korea: your national or regional SME agency)",
            "law_basis": "October 2026"
        },
        {
            "key": "transparency:t1",
            "diagnostic": "AI Transparency Requirements",
            "number": 1,
            "question": "Do you keep a list of every point where customers or users meet AI (chatbots, recommendations, screening, voice support, kiosks, etc.), noting which notice and explanation duties apply at each one?",
            "options": [
                "Yes — list plus the rules that apply at each point",
                "List only (applicable rules not mapped)",
                "No list"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 31(1) prior notice for high-impact and generative AI · Enforcement Decree Art. 23(1) — the list shows where notice is needed",
                "eu": "EU AI Act Art. 50(1) notice of AI interaction (from 2026-08-02) · Art. 26(11) informing persons subject to high-risk AI (from 2027-12-02)",
                "us": "Colorado SB 26-189 notice at the point of interaction (2027-01-01) · Utah Code §13-75-103"
            },
            "why": "A notice has to sit at each place where AI is used. Without a list, you will miss new touchpoints such as a support chatbot or a phone voicebot added last quarter. Korea's prior-notice duty (Art. 31(1)) covers high-impact and generative AI, while EU AI Act Art. 50(1) covers any AI that interacts directly with people, so the scope differs by market.",
            "first_step": "Build one table of every point where AI meets users across web, app, phone, email and stores, with owner and launch date",
            "law_basis": "October 2026"
        },
        {
            "key": "transparency:t2",
            "diagnostic": "AI Transparency Requirements",
            "number": 2,
            "question": "Does AI make, or strongly influence, decisions about individuals (hiring, lending, insurance, pricing, eligibility for a service, account suspension, etc.)?",
            "options": [
                "No — not used for decisions about individuals",
                "AI recommends; a person genuinely decides",
                "AI decides with no human involvement"
            ],
            "provisions": {
                "kr": "Korea PIPA Art. 37-2 (fully automated decisions — right to refuse and to request an explanation) · Korea's AI Basic Act Art. 2 item 4(g) (hiring, loan screening and other high-impact areas)",
                "eu": "GDPR Art. 22 · EU AI Act Art. 86 right to explanation (decisions based on Annex III high-risk AI)",
                "us": "Colorado SB 26-189 \"consequential decision\" (2027-01-01) · CCPA regulations on ADMT \"significant decision\" (2027-01-01)"
            },
            "why": "This question measures exposure, not control. Korea PIPA Art. 37-2 (already in force) gives a right to refuse fully automated decisions that significantly affect a person's rights or obligations (except decisions based on consent, law or contract under Art. 15(1) items 1, 2 and 4), and a right to request an explanation of automated decisions. Colorado SB 26-189 applies when AI materially influences a consequential decision, so a human final decision does not necessarily take you out of scope. If the human review is a rubber stamp, regulators may treat the decision as automated.",
            "first_step": "For each decision that uses AI, classify it as \"AI alone\" or \"AI recommends, person decides\" and record how often reviewers change the outcome",
            "law_basis": "October 2026"
        },
        {
            "key": "transparency:t3",
            "diagnostic": "AI Transparency Requirements",
            "number": 3,
            "question": "Before people use the service, do you tell them that AI is involved, using a method that fits each channel (on-screen notice, spoken message, contract wording, signage in stores)?",
            "options": [
                "Prior notice in every channel",
                "Only in the terms of service or contract",
                "Some channels only (phone, stores, etc. missing)",
                "No notice",
                "N/A — no AI features offered to users (internal use only)"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 31(1) prior notice · Enforcement Decree Art. 23(1) (on the product or in terms, on screen, or posted at the location) · Art. 43(1) item 1 administrative fine up to KRW 30 million",
                "eu": "EU AI Act Art. 50(1) and (5) clear notice at the latest at the first interaction (from 2026-08-02)",
                "us": "Utah Code §13-75-103 (on request; high-risk interactions in regulated occupations) · California B&P Code §17941 (BOT Act) · SB 243 companion chatbots (2026-01-01)"
            },
            "why": "Prior notice under Art. 31(1) of Korea's AI Basic Act is the transparency duty with a direct administrative fine (Art. 43(1) item 1; Enforcement Decree Annex 2: KRW 5 million for a first violation, 10 million for a second, 15 million for a third or later). The Decree lets you give notice in the terms, on screen or by signage, but channels without a screen, such as phone and stores, are where gaps usually appear. EU AI Act Art. 50(5) requires clear notice at the latest at the first interaction. Labelling and watermarking of AI outputs are covered by our GenAI Labeling diagnostic.",
            "first_step": "Using the Q1 touchpoint list, set the notice method for each channel (screen text, opening voice message, contract clause, store signage)",
            "law_basis": "October 2026"
        },
        {
            "key": "transparency:t4",
            "diagnostic": "AI Transparency Requirements",
            "number": 4,
            "question": "Where you do not give notice (AI use is obvious from the name, internal-only tools, etc.), do you record the reasons for that decision?",
            "options": [
                "Yes — reasons recorded for each exception and checked by Legal",
                "Staff judgment only, no record",
                "No criteria for exceptions",
                "N/A — every touchpoint gives notice, no exceptions"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Enforcement Decree Art. 23(4) (AI use obvious, internal use only, exceptions set by ministerial notice)",
                "eu": "EU AI Act Art. 50(1) proviso (obvious to a reasonably well-informed, observant and circumspect person)",
                "us": "Utah Code §13-75-104 safe harbor (clear disclosure at the outset and throughout) — no statutory duty to record exception decisions (recommended practice)"
            },
            "why": "Enforcement Decree Art. 23(4) allows you to omit notice where AI use is obvious or the tool is for internal use only, but it is up to you to show that it was obvious. In a fine proceeding (Art. 43(1) item 1) or a customer complaint, an exception without a record looks like an omission (exceptions to the labelling duties in Art. 31(2)–(3) can also come up in an Art. 40 fact-finding investigation). The \"obvious\" exception in EU Art. 50(1) works the same way.",
            "first_step": "For each touchpoint without notice, record in one line which exception applies, with a screenshot of the name or screen that makes it obvious",
            "law_basis": "October 2026"
        },
        {
            "key": "transparency:t5",
            "diagnostic": "AI Transparency Requirements",
            "number": 5,
            "question": "If you use AI that infers emotions from faces or voices, or sorts people using biometric data, do you tell the people affected that it is in use and how it works?",
            "options": [
                "Yes — prior notice, explanation of how it works, and a legal basis (e.g., consent)",
                "Notice of use only (no explanation of how it works)",
                "No notice",
                "N/A — no emotion recognition or biometric categorization"
            ],
            "provisions": {
                "kr": "No specific rule in Korea's AI Basic Act — Korea PIPA Art. 23 and Enforcement Decree Art. 18 item 3 (biometric data used to identify a person is sensitive data; separate consent)",
                "eu": "EU AI Act Art. 50(3) notice to persons exposed to emotion recognition or biometric categorization (from 2026-08-02) · emotion recognition at work and in education banned under Art. 5(1)(f) (since 2025-02-02)",
                "us": "Illinois BIPA 740 ILCS 14/15 (written notice and release before collecting biometrics) — no general notice rule for emotion recognition"
            },
            "why": "EU AI Act Art. 50(3) requires deployers of emotion recognition and biometric categorization systems to inform the people exposed about how the system operates (from 2026-08-02), and Art. 5(1)(f) bans emotion recognition in workplaces and education except for medical or safety reasons. Korea's AI Basic Act has no specific rule, but biometric data used to identify a person is sensitive data under Korea PIPA Art. 23 and needs separate consent.",
            "first_step": "Find and list every such feature: call-center sentiment analysis, in-store cameras, video interview analysis, etc.",
            "law_basis": "October 2026"
        },
        {
            "key": "transparency:t6",
            "diagnostic": "AI Transparency Requirements",
            "number": 6,
            "question": "If you make automated decisions using personal data, have you published (e.g., on your website) the fact and purpose, the main types of personal data, the factors considered, and how to refuse or request an explanation?",
            "options": [
                "Yes — all five items published in plain language",
                "Partly covered in the privacy policy",
                "Not published",
                "N/A — no automated decisions based on personal data"
            ],
            "provisions": {
                "kr": "Korea PIPA Art. 37-2(4) · Enforcement Decree Art. 44-4(1) (five items to publish) and (2) (standardized, systematized terms people can easily understand; charts and images allowed)",
                "eu": "GDPR Art. 13(2)(f) and 14(2)(g) — existence of automated decision-making, logic involved and envisaged consequences",
                "us": "CCPA regulations §7220 pre-use notice for ADMT (2027-01-01) · Colorado SB 26-189 notice (2027-01-01)"
            },
            "why": "Korea PIPA Art. 37-2(4) requires you to publish the criteria and process of automated decisions and how personal data is processed, in a form people can easily find, and Enforcement Decree Art. 44-4 lists five items and requires standardized, systematized terms that people can easily understand (in force since 2024-03-15). This page is the first thing customers and regulators look at, and it is where refusal and explanation requests start. GDPR Art. 13(2)(f) requires the same information at the time of collection.",
            "first_step": "Write one page per decision type covering the five items in Decree Art. 44-4(1), using examples instead of jargon",
            "law_basis": "October 2026"
        },
        {
            "key": "transparency:t7",
            "diagnostic": "AI Transparency Requirements",
            "number": 7,
            "question": "If a customer asks \"Why did the AI decide this about me?\", can you produce an explanation of their decision covering the outcome, the main types of personal data used, the main criteria and the process?",
            "options": [
                "Yes — individual explanations from a standard template and decision logs",
                "Only a general description of how it works",
                "No way to explain",
                "N/A — AI is not used for decisions about individuals"
            ],
            "provisions": {
                "kr": "Korea PIPA Art. 37-2(2) · Enforcement Decree Art. 44-3(2) (outcome, main data types, main criteria, process) · Korea's AI Basic Act Art. 34(1) item 2 (explanation measures for high-impact AI)",
                "eu": "GDPR Art. 15(1)(h) (CJEU C-203/22: explain the procedure and principles actually applied) · EU AI Act Art. 86 right to explanation",
                "us": "Colorado SB 26-189 plain-language explanation within 30 days of an adverse outcome (2027-01-01) · CCPA regulations §7222 ADMT access right (2027-01-01)"
            },
            "why": "On request, Korea PIPA Enforcement Decree Art. 44-3(2) requires a \"concise and meaningful explanation\" covering the outcome, the main types of personal data used, the main criteria including how those data affected the decision, and the process. In C-203/22 (27 February 2025) the CJEU held that the explanation must let the person understand and challenge the procedure and principles actually applied. For high-impact AI, explanation measures are also mandatory under Art. 34(1) item 2 of Korea's AI Basic Act. Without decision logs an explanation cannot be built after the fact, so this usually needs engineering work.",
            "first_step": "Design logging so each decision automatically records input data types, outcome and the 3–5 most influential factors",
            "law_basis": "October 2026"
        },
        {
            "key": "transparency:t8",
            "diagnostic": "AI Transparency Requirements",
            "number": 8,
            "question": "Do you have a channel for refusal, explanation and review requests, and does someone with authority to change the decision reconsider it and reply in writing within 30 days?",
            "options": [
                "Yes — channel, 30-day deadline, empowered reviewer and case log all in place",
                "Handled case by case (no deadline or log)",
                "No channel for requests",
                "N/A — AI is not used for decisions about individuals"
            ],
            "provisions": {
                "kr": "Korea PIPA Art. 37-2(3) · Enforcement Decree Art. 44-3(1) and (5) (re-processing with human involvement; within 30 days, extendable twice) · Art. 75(2) item 24 administrative fine up to KRW 30 million",
                "eu": "GDPR Art. 22(3) human intervention, right to express a view and contest · Art. 12(3) reply within one month",
                "us": "Colorado SB 26-189 right to request meaningful human review after an adverse outcome (2027-01-01)"
            },
            "why": "On a refusal or explanation request, Korea PIPA Art. 37-2(3) requires you, absent a justifiable reason, to take the necessary step — stop applying the automated decision, re-process it with human involvement, or explain it (decisions based on consent, law or contract cannot be refused, so you answer those with an explanation) — and Enforcement Decree Art. 44-3(5) requires action in writing within 30 days of the request (extendable twice by 30 days for good reason). Failing to comply without a justifiable reason carries an administrative fine of up to KRW 30 million (Art. 75(2) item 24). A reviewer who cannot change the outcome is unlikely to count as human intervention.",
            "first_step": "Add a \"refuse, explain or review\" button or contact point to decision screens and emails",
            "law_basis": "October 2026"
        },
        {
            "key": "transparency:t9",
            "diagnostic": "AI Transparency Requirements",
            "number": 9,
            "question": "If you provide high-impact AI, have you posted (e.g., on your website) a summary of your explanation and user-protection measures, and the name and contact details of the person responsible for oversight?",
            "options": [
                "Yes — summary plus the responsible person's name and contact details",
                "Partly posted (e.g., no contact details)",
                "Not posted",
                "N/A — no high-impact AI provided"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 34(1) items 2–4 · Enforcement Decree Art. 27(1) (post summaries of the measures and the overseer's name and contact; trade secrets excluded)",
                "eu": "EU AI Act Art. 26(11) informing persons subject to high-risk AI · Art. 26(7) informing workers in advance (from 2027-12-02)",
                "us": "NYC Local Law 144 bias audit summary posted and candidate notice 10 business days before use · Colorado SB 26-189 notice (2027-01-01)"
            },
            "why": "Art. 34(1) of Korea's AI Basic Act makes explanation measures, user protection and human oversight duties that high-impact AI operators \"must perform\", and Enforcement Decree Art. 27(1) requires a summary of those measures and the overseer's name and contact details to be posted at your office or on your website (trade secrets may be left out). Breaches can lead to fact-finding and a corrective order under Art. 40, and ignoring a corrective order carries an administrative fine (Art. 43(1) item 3). Post this after the explanation approach (Q7) is settled.",
            "first_step": "Write 3–5 line summaries of the risk management policy, explanation measures and user-protection measures, marking trade secrets to leave out",
            "law_basis": "October 2026"
        },
        {
            "key": "transparency:t10",
            "diagnostic": "AI Transparency Requirements",
            "number": 10,
            "question": "If you use third-party AI (models, APIs, solutions), have you obtained the materials needed to interpret and explain its outputs (instructions for use, main criteria, training data overview, limitations), with a contract clause requiring them?",
            "options": [
                "Yes — contract clause and materials in hand",
                "Public documentation only (no contract clause)",
                "No materials",
                "N/A — only in-house AI, no third-party AI"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Enforcement Decree Art. 27(4) (deployers may request materials; developers endeavor to cooperate) · Art. 27(3) (no major change of function = developer's measures count)",
                "eu": "EU AI Act Art. 13 instructions for use of high-risk AI (interpreting outputs, limitations, human oversight; from 2027-12-02) · Art. 53(1)(b) GPAI information for downstream providers (since 2025-08-02)",
                "us": "Colorado SB 26-189 developer documentation for deployers (2027-01-01)"
            },
            "why": "Even if you did not build the AI, the duty to explain it to customers stays with the company offering the service. Enforcement Decree Art. 27(4) lets deployers ask developers for materials needed for the Art. 34 duties, but the developer only has to endeavor to cooperate, so it is safer to secure this by contract. If you use the system without a major change of function, the developer's measures count as yours (Art. 27(3)). In the EU, providers of high-risk AI must give deployers instructions for use (Art. 13).",
            "first_step": "List, for each third-party AI in use, the materials received (instructions, model card, limitations, training data overview)",
            "law_basis": "October 2026"
        },
        {
            "key": "transparency:t11",
            "diagnostic": "AI Transparency Requirements",
            "number": 11,
            "question": "Do you check that your AI notices and explanations are understood by real users (including older people, children, people with disabilities and non-native speakers), and provide them in accessible forms such as screen-reader and audio?",
            "options": [
                "Yes — user-tested and accessibility-checked",
                "Written in plain language, but not tested or checked",
                "Legal wording used as is"
            ],
            "provisions": {
                "kr": "Korea PIPA Enforcement Decree Art. 44-4(2) (plain terms, visual aids) · Korea's AI Basic Act Enforcement Decree Art. 23(3) item 2 (for Art. 31(3) notices, consider the age and physical and social circumstances of the main users)",
                "eu": "EU AI Act Art. 50(5) clear, distinguishable and meeting accessibility requirements · GDPR Art. 12(1) concise, clear and plain language",
                "us": "Colorado SB 26-189 plain-language explanation · CCPA regulations §7003 readability and accessibility of notices"
            },
            "why": "A notice or explanation only works if people understand it. Korea PIPA Enforcement Decree Art. 44-4(2) requires standardized, systematized terms that people can easily understand in automated-decision disclosures, and EU AI Act Art. 50(5) requires notices to meet accessibility requirements. Korea's Enforcement Decree Art. 23(3) asks you to consider the age and physical and social circumstances of the main users when giving notice of realistic synthetic content. Hard-to-read wording leads to complaints and to disputes claiming that no real explanation was given.",
            "first_step": "Rewrite notices and explanations in plain language that a 12- to 14-year-old could follow (one idea per sentence) and localize them for your main languages",
            "law_basis": "October 2026"
        },
        {
            "key": "transparency:t12",
            "diagnostic": "AI Transparency Requirements",
            "number": 12,
            "question": "Do you keep versions of notice screens and wording, explanation and refusal requests with their outcomes, and human review records, with defined retention periods (e.g., 5 years for high-impact AI evidence)?",
            "options": [
                "Yes — versions, requests and outcomes kept with set retention periods",
                "Partly (e.g., support tickets only)",
                "No records kept"
            ],
            "provisions": {
                "kr": "Korea's AI Basic Act Art. 34(1) item 5 · Enforcement Decree Art. 27(2) (keep evidence of measures for 5 years) · Art. 40 submission of materials in fact-finding",
                "eu": "EU AI Act Art. 26(6) deployers keep logs for at least six months (from 2027-12-02) · GDPR Art. 5(2) accountability",
                "us": "Colorado SB 26-189 keep compliance records for at least 3 years (2027-01-01)"
            },
            "why": "You need to be able to show that notices and explanations were given. Enforcement Decree Art. 27(2) requires high-impact AI operators to keep documents evidencing the Art. 34 measures for 5 years, and a fact-finding investigation under Art. 40 can demand them. Colorado SB 26-189 requires compliance records to be kept for at least 3 years, and EU AI Act Art. 26(6) requires deployers of high-risk AI to keep logs for at least six months.",
            "first_step": "Keep a version log with the date and a screenshot each time notice wording changes",
            "law_basis": "October 2026"
        }
    ]
}