AI Automation ·
What evidence should Korean AI exporters retain before the EU marking deadline?
The European Commission's AI Act FAQ says transparency obligations began applying on August 2, 2026, while certain providers with AI systems already on the market receive until December 2, 2026 to comply with the marking and detection requirement under Article 50(2).[1] Korea's AI Basic Act and implementing decree entered into force in January 2026.[2] Neither fact establishes automatic cross-border compliance.
Narrowing the question
Consider a Korean supplier selling a generative media API to European customers. A visible notice to a user is not necessarily the same as a machine-readable output marking. Applicability also depends on provider role, output and time of market placement. What documentary and technical evidence must a specific version retain?
What the official sources support
The EU FAQ differentiates provisions enforceable from August 2 from the limited December 2 compliance transition.[1] It does not defer all AI obligations until December. Korea's ministry confirmed the Korean Act and Decree became effective January 22.[2] The legal scopes and implementation methods are not interchangeable. A product-level analysis is therefore necessary; this article is not a legal opinion about a named service.
| Dimension | EU service desk[1] | Korean statutory context[2] |
|---|---|---|
| Timing | Some transparency obligations effective in August 2026 | Basic Act effective January 2026 |
| Transition | Article 50(2) marking transition for qualifying earlier systems | EU transition is not a Korean exemption |
| Evidence | Record market entry, role and output marking | Analyze domestic obligations independently |
Alternatives
Option A records a per-version analysis of EU market presence, role, applicable duties and transition grounds. This avoids unnecessary modifications but must be repeated when the product changes. Option B implements durable content marking by default for EU deliveries and manages documented exceptions. It may simplify policy operations but creates compatibility, format and quality costs. Local counsel should validate the legal interpretation.
Verification design
Maintain product version, release date, output types, display notices and machine-detection behavior. Test the original file and transformed copies after compression, cropping or recoding. Where a required marker disappears, hold that distribution path until corrected. These are proposed technical acceptance tests, not an approved regulatory certification.
Conclusion and next question
The real task is establishing scope and preserving proof, not merely watching a deadline. If downstream customers remove metadata, what can a supplier technically guarantee and how should contracts allocate responsibility?