Since 22 January 2026, the Republic of Korea has required an operator of high-impact AI to implement human management and supervision of it. The Framework Act on the Development of Artificial Intelligence and Establishment of Trust is the first comprehensive AI statute in the Asia-Pacific region, and Article 34 is its operative clause for the systems it treats as most consequential: those used in energy supply, health care, employment, education and other areas “that have a significant impact on the protection of human life, physical safety, and basic human rights”.

Where the Act requires human management and supervision of a high-impact system, does it say what a record of that supervision has to show, or only that supervision and a document must exist?

Article 34, in full

Six measures, and the two that matter to this question sit next to each other:

All six are introduced by one clause: operators “must implement the following measures as prescribed by presidential decree” to ensure safety and reliability. The Act names the measures and leaves their content to subordinate rulemaking it does not itself state.

Item 4 and item 5 sit beside each other, and nothing connects them

Item 4 is “Human management and supervision of high-impact AI”. Item 5 is “Preparation and storage of documents that demonstrate measures taken to ensure AI safety and reliability”. Read together, an operator must supervise and must keep documents proving it has measures. What the text does not ask is that the kept document show anything about a particular act of supervision: who exercised it, when, over which decision, or what they did. The document item 5 requires is evidence that a supervision policy exists, not evidence that supervision occurred in any given case.

That is the same shape as every other instrument read on this site, reached independently in a jurisdiction and a legal tradition none of the others share.

The explanation duty is qualified twice over

Item 2 requires a plan “to provide explanations for AI-generated outputs, including the key criteria used to derive such outputs, and an overview of the learning data”, but only “to the extent that it is technically feasible”. A plan to explain outputs in general is not a record that any particular output was explained to any particular person, and the feasibility qualifier means even the plan is conditional.

A route around all six

Article 34(3): if an operator implements “equivalent measures” under other laws and regulations prescribed by presidential decree, it “shall be deemed to have implemented the measures” required by Article 34(1). So the six named measures, including human management and supervision, are not the only route to compliance, and an operator relying on a different framework's human-oversight provision is not measured against Article 34(1)(4)'s wording at all.

Read across the Act

Zero occurrences of record, records, log, logs, logging, audit, retain or retention, checked against the whole committed text rather than one article. A statute can require supervision, require a document, and never once use a word this site checks every instrument for, and this one does.

What this reading does not have

Article 34(1) delegates its content to Presidential Decree No. 36053, which took effect the same day as the Act, and the Ministry of Science and ICT separately published operator obligation guidelines on the same date. Neither was read for this entry. Both are Korean-language instruments, and the same rule this site applies to ISO/IEC 42001's paywall applies here: a reading that cites the clause it rests on cannot cite text it has not verified against a committed source. What the decree and the guidelines add to Article 34, if anything, is recorded here as not established rather than assumed from secondary summaries, several of which describe the Act as requiring “a mechanism for human intervention and supervision” in stronger terms than the enacted text itself supports.

This is not a claim that Korean regulators have failed to specify anything. A decree this reading has not read may say a great deal. The claim is narrower: the Act that has been in force since 22 January 2026 does not say it, and a deployer reading only the Act would not know it either way.

Where this sits against everything else read here

Twelve of twenty instruments in this library's private reading now ask a record to show who intervened in a decision. Korea's Article 34(1)(4) is one of them: the fact is record-answerable, and the Act does not ask for it. The pattern holds across a right created in 2018, a right created in 2023, a right created in 2026, and now a statutory measure created in 2026 in a different hemisphere under a different legal tradition. The gap is not a drafting accident anywhere it appears, and it is not particular to Europe or to the United States.

If you operate under Article 34

A reading of your own records against this Act specifically, scoped to Korea rather than to the twenty other instruments this library also tracks. You already know which country you operate in; the answer should not require sifting Colorado and the EU AI Act out of the result to find the one clause that is actually yours. You get the obligations a record can speak to, which of yours evidence them, and the ones above named as not established rather than guessed at.

It does not make you compliant, and nobody selling software can. It gathers what a record shows against Article 34(1)(4) and (1)(5) and is honest about the four items above that are facts about a decree this reading has not read, not about a record. Ask: troy@machinetestimony.com. If the decree turns out to answer what the Act does not, we will say so rather than sell past it.

Check it

The Act is committed in full at census/sources/kr-ai-basic-act.txt, the English translation prepared by the Center for Security and Emerging Technology following the Korea Legislation Research Institute's translation guidelines, sourced from the Korean Law Information Center. Every count on this page is recomputed from that file by the test suite rather than written down once and trusted.

A reading is wrong in the ordinary way readings are wrong, which is why every statement above names the article, the item number, or the sentence it rests on.

Citing this

The readings are CC BY 4.0, which asks for attribution, so the reference is here rather than left to be composed. This block is generated from the page it sits on, so a date that moves here moves in the citation too.

Clifford, T. (2026). The measure is named. Its content is a decree this reading does not have. Machine Testimony. https://machinetestimony.org/south-korea/

@misc{clifford2026southkorea,
  author = {Clifford, Troy},
  title  = {The measure is named. Its content is a decree this reading does not have},
  year   = {2026},
  note   = {Machine Testimony, read 13 September 2026},
  url    = {https://machinetestimony.org/south-korea/},
}

This page carries no DOI. It cites its dated URL, and saying so is the point: a citation naming a deposit that does not exist is worse than one naming a page that does.