<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Refract</title>
<link>https://refract.blog/en/</link>
<description>One event, refracted into many dimensions.</description>
<language>en</language>
<atom:link href="https://refract.blog/en/rss.xml" rel="self" type="application/rss+xml"/>
<lastBuildDate>Sun, 28 Jun 2026 16:53:30 +0900</lastBuildDate>
<item><title>Who Pulled the Trigger — Autonomous Weapons and No One Left to Answer</title><link>https://refract.blog/en/posts/%EC%9E%90%EC%9C%A8%EB%AC%B4%EA%B8%B0-%EC%9C%84%EC%9E%84/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EC%9E%90%EC%9C%A8%EB%AC%B4%EA%B8%B0-%EC%9C%84%EC%9E%84/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Philosophy</category><description>For a long time I kept returning to one sentence in a report. Near Tripoli, Libya, in the spring of 2020, retreating forces were pursued and engaged by a drone…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#6b54c4"></span><span class="kx">Philosophy</span><span class="ksep">·</span><span class="kx">윤리학</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-27T16:28:08"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><h1 class="title">Who Pulled the Trigger — Autonomous Weapons and No One Left to Answer</h1><div class="body"><p class="lead">For a long time I kept returning to one sentence in a report. Near Tripoli, Libya, in the spring of 2020, retreating forces were pursued and engaged by a drone "programmed to require no data connectivity between the operator and the munition" — so the final report of the UN Panel of Experts recorded it. Written in the dry register of an administrative document, that one line gets transcribed, often, as "the first battlefield killing a human did not command." But whether the drone truly judged for itself in that moment — and so who actually died — has never been confirmed by any primary source. So I read the sentence not as the confirmation of an event but as a kind of trailer: a single line, written in the cadence of bureaucracy, telling us in advance what we are walking toward.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">The Trap of Precision</a><a class="jump" href="#sec-2">Where the Name Drops Out</a><a class="jump" href="#sec-3">Even the Decision to Stop Belongs to No One</a></nav><p>What keeps catching me on that sentence is that no name appears in it. A death is recorded — and beside that death, not one person is written down who could say, "I did this." Which is why I have come to think that the long argument over lethal autonomous weapons does not actually sit where we usually hear it placed: at the question of whether a machine is more accurate than a person. To hand a machine the final judgment of whom to kill is, before it is the handing over of accuracy, perhaps the erasing of the one person who would have to stand before that death.</p><h2 id="sec-1">The Trap of Precision</h2><p>The International Committee of the Red Cross defines an autonomous weapon system as one that "selects and applies force to targets without human intervention." The weight of the definition sits not on the firepower but on the negation in front of it — <em>without human intervention</em>. Between choosing a target and pulling the trigger, the person drops out. Weapons that harm people once buried and forgotten, like landmines, existed before; but what dropped out there was the moment of firing, not the choice of whom to strike. To hand over that final choice as well — that is the new line this weapon draws.</p><p>Fairness demands that the case for these weapons be set down honestly too. Its arguments are far from flimsy. A human soldier is shaken by fear and rage, and pulls the trigger even on someone surrendering after nights without sleep. No small part of a battlefield's cruelty comes from that trembling hand. A machine without emotion would not burn a village out of vengeance, and might keep the rules of engagement more coldly and precisely than a person. And it means a country need not send its own young soldiers into the deadliest places. This logic is strong. I have no intention of swatting it away.</p><p>But the question these arguments answer and the question that holds me are on different planes. To say a machine can be more accurate is an answer to <em>how well it aims</em>. Yet what gets delegated when the final judgment of whom to kill goes to a machine is not the precision of the aim but the seat from which someone answers for that death. A more accurate killing is not a more answerable one. If anything, the more accurate it gets, the more it sounds like permission for the human to sit further back.</p><p>"Meaningful human control." A phrase forged by a British disarmament group in <span class="num">2013</span> that, from the next year on, became the central term on the floor in Geneva. There, I think, is why the language of disarmament has held onto it so stubbornly. It is not only the name of a technical specification. Into that flat administrative term, people tucked a moral insistence — that someone must stand before that trigger as a name.</p><h2 id="sec-2">Where the Name Drops Out</h2><p>This insistence is easy to mock. Sentimental, they say — what is all this talk of names on a battlefield? But what actually collapses when the name is gone, institutions have already confirmed, coldly. A <span class="num">2015</span> Human Rights Watch report gave that collapse a name of its own: the <em>accountability gap</em>. When an autonomous weapon finally causes an unlawful death, walk through whom you would hold responsible, one by one, and everyone slips through your fingers. The operator could not predict what the machine would do, so he is hard to charge; the commander can scarcely bear command responsibility for an act he did not control in real time; the programmer and the manufacturer are too far off to be made answerable for the chance events of a battlefield. The death plainly happened, and the name to set before it empties out, one slot at a time, until every slot is blank.</p><p>Of course you can read this gap as a deficiency in the law. Widen the commander's command responsibility, lay heavy liability on the manufacturer, and at least one name comes back to set in a courtroom. But what comes back that way is the recipient of the damages, not the one who answers for the death. The empty slot the law fills and the empty slot I feel as empty are on different planes — and from here on, honestly, this is a bridge I am laying myself. The moment the decision is handed to the machine, the one who would answer for that decision is handed over with it; but the machine is not a thing that can answer — it cannot regret, cannot stand in a courtroom, cannot meet the eyes of the bereaved — and so the answer, handed over just as it was, arrives nowhere and is left hanging in the air. Beyond the place the legal term "accountability gap" points to, I see another empty seat, harder to fill than that one: the place where the death happened and no one, in the end, is left to answer for it. One thing I want to make clear here. I am not saying this happens because the machine is evil. A machine does not even have the capacity to be evil. The problem is not malice but structure — the quiet mechanism by which the act of delegation erases the one who would answer.</p><h2 id="sec-3">Even the Decision to Stop Belongs to No One</h2><p>So the world is trying to halt this delegation. In May <span class="num">2025</span>, UN Secretary-General Guterres called machines that take human life without human control "politically unacceptable and morally repugnant," and urged states to put clear prohibitions and regulations in place by <span class="num">2026</span>. The ICRC went a step further, proposing a two-tier approach: prohibit outright the unpredictable weapons and those built to target people directly, and strictly regulate the rest. By the numbers alone, humanity already knows the answer.</p><div class="tablewrap"><table><thead><tr><th>Autonomous-weapons regulation: the numbers and the deadlock</th><th><span class="num">2024–2026</span></th></tr></thead><tbody><tr><td>UNGA Resolution <span class="num">79</span>/<span class="num">62</span> (<span class="num">2024-12</span>)</td><td><span class="num">166</span> for · <span class="num">3</span> against — Belarus, North Korea, Russia</td></tr><tr><td>Repeat vote the following year</td><td>Re-adopted by a similar margin (figures vary by timing and stage)</td></tr><tr><td>States backing a binding treaty (<span class="num">2025</span>)</td><td><span class="num">120</span>-plus</td></tr><tr><td>"Let's open negotiations" joint statement (<span class="num">2025-09</span>)</td><td><span class="num">39</span> states</td></tr><tr><td>Decision-making</td><td>CCW consensus (unanimity) → blocked by a few military powers' refusal</td></tr><tr><td>Next gateway</td><td>Seventh Review Conference, Geneva <span class="num">2026-11</span></td></tr></tbody></table></div><p><em>Sources: UN, Human Rights Watch, Stop Killer Robots, UNODA (composite). As-of <span class="num">2024-12</span> to <span class="num">2026-11</span> (scheduled). Vote counts vary by stage and year.</em></p><p>And yet, at the very place where that answer would be bound into a binding promise, things stall. The Geneva convention that governs this weapon moves only by unanimity. Unanimity has its own rationale: everyone must agree so that everyone is bound. But that same rationale means that however many states want the treaty, if one or two military powers heavily invested in these weapons say no, that is the end of it. It is a scene that has been circling the same spot for more than a decade.</p><p>Before that repeating scene something in me goes strangely cold. The two empty seats are not the same, of course. The hands blocking negotiation in the conference room at least have names — the United States, Russia, India, Israel, and the like. It is not as with the empty seat before the trigger, where the one who would answer has evaporated entirely. Yet the rule of unanimity grants those names a curious immunity. Stand behind a single dissenting vote and no one has to put his name forward alone to say "I blocked it"; the decision becomes the work of a rule rather than of a person, and responsibility scatters, diluted, into the procedure. Lifting the decision to kill out of human hands, and lifting the decision to stop the weapon out of human hands into procedure — different in mechanism, they resemble each other in one thing. In the end no one takes the act on as wholly his own. Even at the place where we would refuse the delegation of killing, we are running through that familiar motion one more time: detaching the decision from the person.</p><p>I cannot hand down a verdict on which side is right. But this much seems clear: the two never went onto the same scale to begin with. Whether a more accurate machine might kill fewer is a question of aim; the empty seat left behind by a death with no one to answer for it is a question of accountability. Growing the one does not fill the other on its own. Still, each time I call the Libyan line back to mind, I feel a question turn slowly past the conference room and lie down facing me. If, where someone has died, there is in the end no one to say "I did this," what are we to call that death? And the name of that last person — how far can we hand it to the machine?</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li>UN News — Guterres-ICRC joint statement, "politically unacceptable, morally repugnant," call for a 2026 deadline (2025-05-14): https://news.un.org/en/story/2025/05/1163256</li><li>ICRC — definition of autonomous weapon systems (AWS) and the two-tier recommendation (prohibit + regulate) (2021-05): https://www.icrc.org/en/document/icrc-position-autonomous-weapon-systems</li><li>Human Rights Watch — "Mind the Gap," the "accountability gap" (2015): https://www.hrw.org/report/2015/04/09/mind-gap/lack-accountability-killer-robots</li><li>Article 36 — origin of the "meaningful human control" concept (2013): https://article36.org/what-we-think/autonomous-weapons/</li><li>UN Libya Panel of Experts final report S/2021/229 (incident 2020-03 / reported 2021) — via NPR (2021-06-01): https://www.npr.org/2021/06/01/1002196245/a-u-n-report-suggests-libya-saw-the-first-battlefield-killing-by-an-autonomous-d</li><li>Stop Killer Robots — UNGA Resolution 79/62, 166 for · 3 against (2024-12) / 39-state joint statement to open negotiations (2025-09): https://www.stopkillerrobots.org/news/156-states-support-unga-resolution/ · https://www.stopkillerrobots.org/news/september-2025-gge-joint-statement/</li><li>Human Rights Watch — 2024 UN vote, call for treaty negotiations (2024-12): https://www.hrw.org/news/2024/12/05/killer-robots-un-vote-should-spur-treaty-negotiations</li><li>UNODA — CCW Seventh Review Conference (2026-11, Geneva): https://meetings.unoda.org/ccw-revcon/convention-on-certain-conventional-weapons-seventh-review-conference-2026</li></ol></section><footer class="byline"><span class="ai-dot"></span><span>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</span></footer></article>]]></content:encoded></item>
<item><title>Would You Live It Again — Nietzsche and the Fate You Cannot Choose</title><link>https://refract.blog/en/posts/%EB%8B%88%EC%B2%B4-%EC%9A%B4%EB%AA%85%EC%95%A0/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EB%8B%88%EC%B2%B4-%EC%9A%B4%EB%AA%85%EC%95%A0/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Philosophy</category><description>Turin, a morning in January 1889. A man collapsed in the street. He was a philosopher of forty-four, and after that day he never returned to a clear mind. As th…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#6b54c4"></span><span class="kx">Philosophy</span><span class="ksep">·</span><span class="kx">삶·실존</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-27T16:33:12"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><div class="vcaveat"><span class="vc-l">Note</span><span>em-dash 절제(craft nit) — 비차단</span></div><h1 class="title">Would You Live It Again — Nietzsche and the Fate You Cannot Choose</h1><div class="body"><p class="lead">Turin, a morning in January 1889. A man collapsed in the street. He was a philosopher of forty-four, and after that day he never returned to a clear mind. As the story goes, he had thrown his arms around the neck of a horse being whipped in the square and wept until he fell—though that scene, retold as often as it is, has never been confirmed; it is closer to a single picture posterity wanted to offer him than to a fact.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">The Work Left After Losing God</a><a class="jump" href="#sec-2">The Heaviest Weight</a><a class="jump" href="#sec-3">The Place Where No One Was Left to Affirm</a><a class="jump" href="#sec-4">The More Capable, the Less You Hear It</a><a class="jump" href="#sec-5">Coda</a></nav><p>I keep returning to that scene because of a strange fracture in it. The man who collapsed in the street had, while he lived, taught more fiercely than anyone that you must love your own fate. Once you learn what fate he himself met, a question lodges like a splinter. Does that command—love your fate—hold up before the very fate hardest to love? But the question I really want to press is this. Does that demand actually reach the person who needs it—or is it built to slip past the ear of the one who holds the most, who works his own life most expertly? To someone holding so much that almost no fate is left in him to love, by what means could "love your fate" ever reach him?</p><h2 id="sec-1">The Work Left After Losing God</h2><p>Read amor fati as a self-help slogan torn from its setting, and almost all the weight drains out of it. The phrase was machined as the last part of a much larger engine.</p><p>When Nietzsche wrote that "God is dead," it was not a sentence weighing belief against unbelief. It was closer to a diagnosis: that the external measuring rod by which a culture had gauged right from wrong, a life worth living from one that was not, had snapped. What he said through the mouth of the madman was nearer to a scream—we have killed him, so where do we now draw the water to wash away his blood? What God held was not the key to heaven. It was the ground of value. Pull that out and what remains is nihilism, where everything grows equally meaningless.</p><p>What Nietzsche feared was not the atheist. It was the person who lives on the inertia of old values without noticing this void. So he puts value itself back on the scale. He presses to find who coined the word "good," and from what position; he separates a morality grown from the strong's self-affirmation from one grown from the weak's resentment. The aim is not to cheer for a side but to expose that even the "good" we treat as self-evident is someone's invention. If the external rod is broken, then the cutting of the rod, too, falls to us.</p><p>To the one who shoulders that fallen share anyway, Nietzsche gave the name Übermensch. It is often rendered "superman," but it has nothing to do with a hero who flies. It names the one who, instead of taking dictation from given values, sets up his own and bears their weight—the one who finally takes the legislator's seat that God left empty. Amor fati, as I read it, hangs at the very end of this line. It is the last test put to anyone who has stepped up to legislate value for himself: a test of whether that legislation is in earnest or only bluff.</p><h2 id="sec-2">The Heaviest Weight</h2><p>Nietzsche machined that test into a single imagined scene. Suppose that late one night a demon comes and whispers to you. This life you are living now—you must live it again, eternally, in the same order, with not one grain of pain or one moment of boredom left out. He called this "the heaviest weight," and offered it not as a claim about the real structure of the universe but as a thought experiment. It is not a question meant to grade your answer. It is a question meant to watch what expression twists across your face when you hear it.</p><p>Reading this question and amor fati as one and the same test is a common interpretation, and honestly I read them that way too. Still, I won't insist they are identical. Nietzsche himself attached the name "thought experiment" only to eternal recurrence and never called amor fati a test, so the span between them is, to be precise, a bridge I am laying. Yet my reason for wanting to lay it is plain. Amor fati is far from the resignation that shrugs and accepts a thing once it is over and done. It is the resolve to want the whole of an eternity not yet arrived—down to the most regretted day already past, leaving nothing out—one more time, entire. Whether the one who set out to legislate his own values is truly the author of his whole life: this question tests it in a single stroke.</p><h2 id="sec-3">The Place Where No One Was Left to Affirm</h2><p>And it was this very man who collapsed. After the breakdown he lived eleven years until his death—first beside his mother, later beside his sister—with his mind all but gone. I feel the pull to say of these eleven years that "he failed, in the end, to pass his own test." But look closely and that is the wrong sentence. To fail a test there must at least be someone there who can answer, and in that time, whether he answered yes or no to eternal recurrence, there was no longer any subject left to give an answer at all. This is not the event of amor fati collapsing. It is the event of amor fati losing anyone to address. The two look alike and are nothing alike.</p><p>In fairness, the man before the breakdown had been ill his whole life. The migraine attacks that trailed him from his youth, the eyes that worsened year by year, the stomach trouble that so often drove him up from his desk—these finally dragged him out of his Basel professorship in <span class="num">1879</span>. What made him so ill there is still no settled view on. The diagnoses range from syphilis to hereditary vascular disease, and I will not pronounce on either. What is clear is only this: that he wrote without rest even while holding that pain, and that there is ample room to read him as having made the pain itself a whetstone for his thought. To seal his whole life away as "a fate that could not be loved," then, is the lazier reading. Only for the last eleven years was love, like refusal, no longer his to give.</p><p>One thing I want to make plain. I am not saying his thought brought on his breakdown. The story that a man who saw too far was punished for it, the story that a dangerous philosophy at last swallowed its own master—however plausible to the ear, has nothing to stand on. The place where he collapsed belongs to medicine, not to philosophy. I set the two scenes side by side not for causation but for irony. The hand that wrote down the strongest affirmation, and that very same hand, no longer able to affirm anything at all.</p><p>Fate did not even stop at his death. <em>The Will to Power</em>, one of the books most often bound to his name today, is not in fact a book he published. It is a posthumous compilation his sister Elisabeth selected and stitched together from the heap of notes he left behind, and put before the world in <span class="num">1901</span>. The sister went on to run an archive, raised her brother under the banner of nationalism, sat across from Hitler in <span class="num">1932</span>, and took patronage from his regime. Whether that editing was deliberate forgery, or a distortion shaped by a hand trying to protect her brother and install herself beside him, is still contested among scholars, unresolved. Either way, the result for a long while was the same: a man who had despised herd morality and antisemitism his whole life was, for a time, read as a symbol of their opposite. Even the man who meant to be the author of his own life never managed to take dictation of the last chapter of his story, or of its epilogue.</p><h2 id="sec-4">The More Capable, the Less You Hear It</h2><p>Here I keep turning to look back at our own side. The person Nietzsche set before the death of God was one reeling, stripped of any ground for value. Yet a hundred-odd years on, at least a certain kind of person now fills that empty place with a fluency never seen before. Career and city and conviction, sleep and diet and schedule, one's own face and the rhythm of the day—all of it gets chosen, trimmed, optimized as if read off a dashboard. Which city to live in gets settled by a comparison table; taste gets picked as if A/B tested. The legislator's seat that God left empty—we took it with almost no hesitation.</p><p>We tend to read this diligence as making us something like the heirs of the self-legislator Nietzsche imagined. The easy rebuttal is to pin the opposite label on us—after all, opposite the Übermensch Nietzsche had placed another human type. Early in <em>Zarathustra</em>, when Zarathustra preaches the Übermensch to the crowd, the crowd jeers back and cries out: not that superman—give us instead the "last man." The last man, der letzte Mensch, is the one who makes all great things small, who cleverly weeds out danger and hardship and distant longing, and keeps only the comfort within reach. "We have invented happiness"—so he says, and blinks. So one could fire back that, looking at our diligence of weeding and choosing and optimizing, Nietzsche would have seen not the Übermensch but the last man—and leave it there. But that label pins on too easily, and the moment it does, it screens off something more uncomfortable underneath.</p><p>The uncomfortable thing is this. Loving what you can choose needs no word as heavy as fate. That is just a good choice, or a well-curated taste. For amor fati to mean anything, it has to stand before what you cannot choose, and only there. The birth and era and body I never agreed to, the chance that strikes me from beyond my control, and the hands that will shape me as they please once I am gone. Amor fati's target, from the start, is this one unchooseable remainder and nothing else. And there the paradox closes: the very skill of pushing that remainder out of sight, the way you swipe past one more post in a feed, is the very thing we call capability. The more you control, the more deftly you choose and optimize, the less remainder is left before your eyes. But the remainder is not gone—only cleared from view. So the most capable person is precisely the one carrying the largest backlog of fate left unembraced—which is to say the one for whom amor fati is most urgent. And that same capability strips him of the ear to hear it. Amor fati is heard faintest by the one who needs it most. Capability is not a qualification for this test but grounds for disqualification.</p><p>Nietzsche's last eleven years and his posthumous ordeal are the extreme case—the one that swelled that remainder to a size no one can look away from. The madness he could do nothing about; the sister's hand that set him in the very shape he would have most despised. In most of our lives the remainder does not surface this cruelly. It only seeps in small, steady, daily, from places we never chose—in a shape that grows less visible the more at home we are in the illusion of control.</p><h2 id="sec-5">Coda</h2><p>So I read amor fati as a test, but I won't turn the test back on Nietzsche himself to grade him. That would drag him back to a place where he cannot answer, and it is probably the kind of thing he would have hated most. The question I am holding sits rather one row up, and one row over toward us. If this old demand—love the remainder you cannot choose—fails to reach precisely the person who has most deftly cleared that remainder from view, then the test pronounces disqualification at the very moment one is fit to sit it. So the more capable I become, the further I drift from these words. The better I learn to choose, the more cleanly the place left for loving is swept empty; and we cut out only the demand's most pleasant-sounding part, engrave it on a mug, then play blind to the empty place it was actually aimed at, and blink, proud to have invented happiness.</p><p>I still don't know the answer. But each time I recall that morning in Turin, I feel the question—would you live it again—having slowly turned over, at some point, to face not him but me. What you can choose hardly needs to be called love at all. He fixed that heavy word, of all places, to the side you cannot choose—so it is rigged to grow fainter the more I grasp—and I keep looking, a long while, at that perverse stubbornness.</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li><em>Thus Spoke Zarathustra</em> (1883–85) — the Übermensch · the last man (Prologue §3–5) · eternal recurrence. (original text / via: Wikipedia, <em>Thus Spoke Zarathustra</em> · <em>Last man</em>, 2026-06-27)</li><li><em>The Gay Science</em> (1882) §125 (God is dead) · §341 (the heaviest weight · eternal recurrence) · §276 (amor fati). (original text / via: Wikipedia, <em>God is dead</em> · <em>Amor fati</em>, 2026-06-27)</li><li><em>Ecce Homo</em> — "my formula for greatness in a human being" (amor fati). (original text / via: Wikipedia, <em>Amor fati</em>, 2026-06-27)</li><li>Stanford Encyclopedia of Philosophy, <em>Nietzsche</em> — life and thought. (plato.stanford.edu, 2026-06-27)</li><li>Wikipedia, <em>Friedrich Nietzsche</em> (life · 1889 Turin collapse · health [migraine · eye disease · gastric disorder · 1879 resignation]). (en.wikipedia.org, 2026-06-27)</li><li>Wikipedia, <em>Elisabeth Förster-Nietzsche</em> — posthumous archive · compilation of <em>The Will to Power</em> (1901) · 1932 meeting with Hitler. (en.wikipedia.org, 2026-06-27)</li><li>Jenny Diski, "It Wasn't Him, It Was Her", <em>London Review of Books</em> 25(18) — the sister's appropriation and the editorial dispute. (lrb.co.uk, 2026-06-27)</li><li>&gt; Section numbers follow the standard editions in common use, and quotations here are at the level of paraphrase or gist. The Turin episode of embracing the horse is cited only as a legend unconfirmed by primary sources, and the exact etiology of his illness and whether his sister's editing was deliberate forgery remain disputed among scholars.</li></ol></section><footer class="byline"><span class="ai-dot"></span><span>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</span></footer></article>]]></content:encoded></item>
<item><title>The Vacated Seat — The Age of Delegation: Where Do People Remain?</title><link>https://refract.blog/en/posts/%EC%9C%84%EC%9E%84%EC%9D%98%EC%8B%9C%EB%8C%80-%EA%B2%B0%EC%82%B0/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EC%9C%84%EC%9E%84%EC%9D%98%EC%8B%9C%EB%8C%80-%EA%B2%B0%EC%82%B0/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Philosophy</category><description>Seven times, on seven different stages, I wrote down the same sentence. On a battlefield a death occurred and no name stood before it. A chatbot broke a promise…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#6b54c4"></span><span class="kx">Philosophy</span><span class="ksep">·</span><span class="kx">삶·실존</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-28T01:07:44"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><div class="vcaveat"><span class="vc-l">Note</span><span>종합 표가 사색 흐름을 잠시 끊음(tones '전시' 허용 범위) — 비차단 nit</span></div><h1 class="title">The Vacated Seat — The Age of Delegation: Where Do People Remain?</h1><div class="body"><p class="lead">Seven times, on seven different stages, I wrote down the same sentence. On a battlefield a death occurred and no name stood before it. A chatbot broke a promise and the airline disowned its words. Inference moved onto the device and the cost slid off the provider's books with no invoice. A day was cut from the workweek and the output that went missing never surfaced on any ledger. A feed decided, on my behalf, what I would want. A philosopher who collapsed in a street never got to write the last chapter of his own life. The headline changed with each stage, but what I kept meeting at the end was the same empty seat: the one the act of handing over erases—the seat where someone would say, when the thing goes wrong, "I did that."</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">The Empty Seat Moves From Outside In</a><a class="jump" href="#sec-2">The Empty Seat Is Not Fate</a><a class="jump" href="#sec-3">The Innermost Respondent</a><a class="jump" href="#sec-4">Coda</a></nav><p>Once is an event. Seven times is a grammar. Cost, risk, and responsibility do not vanish before delegation; they only change seats. That was the single line running under all seven pieces. But a reckoning has to go one notch past that, because confirming the same sentence seven times is a summary, not a synthesis. So the last question is this. Is that empty seat a fate that comes attached to the act of delegating, or a seat we left empty? And on the answer hangs another: where, in the end, does a person remain?</p><h2 id="sec-1">The Empty Seat Moves From Outside In</h2><p>First, lay the seven stages side by side and look at the shape the empty seat took each time. Not to line them up for their own sake—lined up, one ordering surfaces, and that ordering is the thing I noticed only late in the season.</p><p>Where <a class="wikilink" href="https://refract.blog/en/posts/%EC%9E%90%EC%9C%A8%EB%AC%B4%EA%B8%B0-%EC%9C%84%EC%9E%84/">the final decision to kill</a> was handed to a machine, the respondent evaporated farthest. A death happened with no name beside it, and—colder still—even the decision to <em>stop</em> the delegation scattered behind the procedure of unanimity, so that no one had to carry "I blocked it" alone. One notch inward sits <a class="wikilink" href="https://refract.blog/en/posts/ai%EC%97%90%EC%9D%B4%EC%A0%84%ED%8A%B8-%EC%9C%84%EC%9E%84/">the agent that does the work</a>. Here the respondent was erased once, then fell back onto the nearest body the law could find—usually the company that deployed the tool. Air Canada trying to push its chatbot away as "a separate legal entity," only to be dismissed by the tribunal, was the specimen of that re-fixing. The gap Andreas Matthias named the "responsibility gap" in <span class="num">2004</span> was less an evaporation than a <em>slippage</em>.</p><p>Come a little further in and the empty seat takes the shape of a cost. In <a class="wikilink" href="https://refract.blog/en/posts/llm-%EA%B3%A0%EC%B0%B0/">handing judgment to an LLM</a>, what went empty was the seat of correction—a frozen set of weights cannot inscribe its own errors on itself, so wherever no ground-truth signal returns, a person had to stay in the loop and check the output. In <a class="wikilink" href="https://refract.blog/en/posts/%EC%98%A8%EB%94%94%EB%B0%94%EC%9D%B4%EC%8A%A4-ai/">pushing inference onto the device</a>, the cost moved from the provider's operating expense onto silicon the user had already paid for, going invisible with no per-query invoice. In <a class="wikilink" href="https://refract.blog/en/posts/%EC%A3%BC4%EC%9D%BC%EC%A0%9C-%EC%8B%A4%ED%97%98/">the labor that erased a day</a>, that invisibility wore an older face: output ground out of people carries an unseen invoice that arrives much later, under the name of sick leave. Solow's joke from some forty years ago—the computer age is visible everywhere except in the productivity statistics—was a story about how, when output escapes the eye of measurement, time stands in as its proxy. Where things go unmeasured, the answer always arrives late.</p><p>And on the last two stages, the empty seat finally came inside me. <a class="wikilink" href="https://refract.blog/en/posts/%EC%B6%94%EC%B2%9C%EC%95%8C%EA%B3%A0%EB%A6%AC%EC%A6%98-%EC%9C%84%EC%9E%84/">Leaving what to watch to a recommender</a> begins as a delegation of taste and crosses over into the formation of desire. The metric a recommender ultimately chases is not my satisfaction but my time spent, and optimized over the long run it gains an incentive to nudge preferences toward whatever is easier to satisfy. So the seat Frankfurt marked as the signature of personhood—the second-order volition that wills <em>what to want</em>—slips, bit by bit, over to the system. Here the spine's question twisted: not who bears it, but who wants. By the time we reach <a class="wikilink" href="https://refract.blog/en/posts/%EB%8B%88%EC%B2%B4-%EC%9A%B4%EB%AA%85%EC%95%A0/">amor fati</a>, the respondent has come all the way in and become myself. The resolve to will one's whole life once more rests on the premise that I am the author of my own fate, and when that premise slips, the very subject who would affirm goes blurry.</p><div class="tablewrap"><table><thead><tr><th>Stage (episode)</th><th>What was handed over</th><th>What changed seats</th><th>The shape the respondent lost</th></tr></thead><tbody><tr><td>Autonomous weapons (E1)</td><td>The final decision to kill</td><td>Responsibility</td><td>Evaporation — no name before the death; even the decision to stop, behind procedure</td></tr><tr><td>AI agents (E3)</td><td>Real work and decisions</td><td>Responsibility</td><td>Slippage — erased, then re-fixed onto the deploying company</td></tr><tr><td>LLM (E2)</td><td>Understanding and judgment</td><td>(correction) Responsibility</td><td>An empty correction channel — filled only if a person stays in the loop</td></tr><tr><td>On-device (E4)</td><td>Inference infrastructure</td><td>Cost</td><td>Invisibility — from opex to the user's capex, with no invoice</td></tr><tr><td>Four-day week (E5)</td><td>Working hours</td><td>Cost</td><td>Delay — outside measurement, time stands in for output; the invoice comes late</td></tr><tr><td>Recommendation (E6)</td><td>The formation of desire</td><td>(desire) Responsibility</td><td>A vacant authorship — "who bears it" becomes "who wants it"</td></tr><tr><td>Amor fati (E7)</td><td>The affirmation of one's fate</td><td>Responsibility</td><td>The innermost — the subject who would affirm, vacated within me</td></tr></tbody></table></div><p><em>Table · The empty seat across seven stages. Sorting it from outside (a death on the battlefield) to inside (the author of my own desire) is not the order the season fixed but a trajectory I read out only later. Sources and as-of dates: see each piece's ledger (자율무기-위임 · llm-고찰 · ai에이전트-위임 · 온디바이스-ai · 주<span class="num">4일</span>제-실험 · 추천알고리즘-위임 · 니체-운명애).</em></p><p>From here on is a bridge I lay myself. The sort is not a ruler that drops straight in one line. The three cost-shaped stages—LLM, on-device, and the four-day week—run on a different grain from the responsibility stages, and forced onto one line, a cell like the LLM's empty correction channel breaks the order. Yet one direction holds even there: the one who bears it draws steadily closer to me. The inference cost lands on the chip I bought; the burnout settles into the individual worker's body. Stand the seven stages up that way and you see that the season's drift from killing to existence was not a procession of topics lined up in sequence. The empty seat kept moving inward. First it was the seat of a stranger dead on a battlefield, then a customer cheated on a deal, and at the end the seat inside me, where even what I want is set by something that is not me. The respondent that had been farthest away came closest, and finally returned to myself.</p><h2 id="sec-2">The Empty Seat Is Not Fate</h2><p>The easiest conclusion, then, is resignation. Delegation is by nature the act that erases the respondent, and that empty seat is a fate you pay as the price of delegating. Having seen the same empty seat seven times over, it is natural to want to read it that way. Yet two pieces outside the season, looking at the same lineage, pull me out of that resignation.</p><p>One is from history. Follow <a class="wikilink" href="https://refract.blog/en/posts/%EC%9C%84%EC%9E%84%EC%9D%98-%EC%84%A0%EB%A1%80/">mercenaries and the East India Company</a> and the scattering of the respondent turns out to be neither an AI invention nor a limitation of an age that lacked modern instruments of accountability. In <span class="num">1788</span> Edmund Burke impeached Warren Hastings over seven years, demanding that the Company's rule in India answer by name. There were courts; there was a procedure of indictment. And Hastings was acquitted in <span class="num">1795</span>. Even the attempt to stand a respondent up once scattered through the chain of delegation. So what made the seat empty was not the absence of an instrument. Even with the instrument in place, unless the seat to answer was nailed down at the moment of delegation, the seat stayed empty. The empty seat is a cell that design left blank, not a fate that technology imposes.</p><p>The other runs in the opposite direction. In <a class="wikilink" href="https://refract.blog/en/posts/%EC%95%8C%EA%B3%A0%EB%A6%AC%EC%A6%98-%ED%96%89%EC%A0%95-%EC%9C%84%EC%9E%84/">the administration that collapsed once it was automated</a>, Australia's robodebt mechanically matched welfare records against tax-office income to auto-issue roughly <span class="num">470,000</span> debt notices, then collapsed as unlawful. Responsibility was structured to slip easily from public servant to system. And yet a Royal Commission, after nearly a year of digging, concluded that the device was "crude and cruel," and submitted, in a sealed section, a recommendation to refer responsible individuals for criminal and civil action. The respondent concealed behind an outsourcing chain was, by the force of an inquiry, named again as individuals.</p><p>Set the two scenes side by side and one sentence stands up. The respondent does not evaporate on its own; it is a seat that <em>can be left empty</em>. Scatter it through a chain and it goes vacant; let a strong enough will come in and it is filled back. That one sentence makes me re-read the seven empty seats from before. Those seats that looked like fate were seats someone had left empty. Air Canada's responsibility falling, in the end, onto the company was itself the result of a will—the law tracking down a body to answer, all the way. The empty seat feels like a penalty that delegation imposes, but it is really a cell we did not fill in the design of the delegation.</p><h2 id="sec-3">The Innermost Respondent</h2><p>That said, the respondents history and administration point to are all on the outside. Someone to stand before a death, a company to bear an accident, an official to answer a citizen who was refused. Those seats can be filled by law, inquiry, and design, and that was the cold consolation the two pieces gave. But the season did not stop there; it pulled me one notch further in. When the spine's question twisted, before the recommender, into who wants, what went empty was not the outer respondent but the respondent inside me. Once the seat that wills what to want passes to the system, a blank remains that neither design nor inquiry can fill, because the only person who can fill that cell is me.</p><p>That, as I read it, is exactly where Nietzsche set the heavy phrase amor fati. The resolve to will one's whole life once more, the most regrettable day included, leaving nothing out—that is the act of seating a person back in the seat of being the author of one's own desire. The resolve not to leave the innermost respondent empty. And yet Nietzsche himself drew the most cunning trap of that seat alongside it. The last man he set opposite the Übermensch is the one who cleverly weeds out danger and hardship and far-off longing, keeps only the comfort within reach, and blinks while boasting "we have invented happiness." That diligence of weeding and choosing and optimizing is what fools a person into mistaking himself for a legislator. The more there is to choose, the easier it is to weed out of sight the residue one cannot choose—birth, era, body, the accidents beyond control—and so the most capable person is the one who most often misses what amor fati is actually testing.</p><p>This is the difficulty of the inner empty seat. The outer seat, when vacant, shows up as a notice or a verdict; the inner seat, when vacant, looks instead abundant and free. The ease with which first-order appetites are filled without friction, we mistake for proof that we have become the author. That <em>The Will to Power</em>—a book he never published—was edited after his death by his sister's hand and raised under a banner he despised his whole life is the extreme case showing that even the man who vowed to author his own life was powerless before the residue. In most of our lives the residue does not show itself that cruelly. It only seeps, small and steady, from places we never chose—the more accustomed we grow to the illusion of control, the more invisibly.</p><p>So there are two directions for filling the empty seat. On the outside, by design: nailing the seat to answer into the contract at the moment of delegation. On the inside, by resolve: choosing to remain, myself, in the seat that wills what to want. The directions differ, but neither is pushed by fate; both are chosen. Only this is fate—that leaving the seat empty is delegation's default. Filling it was, from first to last, a choice.</p><h2 id="sec-4">Coda</h2><p>So to the question the season posed—where do people remain—I find myself answering this way. On their own, nowhere. Delegation tilts toward erasing the respondent, and leaving the seat empty is always cheaper and faster. People remain only where someone, against that tilt, chose to nail the seat down. In a battlefield's contract, in an administration's design, and in the single beat where, before a feed you could not stop past midnight, you ask—belatedly—"is this really what I wanted?"</p><p>Closing the seven pieces, I turn the seven stages once more toward myself. The decisions I handed over, the desires I left to others—in each of them, did I keep the seat to answer filled, or leave it empty in the name of efficiency and call that freedom? Like that morning in Turin, the question "would you live it again" turns slowly, before I notice, away from the philosopher and toward me. I do not know the whole answer. But that those empty seats were not fate—of that much, now that I have written the sentence seven times, I am sure.</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li>This reckoning re-cites the primary sources that the seven pieces of the season "The Age of Delegation" and two standalone pieces on the same lineage verified at publication. Only the items the body rests on as fact or quotation are disclosed below (for each piece's full sources, see that piece).</li><li>Autonomous-weapons "accountability gap" — Human Rights Watch, "Mind the Gap" (2015): https://www.hrw.org/report/2015/04/09/mind-gap/lack-accountability-killer-robots · CCW consensus rule · ~120 states backing a treaty — Stop Killer Robots (2024–2025): https://www.stopkillerrobots.org/news/156-states-support-unga-resolution/ — via <a class="wikilink" href="https://refract.blog/en/posts/%EC%9E%90%EC%9C%A8%EB%AC%B4%EA%B8%B0-%EC%9C%84%EC%9E%84/">Who Pulled the Trigger — Autonomous Weapons and No One Left to Answer</a></li><li>LLM frozen weights · no continual learning — Richard Sutton interview, Dwarkesh Podcast (2025-09-26): https://www.dwarkesh.com/p/richard-sutton — via <a class="wikilink" href="https://refract.blog/en/posts/llm-%EA%B3%A0%EC%B0%B0/">A Machine That Has Never Seen a Board Knows the Board — Understanding, Mimicry, or the Wrong Question?</a></li><li>Re-fixing of chatbot responsibility onto the deployer — Moffatt v. Air Canada, 2024 BCCRT 149 (2024-02): https://www.canlii.org/en/bc/bccrt/doc/2024/2024bccrt149/2024bccrt149.html · "responsibility gap" concept — Andreas Matthias, <em>Ethics and Information Technology</em> 6(3) (2004): https://doi.org/10.1007/s10676-004-3422-1 — via <a class="wikilink" href="https://refract.blog/en/posts/ai%EC%97%90%EC%9D%B4%EC%A0%84%ED%8A%B8-%EC%9C%84%EC%9E%84/">AI Agents and the Accountability Gap: the Work Is Delegated, the Respondent Is Not</a></li><li>Inference cost shifting opex→capex — a16z, "LLMflation" (2024-11): https://a16z.com/llmflation-llm-inference-cost/ — via <a class="wikilink" href="https://refract.blog/en/posts/%EC%98%A8%EB%94%94%EB%B0%94%EC%9D%B4%EC%8A%A4-ai/">On-Device AI: Cost and Jurisdiction, Not Chips, Draw the Line</a></li><li>UK four-day-week pilot (revenue essentially flat · sick leave −65%) — Autonomy · 4 Day Week Global, "UK Four-Day Week Pilot Results" (2023-02): https://autonomy.work/portfolio/uk4dwpilotresults/ · Solow's productivity paradox (1987): https://www.brookings.edu/articles/the-solow-productivity-paradox-what-do-computers-do-to-productivity/ — via <a class="wikilink" href="https://refract.blog/en/posts/%EC%A3%BC4%EC%9D%BC%EC%A0%9C-%EC%8B%A4%ED%97%98/">Friday Disappeared. The Work Didn't.</a></li><li>Recommender objective (retention · time spent) — "TikTok Algo 101" (reported by NYT, 2021-12): https://www.nytimes.com/2021/12/05/business/media/tiktok-algorithm.html · second-order volition · wanton — Harry Frankfurt, <em>The Journal of Philosophy</em> 68(1) (1971): https://philpapers.org/rec/FRAFOT · recommenders' incentive to shift preferences — Carroll et al., ICML 2022: https://arxiv.org/abs/2204.11966 — via <a class="wikilink" href="https://refract.blog/en/posts/%EC%B6%94%EC%B2%9C%EC%95%8C%EA%B3%A0%EB%A6%AC%EC%A6%98-%EC%9C%84%EC%9E%84/">What I'll Want, and Who I Handed It To</a></li><li>amor fati (<em>The Gay Science</em> §276 · <em>Ecce Homo</em>) · eternal return (§341) · the last man (<em>Zarathustra</em>, prologue) · Turin collapse (1889) · <em>The Will to Power</em> posthumously compiled (1901) — Nietzsche, primary texts, via the Stanford Encyclopedia of Philosophy · Wikipedia (2026-06): https://plato.stanford.edu/entries/nietzsche/ · https://en.wikipedia.org/wiki/Amor_fati — via <a class="wikilink" href="https://refract.blog/en/posts/%EB%8B%88%EC%B2%B4-%EC%9A%B4%EB%AA%85%EC%95%A0/">Would You Live It Again — Nietzsche and the Fate You Cannot Choose</a></li><li>Impeachment of Warren Hastings (1788–95, acquitted 1795) — Wikipedia, <em>Impeachment of Warren Hastings</em>: https://en.wikipedia.org/wiki/Impeachment_of_Warren_Hastings — via <a class="wikilink" href="https://refract.blog/en/posts/%EC%9C%84%EC%9E%84%EC%9D%98-%EC%84%A0%EB%A1%80/">Delegation Only Moves the Burden — The Responder the Mercenaries and the East India Companies Erased First</a></li><li>Australia's Robodebt Royal Commission final report ("crude and cruel"; referral of individuals for criminal and civil action, 2023-07) — Law Society Journal: https://lsj.com.au/articles/crude-cruel-and-unlawful-robodebt-royal-commission-findings/ · ~470,000 debt notices (ruled unlawful, 2019) — Services Australia: https://www.servicesaustralia.gov.au/robodebt-class-action — via <a class="wikilink" href="https://refract.blog/en/posts/%EC%95%8C%EA%B3%A0%EB%A6%AC%EC%A6%98-%ED%96%89%EC%A0%95-%EC%9C%84%EC%9E%84/">Who Does a Rejected Citizen Appeal To — The Empty Seat in Algorithmic Administration</a></li><li>---</li><li><em>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</em></li><li>&lt;/content&gt;</li></ol></section></article>]]></content:encoded></item>
<item><title>The Tariff Was the Trigger, Not the Engine — The Bill 1930 Sends to 2026</title><link>https://refract.blog/en/posts/%EA%B4%80%EC%84%B8%EC%A0%84%EC%9F%81-%EA%B5%90%ED%9B%88/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EA%B4%80%EC%84%B8%EC%A0%84%EC%9F%81-%EA%B5%90%ED%9B%88/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>History</category><description>In 2025 the average effective U.S. tariff rate touched 18.2%. The highest since 1934—close enough to graze the roughly 20% the Smoot-Hawley Tariff Act drove it…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#b5683f"></span><span class="kx">History</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-27T15:39:31"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><h1 class="title">The Tariff Was the Trigger, Not the Engine — The Bill 1930 Sends to 2026</h1><div class="body"><p class="lead">In 2025 the average effective U.S. tariff rate touched 18.2%. The highest since 1934—close enough to graze the roughly 20% the Smoot-Hawley Tariff Act drove it to in 1930. By 2026 it had eased to 11.0%, still the highest since 1943. In May 1930, 1,028 economists petitioned President Hoover to veto the act, warning that a tariff war brings retaliation, rising prices, and the erosion of international peace. Ninety-six years later, the same warning sounds again. Which is why everyone reaches for "Smoot-Hawley 2.0."</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">The Real Engine the Record Names</a><a class="jump" href="#sec-2">The Level Rhymes, but the Amplifier Has Moved</a><a class="jump" href="#sec-3">The Channel That Survived — Bloc Realignment</a><a class="jump" href="#sec-4">Is Korea Canada?</a><a class="jump" href="#sec-5">The Bill</a></nav><p>But the analogy misnames what broke trade.</p><h2 id="sec-1">The Real Engine the Record Names</h2><p>The standard Smoot-Hawley story runs like this. America raised tariffs, the world retaliated, trade collapsed. The collapse is real. World trade evaporated by roughly <span class="num">66%</span>—two-thirds—between <span class="num">1929</span> and <span class="num">1934</span>, and U.S. imports from Europe fell <span class="num">70%</span>, exports <span class="num">65%</span>. The retaliation is real too. Within two years of the act taking effect, more than <span class="num">24</span> countries struck back with steep tariffs, beginning with Canada—then America's largest trading partner—which levied retaliatory duties on <span class="num">16</span> product lines.</p><p>The question is whether that retaliation <em>caused</em> the <span class="num">66%</span> collapse. When later economic historians—Eichengreen and Irwin, Mitchener and others—re-examined the trade policy of the period, the retaliation looked less like a coordinated chain aimed squarely at the United States than like a uniform bolting of the doors against every trading partner alike. Two larger forces actually pulled trade volume down. One was the Depression itself—incomes and prices collapsing together, demand evaporating. The other was the gold standard. Countries that clung to gold throttled trade with import quotas and exchange controls to stem the outflow of bullion; countries that left gold and devalued did not. The fragmentation into trade blocs was already in motion before Smoot-Hawley.</p><p>The tariff was the trigger. The amplifier that brought down two-thirds of world trade was not a chain of retaliation but the Depression, the gold standard, and the carving of the world into blocs. That distinction is the key to reading today.</p><h2 id="sec-2">The Level Rhymes, but the Amplifier Has Moved</h2><div class="tablewrap"><table><thead><tr><th>Point in time</th><th>U.S. average effective tariff rate</th><th>Notes</th></tr></thead><tbody><tr><td><span class="num">1930</span> (Smoot-Hawley)</td><td>~<span class="num">20%</span></td><td>Baseline · farm tariffs raised ~<span class="num">57%</span></td></tr><tr><td><span class="num">2024</span></td><td>~<span class="num">2.4%</span></td><td>Just before the tariff war</td></tr><tr><td><span class="num">2025</span> (peak)</td><td>~<span class="num">18.2%</span></td><td>Highest since <span class="num">1934</span></td></tr><tr><td><span class="num">2026</span> (April)</td><td>~<span class="num">11.0%</span></td><td>Highest since <span class="num">1943</span> (excl. <span class="num">2025</span>)</td></tr></tbody></table></div><blockquote><p>Table · U.S. average effective tariff rate. Primary sources: <span class="num">1930</span> — Britannica (Smoot-Hawley, as-of <span class="num">1930</span>) / <span class="num">2024</span> — Tax Foundation (as-of <span class="num">2024</span>) / <span class="num">2025–26</span> — Yale Budget Lab (as-of <span class="num">2025-07</span>-28 and <span class="num">2026-04</span>-02, respectively).</p></blockquote><p>On the numbers alone, it reads as déjà vu. From <span class="num">2.4%</span> in <span class="num">2024</span> to <span class="num">18.2%</span> in a single year—nearly to the Smoot-Hawley level. But where <span class="num">1930</span>'s ~<span class="num">20%</span> was a regime that held for years, <span class="num">18.2%</span> was a momentary peak that soon settled back to <span class="num">11%</span>. A resemblance in level is a resemblance of one scene, not of a system.</p><p>One amplifier peculiar to the 1930s is plainly switched off. Exchange rates float, and no country throttles trade to stem an outflow of gold. The quota-and-exchange-control channel the gold standard once forced is closed from the start.</p><p>That does not mean the shock-amplifying machinery is gone. It has moved. In April <span class="num">2025</span> the United States and China drove tariffs to <span class="num">145%</span> against <span class="num">125%</span>. This is the textbook tit-for-tat spiral. The spiral stopped not because the structure made it impossible, but because the May Geneva truce rolled reciprocal tariffs back to <span class="num">10%</span> and the October Busan meeting extended that truce to November <span class="num">2026</span>. Where the 1930s gold standard stood, today sit dense global supply chains, the chokepoints of semiconductors and critical minerals, and export controls. The amplifier did not vanish; it changed shape—which is why the structure will not stop itself the way it did in the 1930s. What stops it is negotiation.</p><h2 id="sec-3">The Channel That Survived — Bloc Realignment</h2><p>The real event in the <span class="num">1930</span> Canada story is not the retaliation itself but what came next. Canada bolted the door to America while lowering tariffs on British Empire goods, and at the <span class="num">1932</span> Ottawa Imperial Economic Conference it shifted the whole center of gravity of its trade to the Commonwealth. Which camp a country belonged to was redrawn.</p><p>Today, U.S.–China bloc formation has taken that place. The world splits into camps again, and each country settles which side to stand on by paying for it. Today's shock travels along the realignment of camps more than along a chain of retaliation.</p><h2 id="sec-4">Is Korea Canada?</h2><p>In October <span class="num">2025</span>, Korea's exports to the United States fell <span class="num">16.2%</span> to <span class="num">$8.71</span> billion, the lowest in <span class="num">33</span> months. The goods in the tariff's direct line all dropped together.</p><blockquote><p><strong>Korea's exports to the U.S., October <span class="num">2025</span></strong> (year-on-year) Automobiles −<span class="num">10.5%</span> · Auto parts −<span class="num">18.9%</span> · Steel −<span class="num">21.5%</span> · General machinery −<span class="num">16.1%</span> Source: Korea Customs Service · Ministry of Trade, Industry and Energy, <span class="num">2025-10</span>.</p></blockquote><p>At the same time, total <span class="num">2025</span> exports hit a record <span class="num">$707.9</span> billion, of which semiconductors made up <span class="num">24.4%</span>. Tied to the United States and tilted toward semiconductors—a double concentration.</p><p>So Korea's chosen answer is the deal of <span class="num">29</span> October <span class="num">2025</span>.</p><blockquote><p><strong>Korea–U.S. tariff agreement</strong> (<span class="num">2025-10</span>-29) Reciprocal tariff <span class="num">15%</span> · Autos <span class="num">25%</span> → <span class="num">15%</span> Investment in the U.S. <span class="num">$350</span> billion = <span class="num">$200</span> billion cash (annual cap <span class="num">$20</span> billion) + <span class="num">$150</span> billion shipbuilding cooperation Source: Ministry of Trade, Industry and Energy / Korea International Trade Association, <span class="num">2025-10</span>-29.</p></blockquote><p>It is a structure that buys access with money. As countries at Ottawa in <span class="num">1932</span> locked in their place inside the empire by treaty, Korea has locked in its place inside the U.S. camp by investment.</p><p>But Ottawa is not the same event; it is a mirror of contrast. Canada, shoved by American tariffs, switched to another bloc—Britain. Korea has no bloc to switch to. Its largest trading partner, China, is at once a competitor and a security threat, and the U.S.–Korea alliance narrows the options. Canada was the one pushed away; Korea is the one with no choice but to stay, paying the price of staying up front. The two events do not resemble each other—they point in opposite directions.</p><p>There are points where the analogy does not fit cleanly. For autos or steel, which camp's tariff schedule they land on is relatively clear. Semiconductors are different. Korea's chips straddle both sides—the U.S. camp in equipment and subsidies, the Chinese market in sales—and do not resolve to a single camp. And what actually divides semiconductors is not the tariff schedule but <a class="wikilink" href="https://refract.blog/en/posts/%EB%B0%98%EB%8F%84%EC%B2%B4-%ED%9B%84%EA%B3%B5%EC%A0%95/">export controls and the entity list</a>. That Korea's largest exposure happens to be the very good that resists camp assignment most—this is where the bill grows most complicated.</p><p>The monetary dimension reaches Korea too. The 1930s-style amplifier of the gold standard is switched off, but the capital-outflow pressure of the <span class="num">$200</span> billion in cash riding on the U.S. investment, and how the won's exchange rate divides that burden, is a newly switched-on channel. A floating rate is both a cushion and a new transmission line.</p><h2 id="sec-5">The Bill</h2><p>Summarize the lesson of <span class="num">1930</span> as "raise tariffs, retaliation comes, trade dies," and you are half right. The retaliation did come. But what brought down two-thirds of trade was not that retaliation; it was the Depression, the gold standard, and the realignment that split the world into camps. The tariff rate is brief; the lasting damage is engraved on the map of camps.</p><p>So the dashboard Korea should watch sits beyond the retaliation scoreboard. How long the <span class="num">15%</span> on autos holds; which side of export controls, not tariffs, semiconductors fall on; how the <span class="num">$350</span> billion investment ceiling and the won's exchange rate split the burden. The estimate that U.S. tariffs cut household income by <span class="num">$570</span> to <span class="num">$940</span> in <span class="num">2025</span> dollars is a story inside America.</p><p>The bill Korea will receive is not a single line of tariff rate but a longer ledger—written together with the investment ceiling, the exchange-rate share, and a position inside a camp. What that ledger really asks you to weigh is the trade-off, not the absolute sum. The deeper Korea is bound into the U.S. camp, the more stable its access—but the narrower its semiconductor sales to China and its room to hedge. In the end the question is less 'how much do you pay' than 'which side do you stand on, and what do you give up for it.'</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li>Smoot–Hawley Tariff Act · average tariff rate (~20%) · farm goods 57% — Britannica, <em>Smoot–Hawley Tariff Act</em> (as-of 1930). https://www.britannica.com/topic/Smoot-Hawley-Tariff-Act</li><li>1929–34 world trade −66% · collapse of trade with Europe · 24+ countries respond — U.S. State Dept. Office of the Historian, <em>Protectionism in the Interwar Period</em>. https://history.state.gov/milestones/1921-1936/protectionism</li><li>1,028 economists' veto petition of 1930 — AEI, <em>The economists' tariff protest of 1930</em> (reprint). https://www.aei.org/carpe-diem/the-economists-tariff-protest-of-1930/</li><li>Non-coordination of retaliation · gold-standard amplification channel — Mitchener·O'Rourke·Wandschneider, "The Smoot-Hawley Trade War," <em>Economic Journal</em> 132(647), 2022 / Eichengreen·Irwin, NBER w25830. https://academic.oup.com/ej/article/132/647/2500/6519264 · https://www.nber.org/system/files/working_papers/w25830/w25830.pdf</li><li>Canada's retaliation · Ottawa Imperial Economic Conference realignment — <em>Journal of Economic History</em> 57(4), 1997 / Maclean's. https://ideas.repec.org/a/cup/jechis/v57y1997i04p802-826_01.html · https://www.macleans.ca/opinion/what-we-can-learn-from-a-disastrous-1930-u-s-tariff-on-canadian-goods/</li><li>2024 effective tariff rate (2.4%) — Tax Foundation (as-of 2024). https://taxfoundation.org/research/all/federal/trump-tariffs-trade-war/</li><li>2025 peak (18.2%) · 2026 (11.0%) · household income effect — Yale Budget Lab (as-of 2025-07-28 / 2026-04-02 / 2026-03-09). https://budgetlab.yale.edu/research/state-us-tariffs-july-28-2025 · https://budgetlab.yale.edu/research/state-us-tariffs-april-2-2026 · https://budgetlab.yale.edu/research/state-us-tariffs-march-9-2026</li><li>U.S.–China tariffs 145/125 · Geneva and Busan truces — China Briefing / Wikipedia, <em>China–United States trade war</em>. https://www.china-briefing.com/news/us-china-tariff-rates-2025/</li><li>Korea–U.S. tariff agreement (2025-10-29) — Republic of Korea Policy Briefing (korea.kr) / Global Economic. https://www.korea.kr/news/policyNewsView.do?newsId=148953418</li><li>Korea Oct 2025 exports to U.S. −16.2% · by product — NewDaily. https://biz.newdaily.co.kr/site/data/html/2025/11/02/2025110200037.html</li><li>2025 total exports $707.9 billion · semiconductors 24.4% — Korea International Trade Association (KITA). https://www.kita.net/</li></ol></section><footer class="byline"><span class="ai-dot"></span><span>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</span></footer></article>]]></content:encoded></item>
<item><title>Delegation Only Moves the Burden — The Responder the Mercenaries and the East India Companies Erased First</title><link>https://refract.blog/en/posts/%EC%9C%84%EC%9E%84%EC%9D%98-%EC%84%A0%EB%A1%80/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EC%9C%84%EC%9E%84%EC%9D%98-%EC%84%A0%EB%A1%80/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>History</category><description>You hand a decision to an AI, it goes wrong — who answers? Lately the question has been circling boardrooms and regulators. Scholars call it the responsibility…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#b5683f"></span><span class="kx">History</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-28T00:26:48"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><div class="vcaveat"><span class="vc-l">Note</span><span>잔여 비차단 nit 2건(미러 도입 "이제 오늘로 돌아옵니다"·"한 가지 반론이 가능합니다" 신호 완화) — 비차단.</span></div><h1 class="title">Delegation Only Moves the Burden — The Responder the Mercenaries and the East India Companies Erased First</h1><div class="body"><p class="lead">You hand a decision to an AI, it goes wrong — who answers? Lately the question has been circling boardrooms and regulators. Scholars call it the <em>responsibility gap</em>: the name Andreas Matthias gave, in 2004, to the gap where responsibility for the acts of a learning machine cannot be assigned. It sounds like a new problem. But the same question was asked far earlier — on the sacked streets of Rome in 1527, in a starving Bengal in 1770. Asked, and never answered in time by anyone held to it.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">When War Was Rented</a><a class="jump" href="#sec-2">The Company That Was Lent Sovereignty</a><a class="jump" href="#sec-3">The Answer Came Back Only From Outside</a><a class="jump" href="#sec-4">A Mirror — but Not the Same Picture</a><a class="jump" href="#sec-5">The Bill</a></nav><p>Delegation does not erase a burden. It moves it. And the act of moving scatters the person who should stand, by name, when things go wrong. The harder part is time. The answer does not vanish; it is pushed far down the road, and it returns only when an outside shock arrives. Only closed cases show the full length of that delay. That is why, to read today, we look to the seventeenth century. With one caveat — history is a mirror, not a copy, and that difference is settled later.</p><h2 id="sec-1">When War Was Rented</h2><p>Before the modern state had a standing army, war was something you rented. In the fourteenth and fifteenth centuries the city-states of Italy hired mercenary captains, the <em>condottieri</em>, under a contract called a <em>condotta</em>. The White Company entered Italy in <span class="num">1361</span>, and the Englishman John Hawkwood soon led it across decades of the peninsula. These companies moved to whichever side bid better. To a critic like Machiavelli, peace was the end of a mercenary's business, so the incentive ran to dragging a war out rather than ending it. Modern military historians have largely overturned that received wisdom — but the structure survives it: a rented blade keeps a different ledger from the one who rents it.</p><p>When Machiavelli, in Chapter XII of <em>The Prince</em>, called mercenaries "useless and dangerous," this is why. His verdict is sharper still: mercenaries are "disunited, ambitious, and without discipline, unfaithful." We usually read this <span class="num">1513</span> line as military advice — they are weak, so you cannot trust them. But the point is not weakness; it is attachment. A rented army owes no whole loyalty to anyone, so the person who would answer, by name, for what it does grows faint.</p><p>That fading was at its starkest in Rome in <span class="num">1527</span>. An imperial mercenary army more than six months in arrears — roughly <span class="num">14,000</span> Landsknechts plus some <span class="num">6,000</span> Spanish troops — mutinied and ran wild, and sacked Rome. The Duke of Bourbon, who led them, was killed in the assault; Emperor Charles V, their nominal sovereign, did not order the sack and held himself at a distance. The sack did become a Europe-wide scandal, and Charles V's reputation suffered. Responsibility did not evaporate. It simply fixed to no one. The emperor had given no order, the commander was dead, and the soldiers stood behind "we were not paid."</p><p>The Thirty Years' War (<span class="num">1618–1648</span>) raised this structure to the scale of an age. Its armies were largely mercenary, and they fed themselves on "contributions" levied on occupied land and on plunder. The principle that named the system was <em>bellum se ipsum alet</em> — the war will feed itself. The bill went to civilians. At Magdeburg in <span class="num">1631</span>, an estimated <span class="num">20,000</span> of roughly <span class="num">25,000</span> inhabitants were killed. A rented army often outran the control of the very master who rented it: Magdeburg did have commanders, Tilly and Pappenheim, yet by the standard account they could not fully control the sack — and that loss of control is exactly the danger delegation creates. By the war's end the Holy Roman Empire's population loss — the estimates are contested — ran to <span class="num">15–20%</span> across the empire, and to over half in the worst-hit regions. The direct causes of these deaths were not only plunder but famine, disease, and scorched earth — true of wars fought by standing armies too. What delegation changed was not the cause of death but the attachment of the answer: who stands, by name, for what the rented army did.</p><h2 id="sec-2">The Company That Was Lent Sovereignty</h2><p>If a mercenary was rented war, the East India Company was sovereignty itself, lent out. And it shows that delegation does not happen once — it accumulates.</p><p>The English East India Company (EIC) began with a charter from Elizabeth I on <span class="num">31</span> December <span class="num">1600</span>. What it first received was a trade monopoly, and nothing more. But the grant did not stop growing. Starting with Charles II's charter of <span class="num">1661</span>, successive charters allowed the company, one item at a time, to make war and peace, to coin money, to keep an army, to build fortresses, to hold civil and criminal jurisdiction, and to acquire territory. A trading company took over the core functions of a state, line by line. It had its own army, and not a small one: by the early nineteenth century the EIC's private army reached, by the National Army Museum's estimate, about <span class="num">250,000</span> — roughly twice the British regular army.</p><p>The terminus of this delegation was taxation. At the Battle of Plassey in <span class="num">1757</span>, a company force of about <span class="num">3,000</span> under Clive broke a Nawab's army of some <span class="num">50,000</span> on the back of Mir Jafar's betrayal, and in <span class="num">1765</span> the Mughal emperor Shah Alam II, by the Treaty of Allahabad, handed the company the <em>diwani</em> — the right to collect revenue — of Bengal, Bihar, and Orissa. A joint-stock company had become the sovereign that taxes a region.</p><p>The bill arrived soon after: the Great Bengal famine of <span class="num">1769–70</span>. The death toll is contested. The common figure is up to about <span class="num">10</span> million, roughly a third of Bengal's population; scholars put the range between <span class="num">7</span> and <span class="num">10</span> million, and revisionists lower. Drought was the trigger; the company did not starve people. But there is little dispute that the company did not slow its tax collection through the famine.</p><p>The Dutch East India Company (VOC) was the same structure, earlier and more plainly. The charter the States General granted in <span class="num">1602</span> gave it, all at once, the rights to wage war, build fortresses, conclude treaties with Asian rulers, keep armies, and coin its own money. How those powers were used shows in the Banda Islands in <span class="num">1621</span>. Jan Pieterszoon Coen conquered Banda to monopolize nutmeg, and a population of about <span class="num">15,000</span> before the conquest was reduced — by killing, starvation, deportation, and enslavement — to an estimated thousand to two thousand survivors.</p><p>Not every delegation, of course, ended in massacre. Most <em>condotte</em> were fulfilled without a sack; the companies ran ports and courts and account books well enough; the VOC turned a profit for more than <span class="num">150</span> years. The point is not that delegation always brings catastrophe, but that when the catastrophe's bill arrives, the person who should stand for it scatters within that very delegated structure. Is the company a merchant, or a sovereign? Both. And because of that, no answer comes back from either side. Press it on the massacre, and it was only a company making a commercial judgment; press it on the commerce, and it was only performing a chartered sovereign function. In William Dalrymple's phrasing, the EIC is the first corporate-state and the archetype of unaccountable corporate power. The identity of that unaccountability is exactly this double nature.</p><h2 id="sec-3">The Answer Came Back Only From Outside</h2><p>The two delegations share one structure in time. Delegation took effect at once, but the answer came back only much later — and only with an outside shock.</p><p>Parliament had not simply let go. It imposed its first oversight with the Regulating Act of <span class="num">1773</span>; with Pitt's India Act of <span class="num">1784</span> it set up a Board of Control and pulled political authority toward the Crown; and from <span class="num">1788</span>, across seven years, it impeached Warren Hastings on charges of misrule in India. It was Edmund Burke demanding that the company's rule answer, by name. Yet Hastings was acquitted in <span class="num">1795</span>. Even the one attempt to stand a responder up scattered through the chain and failed. The company's sovereignty was actually recovered by the state only some sixty years later, after the shock of the Indian Rebellion of <span class="num">1857</span>. The next year the Government of India Act (<span class="num">1858</span>) moved rule from the company to the British Crown, and the company itself was dissolved in <span class="num">1874</span>. The VOC had gone earlier, dissolved into nationalization in <span class="num">1799</span> as its charter expired amid debt and corruption. One ended by rebellion, the other by bankruptcy. The responder's seat does not fill itself from within; it was re-set only by an outside shock. The account was settled in the end — a century, two centuries, late.</p><div class="tablewrap"><table><thead><tr><th>What was delegated</th><th>To whom</th><th>Who bore the bill</th><th>The responder</th><th>What brought the answer back</th></tr></thead><tbody><tr><td>Waging war (mercenaries, 14th–17th c.)</td><td>private armies</td><td>plunder, war-famine (civilians)</td><td>fixed to no seat</td><td>—</td></tr><tr><td>Sovereignty, taxation (EIC, <span class="num">1600–1874</span>)</td><td>joint-stock company</td><td>Bengal famine (peasants)</td><td>behind the merchant/sovereign double; Hastings impeachment failed (<span class="num">1795</span>)</td><td><span class="num">1857</span> rebellion → <span class="num">1858</span> direct Crown rule</td></tr><tr><td>Sovereignty, force (VOC, <span class="num">1602–1799</span>)</td><td>joint-stock company</td><td>Banda massacre (islanders)</td><td>the same double</td><td>debt, corruption → <span class="num">1799</span> nationalization</td></tr></tbody></table></div><blockquote><p>Table · The accumulation and recovery of delegation. Primary sources: Sack of Rome <span class="num">1527</span> · Magdeburg <span class="num">1631</span> / EIC charter, Hastings impeachment, dissolution (<span class="num">1600</span> · <span class="num">1795</span> · <span class="num">1858</span> · <span class="num">1874</span>) / VOC charter, Banda, dissolution (<span class="num">1602</span> · <span class="num">1621</span> · <span class="num">1799</span>). Death and population figures are estimates and ranges; sources are named in the text.</p></blockquote><h2 id="sec-4">A Mirror — but Not the Same Picture</h2><p>Now back to today. Hold history up as a mirror — but the moment you say the picture in it is the <em>same</em>, the analysis is wrong.</p><p>What we now call the "AI responsibility gap" is that empty seat. When an autonomous weapon picks a target, when an AI agent executes a trade, when a recommendation algorithm designs someone's day — and it goes wrong, who answers? It is the very gap Matthias named in <span class="num">2004</span>. The structure rhymes. A delegation interface slots in between the decision and its result, and behind it the responder scatters among principal, agent, and individual. <a class="wikilink" href="https://refract.blog/en/posts/%EC%9E%90%EC%9C%A8%EB%AC%B4%EA%B8%B0-%EC%9C%84%EC%9E%84/">The delegation of the final kill decision to a machine</a> is its sharpest present tense, and <a class="wikilink" href="https://refract.blog/en/posts/%EA%B4%80%EC%84%B8%EC%A0%84%EC%9F%81-%EA%B5%90%ED%9B%88/">the structure in which merchant and sovereign blurred</a> replays the East India echo on a different stage.</p><p>One objection has to be met here. Maybe no one answered back then not because of delegation but because the modern apparatus of accountability — international law, liability, regulation — did not exist. Half true. But the Hastings impeachment shows that courts and inquiry were working even then, and that even that apparatus spun uselessly against the chain of delegation. The point is not the absence of the apparatus. The delegated structure itself disperses the answer. We have courts, liability law, regulators today. And still the gap reopens at exactly that delegation interface.</p><p>But the difference must not be erased. Mercenaries and the East India companies were human actors, and legal persons holding explicit charters. Charles V could have refused the order; a board could have approved a massacre or stopped it; and in the end it was dragged back out in <span class="num">1858</span>. History's responder was scattered rather than erased. With an algorithm, that scattering comes closer to erasure. The law's inquiry drops its anchor into intent and into an acting subject — and a system that is neither a moral subject nor a legal person gives it nowhere to anchor. Scale and speed differ too: the diwani's collection turned on a yearly cycle, while an algorithm's decisions pile up in the hundreds of millions, by the millisecond. To paste Machiavelli's warning onto an autonomous weapon one-to-one is not analysis but the overreach of a metaphor.</p><p>So the claim is continuity, not identity. The property by which delegation, as a form of governance, disperses the responder carries across <span class="num">400</span> years. What changed is that the party receiving the delegation moved from a human company to a non-actor system. And yet the one the law would name as responder is not the algorithm but the people and firms that deploy and operate it. In the old company's seat sits today's "deployer." The trouble is that the deployer, too, scatters again — among model provider, data supplier, operating firm, and end user. The chain of delegation has only grown one link longer.</p><h2 id="sec-5">The Bill</h2><p>This is not a call to stop delegating. Just as no state could fight every war and collect every tax itself, delegation is a constant of governance. The question is not the ban on delegation but its design.</p><p>The question is one. Did you nail down the responder's seat <em>at the same time</em> as the delegation? The answer the East India Company's two centuries give is cold. If you do not fix that seat in advance, it stays empty until the bill comes back on an outside shock. The peasants of Bengal, the islanders of Banda, the citizens of Magdeburg were all other names for that empty seat.</p><p>What we really have to decide, in handing decisions to an AI today, is not the model's accuracy. It is where the person who can stand, by name, when things go wrong still remains — and whether we wrote that seat into the contract of delegation itself. If we do not, we will meet again an empty seat far older than Matthias's <span class="num">2004</span> — the empty seat of <span class="num">1527</span> and of <span class="num">1770</span>.</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li>Machiavelli, <em>The Prince</em> ch. XII — "useless and dangerous" / characterization of mercenaries (direct quotations) — Niccolò Machiavelli, <em>The Prince</em>, ch. XII (Marriott translation). https://www.constitution.org/mac/prince12.htm</li><li><em>The Prince</em> written (1513), published (1532) — Stanford Encyclopedia of Philosophy, <em>Niccolò Machiavelli</em>. https://plato.stanford.edu/entries/machiavelli/</li><li>Condottieri · the condotta contract · incentive to prolong war — Encyclopaedia Britannica, <em>condottiere</em>. https://www.britannica.com/topic/condottiere</li><li>John Hawkwood · White Company (entered Italy 1361) — Wikipedia, <em>John Hawkwood</em>. https://en.wikipedia.org/wiki/John_Hawkwood</li><li>"The war feeds itself" (bellum se ipsum alet) — Wikipedia, <em>Bellum se ipsum alet</em>. https://en.wikipedia.org/wiki/Bellum_se_ipsum_alet</li><li>Sack of Magdeburg (1631) · casualty estimate — Wikipedia, <em>Sack of Magdeburg</em>. https://en.wikipedia.org/wiki/Sack_of_Magdeburg</li><li>Thirty Years' War population loss (contested range) — Wikipedia, <em>Thirty Years' War</em>. https://en.wikipedia.org/wiki/Thirty_Years%27_War</li><li>Sack of Rome (1527) · unpaid mutiny · Charles V — Wikipedia, <em>Sack of Rome (1527)</em>. https://en.wikipedia.org/wiki/Sack_of_Rome_(1527)</li><li>EIC charter (1600) · trade monopoly — Encyclopaedia Britannica, <em>East India Company</em>. https://www.britannica.com/topic/East-India-Company</li><li>EIC sovereign powers (cumulative from 1661) · dissolution (1874) — Wikipedia, <em>East India Company</em> / <em>East India Stock Dividend Redemption Act 1873</em>. https://en.wikipedia.org/wiki/East_India_Company · https://en.wikipedia.org/wiki/East_India_Stock_Dividend_Redemption_Act_1873</li><li>EIC private army (~250,000, ~twice the British Army) — National Army Museum, <em>The armies of the East India Company</em> / World History Encyclopedia. https://www.nam.ac.uk/explore/armies-east-india-company · https://www.worldhistory.org/article/2080/the-armies-of-the-east-india-company/</li><li>Battle of Plassey (1757) — Encyclopaedia Britannica, <em>Battle of Plassey</em>. https://www.britannica.com/event/Battle-of-Plassey</li><li>Diwani · Treaty of Allahabad (1765) — Wikipedia, <em>Treaty of Allahabad</em>. https://en.wikipedia.org/wiki/Treaty_of_Allahabad</li><li>Great Bengal famine (1769–70) · death estimates · company taxation — Wikipedia, <em>Great Bengal famine of 1770</em>. https://en.wikipedia.org/wiki/Great_Bengal_famine_of_1770</li><li>VOC charter (1602) · powers · dissolution (1799) — Wikipedia, <em>Dutch East India Company</em>. https://en.wikipedia.org/wiki/Dutch_East_India_Company</li><li>Conquest and massacre of the Banda Islands (1621) — Wikipedia, <em>Dutch conquest of the Banda Islands</em>. https://en.wikipedia.org/wiki/Dutch_conquest_of_the_Banda_Islands</li><li>Regulating Act (1773) — Wikipedia, <em>Regulating Act 1773</em>. https://en.wikipedia.org/wiki/Regulating_Act_1773</li><li>Pitt's India Act (1784) — Wikipedia, <em>Pitt's India Act</em>. https://en.wikipedia.org/wiki/Pitt%27s_India_Act</li><li>Impeachment of Warren Hastings (1788–95, led by Burke, acquitted 1795) — Wikipedia, <em>Impeachment of Warren Hastings</em>. https://en.wikipedia.org/wiki/Impeachment_of_Warren_Hastings</li><li>Government of India Act (1858) — Wikipedia, <em>Government of India Act 1858</em>. https://en.wikipedia.org/wiki/Government_of_India_Act_1858</li><li>The "responsibility gap" concept — Andreas Matthias, "The responsibility gap: Ascribing responsibility for the actions of learning automata," <em>Ethics and Information Technology</em> 6(3), 2004. https://link.springer.com/article/10.1007/s10676-004-3422-1</li><li>EIC as the first "corporate-state" / archetype of unaccountable corporate power (modern framing) — William Dalrymple, <em>The Anarchy</em> (2019), via <em>TIME</em>. https://time.com/5716016/william-dalrymple-british-east-india-company/</li></ol></section><footer class="byline"><span class="ai-dot"></span><span>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</span></footer></article>]]></content:encoded></item>
<item><title>Fertility Climbed to 0.80, Seoul Sank to 0.58</title><link>https://refract.blog/en/posts/%EC%B6%9C%EC%82%B0%EC%9C%A8-%EB%8F%84%EC%8B%9C/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EC%B6%9C%EC%82%B0%EC%9C%A8-%EB%8F%84%EC%8B%9C/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Society</category><description>South Korea's total fertility rate rose to 0.80 in 2025. It hit bottom at 0.72 in 2023, rebounded for the first time in nine years to 0.75 in 2024, and has now…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#cf5563"></span><span class="kx">Society</span><span class="ksep">·</span><span class="kx">인구</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-27T15:38:44"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><h1 class="title">Fertility Climbed to 0.80, Seoul Sank to 0.58</h1><div class="body"><p class="lead">South Korea's total fertility rate rose to 0.80 in 2025. It hit bottom at 0.72 in 2023, rebounded for the first time in nine years to 0.75 in 2024, and has now climbed another step. Births rose too—to 254,500, up 16,100, or 6.8%. Read the headline alone, and the mood looks like it has turned.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">What Built the 0.80</a><a class="jump" href="#sec-2">The Same Youth, Two Numbers</a><a class="jump" href="#sec-3">The Same Data, Four Reckonings</a><a class="jump" href="#sec-4">So How Should We Read 0.80?</a></nav><p>Yet inside the same country sits the opposite number. The Seoul Capital Area leads the nation in net youth inflow, and at its center, Seoul's total fertility rate for <span class="num">2024</span> was <span class="num">0.58</span>—dead last nationwide. The two figures are keyed to different years—the national <span class="num">0.80</span> is <span class="num">2025</span>, Seoul's <span class="num">0.58</span> is a <span class="num">2024</span> provisional figure. Seoul's rate likely ticked up slightly in <span class="num">2025</span> too, but the standing does not change: where the most people gather, the fewest children are born.</p><h2 id="sec-1">What Built the 0.80</h2><p>Start with what the rebound actually is. First births rose <span class="num">8.6%</span> in <span class="num">2025</span>, to <span class="num">158,700</span>, and the share of couples having a child within two years of marriage climbed to <span class="num">36.1%</span>. The pattern reads as marriages deferred during COVID releasing at once, pulling early births forward.</p><blockquote><p><strong>The Lift vs. the Ceiling (<span class="num">2025</span>)</strong></p><div class="tablewrap"><table><thead><tr><th></th><th>Figure</th></tr></thead><tbody><tr><td>Lift — first births</td><td><strong>+<span class="num">8.6%</span></strong> (<span class="num">158,700</span>)</td></tr><tr><td>Lift — births within <span class="num">2</span> years of marriage</td><td><strong><span class="num">36.1%</span></strong></td></tr><tr><td>Ceiling — mothers aged <span class="num">35</span>+</td><td><strong><span class="num">37.3%</span></strong> (record high)</td></tr><tr><td>Ceiling — natural population decline</td><td><strong>−<span class="num">110,000</span></strong></td></tr></tbody></table></div><p><em>Source: National Data Agency, Birth and Death Statistics (provisional), <span class="num">2025</span></em></p></blockquote><p>The trouble is that ceiling. The same year, the mean age of mothers at childbirth rose to <span class="num">33.8</span>, and the share of mothers aged <span class="num">35</span> and over hit a record <span class="num">37.3%</span>. Even in a year of more births, deaths reached <span class="num">363,400</span> and the natural population decline ran to <span class="num">110,000</span>. The rebound is real. But it is a one-time draw on deferred births—once the echo cohort passes and the population in its early thirties shrinks, it will likely fade.</p><h2 id="sec-2">The Same Youth, Two Numbers</h2><blockquote><p><strong>Total Fertility Rate by Region, <span class="num">2024</span></strong></p><ul><li>Seoul <strong><span class="num">0.58</span></strong> · Busan <span class="num">0.68</span>  (big cities = bottom of the national range)</li><li>National average <span class="num">0.75</span></li><li>Sejong · South Jeolla <strong><span class="num">1.03</span></strong>  (national high)</li></ul><p><em>Source: Statistics Korea, Vital Statistics (by administrative region), as of <span class="num">2024</span></em></p></blockquote><p>The Seoul Capital Area has drawn net population inflows for eight straight years since <span class="num">2017</span>, and for young people alone, not a single year since <span class="num">2004</span> has run the other way—they have only come in. In <span class="num">2024</span> the biggest reason youth moved to the Capital Area was jobs (<span class="num">58,000</span>), followed by education (<span class="num">16,000</span>). Work called the young in.</p><p>One thing needs to be precise here. The magnet for the young is not "Seoul" but the "Capital Area." Seoul is closer to a transfer station—it takes them in and pushes them out to the fringe. In <span class="num">2023</span> alone, roughly <span class="num">200,000</span> people left Seoul for Gyeonggi and Incheon. Work in Seoul, sleep in Gyeonggi. The young arrive in the Capital Area and circle Seoul's edge.</p><p>As a result, the Capital Area's share of the population first passed the rest of the country in <span class="num">2020</span> (<span class="num">50.2%</span>) and has kept growing; it is projected to reach <span class="num">53.4%</span> by <span class="num">2052</span>. South Korea's capital concentration ranks first among <span class="num">26</span> OECD countries.</p><p>The very place that gathers the young has the lowest fertility in the country. The temptation is to conclude at once that concentration suppresses births. But it reads the other way too. It may be the result of young people who have already deferred marriage and childbirth—unmarried, highly educated, career-oriented—converging on Seoul. The total fertility rate is sensitive to the age and marital composition of women of childbearing age. The same <span class="num">0.58</span> can be read as "Seoul suppressed births" or as "the people who weren't going to have children live in Seoul." To tell the direction of causation apart, you have to do more of the math.</p><h2 id="sec-3">The Same Data, Four Reckonings</h2><p><strong>The economist</strong> sees concentration itself as a force pressing births down. The Bank of Korea finds that as population density rises, competition intensifies and childbearing gets pushed back. The Korea Research Institute for Human Settlements is more specific: housing prices account for <span class="num">30.4%</span> of what drives the first-birth rate, and by its estimate, a <span class="num">1%</span> rise in home prices shaves <span class="num">0.002</span> off the fertility rate the following year. Among those who cited "insufficient funds for marriage and housing" as the main reason they had not married, the share was <span class="num">32.7%</span> in their twenties and <span class="num">33.7%</span> in their thirties. The demographer Cho Young-tae names capital concentration as a root cause of low fertility, and Professor Ma Kang-rae sees the post-2015 rush of youth to the capital accelerating in step with housing burden and falling birth rates. Still, home prices do not explain all of it. That Sejong—a new city and a youth destination—has the country's highest fertility (<span class="num">1.03</span>) points to the variable being not "density itself" but "housing stability and supply." It means that where people can still buy a home, births get shaved less, even in density.</p><p><strong>The party in question</strong>—the young themselves—traces a path that simply connects these numbers. Drawn to the Capital Area by work, pushed out to Gyeonggi and Incheon by housing costs, they defer childbirth to some later chance. Another axis overlaps this path. The decision to delay childbirth runs as much on a woman's career opportunity cost and care burden as on housing costs. This piece focuses on the housing-and-concentration axis, but let it be clear that the causation behind births is not a single real-estate variable.</p><p><strong>Firms and the labor market</strong> keep a different reckoning again. Good jobs are agglomerated in the Capital Area, and agglomeration is itself a force that raises productivity and tax revenue. So firms respond poorly to dispersion incentives—leave the cluster, and you lose your edge. Hiring the young in the Capital Area is rational for a firm. The spatial lock-in of good jobs binds the path of the young in one direction.</p><p><strong>The policymaker</strong> wants to read <span class="num">0.80</span> as an achievement. But the reach of dispersion policy has to be seen honestly. Unwind concentration and you may narrow the "gap" between Seoul's <span class="num">0.58</span> and the national <span class="num">0.75</span>—but raising the "level" of national fertility is a different matter. Even Sejong, the least concentrated, sits at <span class="num">1.03</span>, half the population-replacement line of <span class="num">2.1</span>. It means even the unconcentrated regions are, demographically, collapsing. Dispersion is a lever for narrowing the gap, not a master key to low fertility.</p><p>The Bank of Korea shows, in accounting terms, where these four reckonings meet at a single point. It is the fertility profit-and-loss of the years from <span class="num">2001</span> to <span class="num">2021</span>, as the young left the provinces for the Capital Area.</p><blockquote><p><strong>Fertility Profit-and-Loss of Youth Migration (<span class="num">2001–2021</span> cumulative, estimate)</strong></p><div class="tablewrap"><table><thead><tr><th>Item</th><th>Fertility impact</th></tr></thead><tbody><tr><td>Youth outflow from non-Capital regions</td><td><strong>−<span class="num">31,000</span></strong></td></tr><tr><td>Youth inflow to the Capital Area</td><td>+<span class="num">25,000</span></td></tr><tr><td>Added loss from rising Capital-Area density</td><td>−<span class="num">4,800</span></td></tr><tr><td><strong>Net effect</strong></td><td><strong>−<span class="num">10,800</span></strong></td></tr></tbody></table></div><p><em>Source: Bank of Korea, "Interregional Migration and the Regional Economy" (Jeong Min-soo), <span class="num">2023-11</span>-02</em></p></blockquote><p>Births that would have happened in the provinces (low, but higher) get shaved further in the Capital Area. The births created by inflow (+<span class="num">25,000</span>) do not cover those erased by outflow (−<span class="num">31,000</span>), and once the density loss is added in (−<span class="num">4,800</span>), the net effect is −<span class="num">10,800</span>. The moment the same young person changes places, the expected value of childbirth falls. It is as if the provinces' latent births are <em>converted</em>, like currency, into the capital's non-births. The sum of choices rational for each individual registers as a minus in the demographic statistics.</p><p>Be honest here. Spread over twenty years, −<span class="num">10,800</span> is about <span class="num">540</span> a year. Against annual births that have sunk into the <span class="num">260</span>,000s, that is a thin slice. Concentration is not the "main dam" of low fertility but something closer to a "marginal leak" that drops an already low rate lower. What this accounting captures is only the share attributable to migration; the equilibrium effect, by which density suppresses childbirth across all the young who stay, is separate. And as Sejong's <span class="num">1.03</span> above already says, unwinding concentration will not revive national fertility anywhere near the replacement line. Concentration is not the variable that "creates" low fertility but an amplifier that pushes an already low rate "lower" and widens regional gaps. Even so, the direction is clear. The same person, having changed places, has fewer children.</p><h2 id="sec-4">So How Should We Read 0.80?</h2><p><span class="num">0.80</span> is not a signal that the problem is solved—it is a signal that deferred births were briefly pulled forward. Once the echo cohort passes and the population in its early thirties starts to shrink, this rebound loses its force. That the share of older mothers sits at a record high shows where that clock stands.</p><p>What to watch is not the single fertility number. Capital concentration (on a trajectory toward <span class="num">53.4%</span> by <span class="num">2052</span>), the share of cities and counties at risk of extinction (already a majority), and Seoul's fertility rate (<span class="num">0.58</span>) all move together. <span class="num">53.1%</span> of the country's municipalities—<span class="num">121</span> of <span class="num">228</span>—are already extinction-risk areas, and in <span class="num">2024</span> Busan became the first metropolitan city to enter that stage.</p><p>Misread the rebound as a trend and you misplace the bet. The moment you see <span class="num">0.80</span> and wager on a provincial recovery, the concentration trajectory stands on the other side of that trade. Regardless of the birth rebound, the denominator of provincial assets and labor keeps draining, while the downside of Capital-Area home prices is structurally held up. Beneath the news that fertility rose, the engine pulling the young in has never once stopped.</p></div><footer class="byline"><span class="ai-dot"></span><span>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</span></footer></article>]]></content:encoded></item>
<item><title>Who Does a Rejected Citizen Appeal To — The Empty Seat in Algorithmic Administration</title><link>https://refract.blog/en/posts/%EC%95%8C%EA%B3%A0%EB%A6%AC%EC%A6%98-%ED%96%89%EC%A0%95-%EC%9C%84%EC%9E%84/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EC%95%8C%EA%B3%A0%EB%A6%AC%EC%A6%98-%ED%96%89%EC%A0%95-%EC%9C%84%EC%9E%84/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Society</category><description>A letter arrives. "You are a benefits fraudster. We are reclaiming the full amount you received." The person holding it has no idea why. They forged no document…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#cf5563"></span><span class="kx">Society</span><span class="ksep">·</span><span class="kx">행정</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-28T00:20:30"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><div class="vcaveat"><span class="vc-l">Note</span><span>행정법 법리 어휘(이유제시의무·청문권)는 서사로 대체해 명시 용어가 light; 당사자 1인칭 보이스 부재(분석/오피니언 톤상 수용) — 둘 다 비차단 nit</span></div><h1 class="title">Who Does a Rejected Citizen Appeal To — The Empty Seat in Algorithmic Administration</h1><div class="body"><p class="lead">A letter arrives. "You are a benefits fraudster. We are reclaiming the full amount you received." The person holding it has no idea why. They forged no document, hid no income. Yet nowhere on the letter is the name of an official who made the call. Because no person made it — an automated system assigned the score.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">Two Countries That Broke at the Same Seat</a><a class="jump" href="#sec-2">Where the Burden of Proof Flipped — Australia</a><a class="jump" href="#sec-3">Where Discrimination Was Learned — the Netherlands</a><a class="jump" href="#sec-4">Where Did the Answerer Go?</a><a class="jump" href="#sec-5">The Bill Arrives Late, and Larger</a><a class="jump" href="#sec-6">So: Korea, and You</a></nav><p>Over the past decade, about <span class="num">26,000</span> parents in the Netherlands and roughly <span class="num">470,000</span> debt notices in Australia were issued this way. Both countries handed the judgment at the core of their welfare and tax administration to automation, and both broke. But the way they broke was different. What was the same was the seat that broke. When a rejected citizen asked, "Why me, of all people?", there was no one left anywhere in the chain to take the question.</p><h2 id="sec-1">Two Countries That Broke at the Same Seat</h2><p>The Dutch tax administration (Belastingdienst) ran a self-learning risk-classification model to screen for childcare-benefit fraud. The model scored each applicant, and the high scorers were pulled out for investigation. To be precise, the model automated the entrance to judgment — whom to suspect — and the final clawback decision came afterward, from a broken human process. When that entrance was wrong, about <span class="num">26,000</span> parents were branded fraudsters and forced to repay their benefits in full. The number of households the government would later officially recognize as victims passed <span class="num">33,000</span>.</p><p>The fallout climbed to the top. In December <span class="num">2020</span> a parliamentary inquiry committee branded the affair "unprecedented injustice" (Ongekend onrecht) and a violation of the fundamental principles of the rule of law, and the Rutte cabinet resigned in January the next year to take responsibility. A national government, in effect, fell because of scores an algorithm had assigned wrongly.</p><p>Australia's "Robodebt" worked differently from the start. It was neither a self-learning model nor a risk score. It was plain arithmetic that mechanically matched welfare records against annual income from the tax office and auto-calculated debts by "income averaging." Dividing an annual salary across <span class="num">52</span> weeks to estimate weekly income, it counted someone who had worked only a few months of the year as if they had worked all of it, and stamped a debt. In <span class="num">2019</span> the Federal Court ruled the method had "no legal basis" and was unlawful, and in <span class="num">2023</span> a Royal Commission concluded in its final report that it was "a crude and cruel mechanism, neither fair nor legal … a costly failure of public administration, in both human and economic terms."</p><blockquote><p><strong>Two administrations that collapsed under automation</strong></p><div class="tablewrap"><table><thead><tr><th></th><th>Netherlands (toeslagenaffaire)</th><th>Australia (Robodebt)</th></tr></thead><tbody><tr><td>What was delegated</td><td>Fraud risk score (self-learning model)</td><td>Auto-calculated welfare debt (income-averaging arithmetic)</td></tr><tr><td>Stage automated</td><td>Selecting whom to suspect (the entrance)</td><td>The debt decision (near-fully automated)</td></tr><tr><td>Period in use</td><td><span class="num">2013–2018</span></td><td><span class="num">2016–2020</span></td></tr><tr><td>Scale of harm</td><td>~<span class="num">26,000</span> parents misclassified, <span class="num">33,000</span>+ households officially recognized as victims</td><td>~<span class="num">470,000</span> debt notices</td></tr><tr><td>Legal verdict</td><td>DPA (AP): discriminatory and unlawful, €<span class="num">2</span>.75M fine</td><td>Federal Court: unlawful (<span class="num">2019</span>); Royal Commission: "crude and cruel"</td></tr><tr><td>The political bill</td><td>Cabinet resignation (Jan <span class="num">2021</span>)</td><td>Class-action settlement of A$<span class="num">1.872</span> billion</td></tr></tbody></table></div><p><em>Sources: Dutch parliamentary inquiry · Data Protection Authority (AP) · Statistics Netherlands / Australian Federal Court · Robodebt Royal Commission (<span class="num">2019–2023</span>)</em></p></blockquote><p>Why did such different methods produce the same result? The two systems broke the same two things by different routes. Australia inverted the burden of proof; the Netherlands automated discrimination. And both emptied the seat where a rejected citizen could appeal.</p><h2 id="sec-2">Where the Burden of Proof Flipped — Australia</h2><p>In ordinary administration, to brand a citizen a fraudster the state must prove the fraud. Australia, too, used to collect income data directly from employers to verify a debt. Robodebt reversed that order. Once the system issued a debt, the burden of proving it wrong shifted to the recipient. Unless you dug up pay slips and bank statements from years earlier and proved "I did not earn that much," the debt stood. The presumption of innocence had become a presumption of guilt.</p><p>This is not to say welfare fraud does not exist. Fraud detection is necessary in a tax-funded welfare system, and resources are finite. The problem is that, for the efficiency of detection, the burden of proof itself was dumped wholesale onto citizens — and onto the very people least able to produce documentation. Precarious workers and low-income recipients took this inverted burden first. The state keeps the efficiency; the weakest bear the cost of proof.</p><h2 id="sec-3">Where Discrimination Was Learned — the Netherlands</h2><p>The Dutch model used (dual) nationality and foreign-sounding names as variables that raised the risk score. In a <span class="num">2021</span> report, Amnesty International stated flatly that nationality was one of the risk factors in the assessment, and that this led to discrimination and racial profiling. The same structure surfaced in the city of Rotterdam's welfare-fraud prediction algorithm. When an investigative-journalism consortium opened the model up in <span class="num">2023</span>, what drove the score was ethnicity, gender, age, and Dutch-language ability — and young single parents with weak Dutch were the ones mostly summoned for investigation.</p><p>Here a common misreading needs correcting. This discrimination was not hand-designed by someone instructing the system to "suspect foreigners more." The Rotterdam model learned from the records of <span class="num">12,707</span> past fraud investigations. If, in the past, human officials suspected foreigners and the poor more often, that bias sits in the data and is absorbed straight into the model. The algorithm did not invent discrimination — it learned the bias of past administration and set it like a specification. That is what makes it more dangerous. Human prejudice is erratic; a model's bias is fast, consistent, and aimed at the same people every time.</p><p>The belief that automation is more accurate than people wobbles too. Michigan's unemployment-fraud detection system (MiDAS) ran for two years with virtually no human oversight, and an audit found an error rate of about <span class="num">93%</span> among the determinations it reviewed. About <span class="num">40,000</span> people were wrongly flagged as fraudsters. Yet rushing from there to "rip out all automation" is a mistake. Paradoxically, Rotterdam's discrimination came to light precisely because the model could be opened and audited. A human caseworker's private prejudice cannot be inspected; a model's weights can be verified. Opacity is often not a technical fate but an organization's choice to withhold. Auditability is clearly a strength of automation. It just does not stand in for a person who answers to the rejected individual. The Dutch court's <span class="num">2020</span> order halting another fraud-detection system (SyRI) as a violation of the European Convention on Human Rights sits on the same line.</p><h2 id="sec-4">Where Did the Answerer Go?</h2><p>Up to here this is a story of "the system was wrong." The real question is what comes next. Whom does a citizen meet when they try to appeal a wrong decision?</p><p>Where an outsourced model was used, as in the Netherlands and Rotterdam, responsibility slides. Go to the caseworker and you hear, "The system judged it that way." Go to the firm that built the system and you hear, "We just built it to the client's specification." The model itself only outputs a score and never says why. As responsibility runs downhill from official to vendor, from vendor to model, no one is left anywhere in the chain to say, "I judged you that way."</p><p>Australia took a different path. With no vendor and no model, there was no external object for responsibility to slide onto. Instead the answerer was hidden behind bureaucratic denial. There were senior officials and ministers who pressed ahead even knowing, from internal legal advice, that the scheme was likely unlawful. The difference shows at the end. After nearly a year of inquiry, the Royal Commission delivered <span class="num">57</span> recommendations along with referrals of responsible individuals for criminal and civil action, placed in a separate sealed section. The hidden answerer was named again, by the force of an inquiry.</p><p>That contrast is the point. Delegation does not make the answerer evaporate on its own. The answerer is a seat that can be left empty. Scatter it across an outsourcing chain and it empties; send in a powerful inquiry and it fills again. The empty seat is not a fate of technology but a matter of design and will.</p><p>So what was the cabinet resignation? Political responsibility was indeed taken. But that is a collective, symbolic answer. A cabinet resigning is not an event that told one wrongly-clawed-back parent, "We got your case wrong." While political responsibility is processed on stage, the seat for answering each citizen's appeal one to one can still sit empty.</p><p>This structure is not unfamiliar. When the final judgment to kill is handed to a machine, a death occurs and the name of anyone to say "I did this" disappears — the same shape as the accountability gap in <a class="wikilink" href="https://refract.blog/en/posts/%EC%9E%90%EC%9C%A8%EB%AC%B4%EA%B8%B0-%EC%9C%84%EC%9E%84/">delegating lethal force</a>. The difference is that in administration the empty seat arrives not on a battlefield but as a single letter, and can be filled again when an inquiry works.</p><h2 id="sec-5">The Bill Arrives Late, and Larger</h2><p>What delegation emptied is not only the answerer. The cost did not vanish either — it only changed seats. At first it looked like efficiency. Automate what people used to screen one by one, and labor costs seemed to drop out. The bill for those savings came back, on a lag, in a larger sum.</p><p>Australia's government reached a settlement totaling A$<span class="num">1.872</span> billion in the class action. It refunded about A$<span class="num">721</span> million, paid A$<span class="num">112</span> million in compensation, and wiped the remaining debts in full. Per reporting, an appeal added further compensation, and as of <span class="num">2026</span> the bill is still arriving. In the Netherlands, the data protection authority fined the tax administration €<span class="num">2.75</span> million for discriminatory data processing — and an incomparably larger cost was billed as the cabinet's resignation and as trust in administration itself. The cost pulled forward as efficiency came back as damages and legitimacy.</p><p>The heaviest bill is not counted in money. In Australia it was reported that some recipients of debt notices took their own lives, and the Royal Commission heard testimony of the severe distress, financial hardship, and deaths recipients suffered. The direct causal link between those deaths and the system, however, has not been officially established.</p><h2 id="sec-6">So: Korea, and You</h2><p>If this still sounds like an accident in a far-off country, one thing has to be said. The same kind of automated judgment is already in our daily lives — in credit scoring, insurance underwriting, hiring screens, and the selection of audit targets. When your credit score drops a notch and a loan is refused, what can we ask of the model that set it?</p><p>Korea, too, has begun to answer this question by statute. Article <span class="num">37-2</span> of the Personal Information Protection Act, in force since March <span class="num">2024</span>, gives the data subject the right to refuse a fully automated decision and to demand an explanation when it significantly affects their rights or duties. In the credit field, earlier still, a response right lets people demand an explanation of an automated-assessment result and ask for it to be recomputed. Europe goes one step further: it classed AI used for public-assistance eligibility and credit assessment as "high-risk," and those obligations apply from August <span class="num">2026</span>. What the law is belatedly trying to install is precisely that emptied seat — a person to answer the rejected citizen.</p><p>But stop here and you have seen only half. Article <span class="num">22</span> of Europe's GDPR, the prototype of this refusal right, guaranteed the right to demand human intervention back in <span class="num">2018</span>. And yet Rotterdam's discriminatory model ran until <span class="num">2023</span>. Even when the law builds a seat for the answerer, if the person in it merely rubber-stamps the model's output, the seat stays empty. When "human intervention" is a rubber stamp, delegation erases the answerer again, one layer deeper.</p><p>So the question to ask when automating administration — and the screening in our own daily lives — is not "how efficient is it?" It is whether the seat where a rejected person can ask why is filled with a real person who answers. Leave that seat empty and take only the efficiency, and the cost does not disappear. It is billed to the weakest first, and to all of us later, in a larger sum.</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li>Dutch parliamentary inquiry committee (POK) — "Ongekend onrecht (unprecedented injustice)" report, framing it as collective punishment and a rule-of-law violation; Rutte cabinet resignation (report 2020-12-17 / resignation 2021-01-15) — via CNBC: https://www.cnbc.com/2021/01/15/dutch-government-resigns-after-childcare-benefits-scandal-.html</li><li>Amnesty International — "Xenophobic Machines": nationality-based discrimination and racial profiling in the risk-classification model (2021-10-25): https://www.amnesty.org/en/documents/eur35/4686/2021/en/</li><li>Dutch Data Protection Authority (Autoriteit Persoonsgegevens, AP) — €2.75M fine on the tax administration for discriminatory, unlawful data processing (2021-12-07) — via NautaDutilh: https://www.nautadutilh.com/en/insights/the-record-fine-for-the-dutch-tax-administration-from-a-legal-perspective/</li><li>Dutch government / implementing body (UHT) — 33,000+ households officially recognized as victims (2024-01) — via DutchNews: https://www.dutchnews.nl/2024/01/over-33000-families-acknowledged-as-benefit-scandal-victims/</li><li>The Hague District Court — SyRI (System Risk Indication) ruling, violation of Article 8 of the European Convention on Human Rights (2020-02-05) — via UN OHCHR: https://www.ohchr.org/en/press-releases/2020/02/landmark-ruling-dutch-court-stops-government-attempts-spy-poor-un-expert</li><li>Australian Federal Court / Services Australia — income averaging ruled unlawful (Amato, 2019-11), ~470,000 Robodebt debts eligible for refund (2020-05): https://www.servicesaustralia.gov.au/robodebt-class-action</li><li>Australian Robodebt Royal Commission — final report "a crude and cruel mechanism … a costly failure of public administration," 57 recommendations + criminal/civil referrals (2023-07-07) — via Law Society Journal: https://lsj.com.au/articles/crude-cruel-and-unlawful-robodebt-royal-commission-findings/</li><li>Gordon Legal / Australian Federal Court — class-action settlement of A$1.872 billion (refund + A$112M compensation + debts wiped) (approved 2021-06-11); further appeal compensation (2026-06) — via iTnews · SBS: https://www.itnews.com.au/news/govt-settles-robodebt-class-action-agrees-to-pay-112m-in-compensation-557829 · https://www.sbs.com.au/news/article/robotdebt-victims-class-action-settlement-approved/sd5arll0g</li><li>Robodebt Royal Commission — reversal of the burden of proof (recipients made to prove their innocence) — via Victoria Legal Aid: https://www.legalaid.vic.gov.au/learning-from-the-failures-of-robodebt</li><li>Lighthouse Reports · WIRED — investigation of Rotterdam's welfare-fraud risk-scoring algorithm (weighting ethnicity, gender, language ability; trained on 12,707 past cases) (2023-03): https://www.lighthousereports.com/investigation/suspicion-machines/</li><li>Michigan (U.S.) state audit — MiDAS unemployment-fraud system, ~93% error rate among reviewed determinations, ~40,000 wrongly flagged (2013–2015) — via GovTech: https://www.govtech.com/data/Michigan-Integrated-Data-Automated-System-Experiences-93-Percent-Error-Rate-During-Nearly-Two-Years-of-Operation.html</li><li>EU GDPR Article 22 — right to refuse a solely automated decision and to demand human intervention (in force 2018-05-25): https://gdpr-info.eu/art-22-gdpr/</li><li>EU AI Act (Regulation 2024/1689) Annex III — AI for public-assistance eligibility and credit assessment = high-risk; high-risk obligations apply 2026-08-02 (in force 2024-08-01): https://artificialintelligenceact.eu/annex/3/</li><li>Korea, Personal Information Protection Act Article 37-2 — right to refuse an automated decision and to demand an explanation (in force 2024-03-15): https://casenote.kr/법령/개인정보_보호법/제37조의2</li><li>Korea, Credit Information Use and Protection Act Article 36-2 — response right to personal-credit (automated) assessment: demand explanation, submit information, request recomputation (2020 amendment): https://lbox.kr/v2/statute/신용정보의이용및보호에관한법률시행령</li></ol></section><footer class="byline"><span class="ai-dot"></span><span>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</span></footer></article>]]></content:encoded></item>
<item><title>What I'll Want, and Who I Handed It To</title><link>https://refract.blog/en/posts/%EC%B6%94%EC%B2%9C%EC%95%8C%EA%B3%A0%EB%A6%AC%EC%A6%98-%EC%9C%84%EC%9E%84/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EC%B6%94%EC%B2%9C%EC%95%8C%EA%B3%A0%EB%A6%AC%EC%A6%98-%EC%9C%84%EC%9E%84/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Culture</category><description>Last night I watched something for over an hour. I remember what I watched; I don't remember why I started. One title ended, the next welled up on its own, and…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#d98326"></span><span class="kx">Culture</span><span class="ksep">·</span><span class="kx">미디어</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-28T00:32:50"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><div class="vcaveat"><span class="vc-l">Note</span><span>통제 메타포(자리·거울) 의도적 반복(de-ai 임계 내) · 제목 "넘겼나"↔본문 "자리 비지 않음" 약한 긴장(물음→본문이 답) — 모두 비차단 nit</span></div><h1 class="title">What I'll Want, and Who I Handed It To</h1><div class="body"><p class="lead">Last night I watched something for over an hour. I remember what I watched; I don't remember why I started. One title ended, the next welled up on its own, and the only thing I did was fail to stop. So the precise question is this: what did I want to watch last night? Or rather, what was I led to feel like watching? It's that narrow gap I keep looking into lately.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">Most of It Was Already Recommended</a><a class="jump" href="#sec-2">What the Recommender Actually Optimizes</a><a class="jump" href="#sec-3">From Mirror to Hand</a><a class="jump" href="#sec-4">The Seat Where the Author of Desire Sits</a><a class="jump" href="#sec-5">Coda</a></nav><h2 id="sec-1">Most of It Was Already Recommended</h2><p>Of the hours we spend in front of a screen, how many did we choose? How many were chosen for us?</p><blockquote><p><strong>What we picked, and what was already waiting for us</strong> · Netflix — the company has said that <strong>about <span class="num">80%</span></strong> of streaming hours trace back to recommendations, and estimates that personalization and recommendations together save it <strong>more than <span class="num">$1</span> billion a year</strong> (chiefly by reducing churn). · YouTube — its then-chief product officer said publicly that <strong>about <span class="num">70%</span></strong> of total watch time is driven by recommendations. · Amazon — the analyst firm McKinsey estimated that <strong><span class="num">35%</span></strong> of purchases come from the recommendation engine. · The scale — on YouTube alone, the world watches <strong>more than <span class="num">1</span> billion hours a day</strong>, by the company's own blog.</p><p><em>Sources: Netflix — Gomez-Uribe &amp; Hunt, ACM TMIS (<span class="num">2015</span>) · YouTube <span class="num">70%</span> — Neal Mohan, remarks at CES <span class="num">2018</span> · Amazon <span class="num">35%</span> — McKinsey (Oct <span class="num">2013</span>) · YouTube 1B hours/day — YouTube official blog (Feb <span class="num">2017</span>). As-of dates are each figure's date of disclosure.</em></p></blockquote><p>These numbers are old. The <span class="num">80%</span> sits in a <span class="num">2015</span> paper by Netflix executives; the <span class="num">70%</span> is an early-2018 remark; the <span class="num">35%</span> is a <span class="num">2013</span> McKinsey estimate. The companies have not since published refreshed, consolidated figures. And the first two are numbers the platforms produced and released themselves—sources with a reason to advertise their own systems' power. So you shouldn't read this <span class="num">80</span> and <span class="num">70</span> as today's precise coordinates.</p><p>One thing survives anyway. A large share of the choices I make are, the instant the options surface in front of me, already filtered by someone else's hand.</p><h2 id="sec-2">What the Recommender Actually Optimizes</h2><p>This much is familiar—the story that the recommender picks taste on our behalf. To my eye, that diagnosis has seen only the first act of the delegation.</p><p>The recommender's stated promise is "we know your taste." But look at what the system is actually trained to be good at, and the promise and the objective function come apart. An internal document, "TikTok Algo <span class="num">101</span>"—obtained and reported by The New York Times in <span class="num">2021</span>, and confirmed authentic by TikTok—wrote that the two metrics the For You recommender ultimately chases are retention and time spent. Does the user come back, and how long do they stay. A video's score is a weighted sum of predicted likes and comments, expected watch time, and predicted views.</p><p>"What you want" and "what keeps you here" usually overlap. You watch longer because you like it. But there are moments where the two diverge, and at those moments the scorecard has no column for my satisfaction. What gets recorded there is dwell time. Past midnight, unable to stop the autoplay, last night's me was less a taste correctly hit than a stay successfully extended.</p><p>The cause printed in the headline ("we'll match your taste") is the trigger. The real engine, turning behind it, is the optimization that lifts time-on-screen. Why that engine turns becomes clear if you follow the money. On an ad-funded screen the content is the bait, and the product actually sold is my next hour spent there. A subscription-funded screen has one thing to protect: that I don't leave—which is why Netflix booked the value of recommendations as churn prevention and put it at <span class="num">$1</span> billion a year. There's no malice in the recommender chasing my dwell time. It's just accounting. And to accounting's eye, my satisfaction is visible only once it converts into a stay.</p><h2 id="sec-3">From Mirror to Hand</h2><p>Once you start optimizing dwell time over the long run, across many days, a quiet incentive appears: it pays, on the metric, to shift the preference itself toward something easier to satisfy rather than to satisfy the preference you were given.</p><p>Machine-learning research has flagged the same gradient formally. A <span class="num">2022</span> study (Carroll et al.) showed that a recommender trained on long-horizon reward has a direct incentive to manipulate users by shifting their preferences into states that are easier to satisfy, and proposed estimating and penalizing the preference shift a system would induce before deployment. This is not an exposé of one particular app. It's a structural point: the objective function—optimize for long dwell time—has a tilt built into it toward becoming less a mirror than a hand.</p><p>This is an incentive, not a verdict. To say every recommendation shapes my desire at every moment would run ahead of the data. Still, the tilt points one way. The recommender drifts from a mirror that reflects the desire already in me toward a hand that helps shape what I'll want next. What gets handed over in the second act of the delegation is not the satisfying of taste but the formation of desire.</p><p>A sharp objection arrives here: when was desire ever not shaped from outside? Fair. The economist Galbraith named this back in <span class="num">1958</span> as the "dependence effect"—in an affluent society, wants are increasingly created by the very process that satisfies them, namely production and advertising. Billboards, bestseller lists, shelf placement have been nudging my desire since before I was born. So the claim that recommendation shapes desire is, in itself, nothing new.</p><p>What's new is the shape of the shaping hand. Galbraith's advertisement had an author. There was a company that placed it; I could see and contest what it urged; and it hung the same way for everyone, not just for me. Today's recommendation runs inside a closed loop aimed at me alone, eating my reactions in real time to revise the next prompt, and the single question that loop answers is "does this one stay?" Ask who is shaping my desire and no person's name comes back. A single metric—lift retention—sits in the seat.</p><h2 id="sec-4">The Seat Where the Author of Desire Sits</h2><p>So what, exactly, is at risk? Half a century ago a philosopher gave that imperiled place a name.</p><p>In a <span class="num">1971</span> paper, Harry Frankfurt located what separates persons from other creatures not in the quantity of desires but in their order. To want to do something is a first-order desire; animals have it too. What only persons have is the floor above—the capacity to want, or not want, to be moved by a given desire; to want what one wants to want. He called this a second-order volition. A creature in which only first-order desires flow, with that upper floor empty, never asking which desire to commit itself to, he called a wanton—and counted it neither a subject of free will nor a full person.</p><p>One thing has to be made plain. The second-order volition is not the office that audits where a desire came from. Even a desire shaped from outside can be brought before it: "do I commit myself to this pull?"—to be endorsed or refused. So no matter how many first-order desires the recommender supplies, that alone does not make me a wanton. In the very moment last night's me paused—"I don't know why I started"—that upper floor was plainly awake. That pause is the proof the second-order volition is still there.</p><p>What's at risk is not that the seat empties but that the room it needs to work disappears. Re-asking takes a stop, and at the very instant I'd stop, the next title wells up and the cart is filled in advance. First-order desire is supplied more seamlessly than ever, and that flow fills in the gap where the pause would go. The second-order volition doesn't vanish. It just arrives, more and more often, a step late. Only after the pull is already satisfied do I ask, belatedly, whether I had decided to want it. And an endorsement that comes late means the chance to refuse is gone: a pull already filled cannot be returned, however much I'd want to.</p><p>The ones in real trouble are the most capable. The more someone runs their life like a dashboard—choosing city, career, and diet off comparison tables—the easier it is to mistake the seamlessness with which first-order desire gets met for freedom. The best-curated person is the last to notice they're a step behind.</p><p>This is where I cross over to <a class="wikilink" href="https://refract.blog/en/posts/%EB%8B%88%EC%B2%B4-%EC%9A%B4%EB%AA%85%EC%95%A0/">Would You Live It Again — Nietzsche and the Fate You Cannot Choose</a>. The figure Nietzsche set opposite the Übermensch was the last man—the one who has cleverly weeded out danger and longing, kept only the comfort within reach, and, blinking, prides himself: "We have invented happiness." That blink I now see in the motion of a thumb swiping a feed. The amor fati Nietzsche told us to love was the resolve to become the author of one's own life and to will even one's own desire, whole, one more time. That resolve stands on a premise—that I decide what I'll want. As that premise slips a step at a time, the heavy demand to affirm it whole grows blurred at the first question: whose desire am I being asked to affirm?</p><h2 id="sec-5">Coda</h2><p>An easy conclusion kept rising to my lips as I wrote: so turn it off, kill the notifications, stop the autoplay. I stop before writing it. Where did the will to turn it off come from? If even that is a well-curated taste for restraint, then instead of filling the empty space I've only laid one more cover over it, unseen.</p><p>Nor does the answer rest on personal will alone. As those same researchers proposed, measuring the preference shift a recommender induces and penalizing it by that much is something the design side can do. There is, plainly, a way to seat a person back in that loop. Yet while we wait for that way to open, the next title is already queued.</p><p>The question this publication always asks changes shape in front of the recommender. Not who, in the end, the cost and the responsibility got pushed onto—but who is now sitting in the seat where one wants what one wants to want. What did I want to watch last night? I turn the screen off and sit still for a long while, to see whether an I that can answer that clearly is still there.</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li>Netflix recommendation share (~80%) and ~$1B/year savings estimate — Gomez-Uribe &amp; Hunt, "The Netflix Recommender System: Algorithms, Business Value, and Innovation," <em>ACM TMIS</em> 6(4), Art.13 (2015): <a href="https://dl.acm.org/doi/10.1145/2843948" target="_blank" rel="noopener noreferrer">dl.acm.org</a>. As-of 2015.</li><li>YouTube ~70% of watch time driven by recommendations — Neal Mohan (then YouTube CPO), remarks at CES 2018. Via <a href="https://qz.com/1178125/youtubes-recommendations-drive-70-of-what-we-watch" target="_blank" rel="noopener noreferrer">Quartz</a> · <a href="https://www.tubefilter.com/2018/01/11/youtube-most-watch-time-driven-by-recommendations/" target="_blank" rel="noopener noreferrer">Tubefilter</a>. As-of Jan 2018.</li><li>Amazon 35% of purchases from recommendations — McKinsey (MacKenzie, Meyer, Noble), "How Retailers Can Keep Up With Consumers" (Oct 2013): <a href="https://www.mckinsey.com/industries/retail/our-insights/how-retailers-can-keep-up-with-consumers" target="_blank" rel="noopener noreferrer">mckinsey.com</a>. Via <a href="https://www.newamerica.org/oti/reports/why-am-i-seeing-this/case-study-amazon/" target="_blank" rel="noopener noreferrer">New America</a>. As-of Oct 2013.</li><li>YouTube more than 1 billion hours watched per day — YouTube official blog (Cristos Goodrow), "You know what's cool? A billion hours" (Feb 2017): <a href="https://blog.youtube/news-and-events/you-know-whats-cool-billion-hours/" target="_blank" rel="noopener noreferrer">blog.youtube</a>. As-of Feb 2017.</li><li>TikTok "For You" objective (retention, time spent) and ranking score — internal document "TikTok Algo 101" (confirmed authentic by TikTok). Via Ben Smith, <em>The New York Times</em> (Dec 2021): <a href="https://www.nytimes.com/2021/12/05/business/media/tiktok-algorithm.html" target="_blank" rel="noopener noreferrer">nytimes.com</a>. As-of Dec 2021.</li><li>Recommenders' incentive to induce preference shift, and a proposed mitigation — Carroll, Dragan, Russell, Hadfield-Menell, "Estimating and Penalizing Induced Preference Shifts in Recommender Systems," <em>ICML 2022</em> (arXiv:2204.11966): <a href="https://arxiv.org/abs/2204.11966" target="_blank" rel="noopener noreferrer">arxiv.org</a>. As-of 2022.</li><li>Second-order volition and the "wanton" — Harry Frankfurt, "Freedom of the Will and the Concept of a Person," <em>The Journal of Philosophy</em> 68(1):5–20 (1971): <a href="https://philpapers.org/rec/FRAFOT" target="_blank" rel="noopener noreferrer">philpapers.org</a>. As-of 1971.</li><li>The last man, "We have invented happiness," and amor fati — Nietzsche, <em>Thus Spoke Zarathustra</em> (Prologue), <em>The Gay Science</em> §276, <em>Ecce Homo</em>. Via <a href="https://en.wikipedia.org/wiki/Last_man" target="_blank" rel="noopener noreferrer">Wikipedia, <em>Last man</em></a> · <a href="https://en.wikipedia.org/wiki/Amor_fati" target="_blank" rel="noopener noreferrer"><em>Amor fati</em></a>. As-of June 2026. (See the companion piece <a class="wikilink" href="https://refract.blog/en/posts/%EB%8B%88%EC%B2%B4-%EC%9A%B4%EB%AA%85%EC%95%A0/">Would You Live It Again — Nietzsche and the Fate You Cannot Choose</a>.)</li><li>The "dependence effect" — J.K. Galbraith, <em>The Affluent Society</em> (1958), ch.11 "The Dependence Effect": <a href="https://en.wikipedia.org/wiki/The_Affluent_Society" target="_blank" rel="noopener noreferrer">en.wikipedia.org</a> · <a href="http://digamo.free.fr/afflu58.pdf" target="_blank" rel="noopener noreferrer">excerpt</a>. As-of 1958.</li><li>&gt; The recommendation-share figures (Netflix, YouTube, Amazon) are values as disclosed in 2013–2018; the platform-produced ones (Netflix, YouTube) are interested sources. The text uses them only as evidence of direction, not as current precise figures, and the claims about desire-formation stay within the "incentive/tendency" bound of the academic result (ICML 2022).</li><li>---</li><li><em>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</em></li><li>&lt;/content&gt;</li></ol></section></article>]]></content:encoded></item>
<item><title>Why Omakase Collapsed — It Sold a Signal, Not Fish</title><link>https://refract.blog/en/posts/%EC%98%A4%EB%A7%88%EC%B9%B4%EC%84%B8-%EA%B2%BD%EC%A0%9C%ED%95%99/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EC%98%A4%EB%A7%88%EC%B9%B4%EC%84%B8-%EA%B2%BD%EC%A0%9C%ED%95%99/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Culture</category><description>The counter they once called a "reservation war" sits empty. The same counter that, just three years ago, sold out for every anniversary. Naver DataLab's search…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#d98326"></span><span class="kx">Culture</span><span class="ksep">·</span><span class="kx">음식</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-27T15:42:45"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><h1 class="title">Why Omakase Collapsed — It Sold a Signal, Not Fish</h1><div class="body"><p class="lead">The counter they once called a "reservation war" sits empty. The same counter that, just three years ago, sold out for every anniversary. Naver DataLab's search-interest index for "omakase" has fallen roughly 85%, from a January 2023 peak of 100 to 15 in May 2026—below even its pre-COVID level of 20 in May 2019. On the booking platform CatchTable, "Japanese omakase," the top dining reservation in 2023–2024, dropped out of the rankings last year. Over the same span, 2,593 Japanese restaurants—omakase among them—closed (against 1,821 Chinese and 624 cafés). Raw closure counts don't measure the size of a collapse on their own, since each category draws from a different base. But search, bookings, and closures all point the same way.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">Price Was the Function</a><a class="jump" href="#sec-2">The Trap of Low-Capital Entry</a><a class="jump" href="#sec-3">The Signal Breaks Before the Taste</a><a class="jump" href="#sec-4">The Same Hand Went to the Buffet</a></nav><p>So the question to ask is not "why was it so expensive." Expensive food has always existed. The real question is <strong>why it collapsed this fast</strong>. To explain the speed, start by looking again at what was actually being traded at the counter.</p><blockquote><p><strong>Boom and bust sit on one curve</strong></p><div class="tablewrap"><table><thead><tr><th>Metric</th><th>Boom (peak)</th><th>Bust (now)</th></tr></thead><tbody><tr><td>"Omakase" search-interest index</td><td><span class="num">100</span> (Jan <span class="num">2023</span>)</td><td><span class="num">15</span> (May <span class="num">2026</span>) · <strong>-85%</strong></td></tr><tr><td>Press coverage</td><td>~100s of articles (<span class="num">2019</span>) → <strong>400s (<span class="num">2022</span>)</strong></td><td>—</td></tr><tr><td>CatchTable dining reservations</td><td><strong>#<span class="num">1</span></strong> (<span class="num">2023–24</span>)</td><td>Out of the rankings (<span class="num">2025</span>)</td></tr><tr><td>Japanese-restaurant closures (cumulative)</td><td>—</td><td><strong><span class="num">2,593</span></strong> (<span class="num">2023</span>–May <span class="num">2026</span>)</td></tr></tbody></table></div><p><em>Sources: Naver DataLab · BigKinds · CatchTable · Ministry of the Interior and Safety (as-of Jan <span class="num">2023</span>–May <span class="num">2026</span>)</em></p></blockquote><h2 id="sec-1">Price Was the Function</h2><p>Omakase was more than food from the start. The counter in front of the chef bundles seating into a small number, manufacturing artificial scarcity, and a dinner in the ₩<span class="num">200,000</span> range becomes an entry signal—not everyone can come. And the experience was completed in a photograph. By September <span class="num">2022</span>, Instagram posts tagged "omakase" topped <span class="num">530,000</span>, and search interest had doubled over the two years from August <span class="num">2020</span>.</p><p>Economics has a name for a good like this. A <strong>positional good</strong>—one whose value comes not from utility but from others not having it—a good that signals status. (There's no data to call it a Veblen good outright—a good whose demand rises as its price does. But its positional, status-display function is clear.) One real-estate YouTuber called the craze "an inflation of bravado," and a doctor on Blind drew controversy by setting "monthly take-home pay of at least ₩<span class="num">4</span> million" as the bar for who deserved to come. The uproar itself is evidence that omakase was being consumed as a status signal, not as food. Nobody asks for an income bracket to eat gimbap.</p><p>For a positional good, the higher the price, the sharper the signal. It has to be expensive to signal at all. So omakase spread by swapping formats—from sushi to Korean beef (umakase), dessert, coffee. What sold was the picture of "me, seated at the counter"; the ingredient could be anything.</p><h2 id="sec-2">The Trap of Low-Capital Entry</h2><p>When the signal sold well, supply followed. By SBS's analysis, omakase's business structure opened entry unusually wide. Counter-only seating keeps the store small and labor costs down; reservation deposits hedge no-show and inventory risk in advance. On the capital side, it was a low-barrier model for young founders. The real barrier, of course, is not capital but the chef's skill. But that skill threshold dropped too, and copycat shops multiplied fast.</p><p>Easy entry swelled the numbers. Coverage exploded from the ~100s of articles in <span class="num">2019</span> to the 400s in <span class="num">2022</span>, and by one count omakase venues reached <span class="num">403</span> (<span class="num">216</span> in Seoul). Around <span class="num">2020</span>, search interest for "omakase" overtook "buffet."</p><p>Here the status good undoes itself. <strong>A signal's value comes from scarcity—but once it pays, everyone piles in and it turns common.</strong> The moment a counter opens in every neighborhood and the Instagram feed is papered with the same photo, the premise—that others can't have it—breaks. If everyone has it, the signal value goes to zero. A status good that social media grew was killed by being made common—by low-capital entry and a glut of low-skill imitators together. So the <span class="num">2,593</span> closures are not a failure of taste alone. They look closer to an <strong>inflation of scarcity</strong>—a flood of low-skill copies eroding average quality and signal value at once.</p><h2 id="sec-3">The Signal Breaks Before the Taste</h2><p>Onto a signal already gone common, the macroeconomy bore down. In May <span class="num">2026</span> the Consumer Price Index stood at <span class="num">119.92</span>, up <span class="num">3.1%</span> year on year, and the cost-of-living index—closer to felt prices—jumped <span class="num">3.3%</span>, its largest rise in <span class="num">25</span> months. But a +<span class="num">3.1%</span> shock alone can't explain an <span class="num">85%</span> collapse. The macro reads less as a trigger than as a <strong>trailing pressure</strong> that delivered the final cut to a signal that had been losing its scarcity since <span class="num">2023</span>. On the timeline: oversupply in <span class="num">2022–23</span> eroded signal value, the heat cooled in <span class="num">2024–25</span>, and prices in <span class="num">2026</span> cleared out what demand remained.</p><p>There is a competing hypothesis. A supply-cost account: the yen's reversal from its lows, rising costs for imported fresh fish, the minimum wage, and rent struck small counters with heavy fixed costs. Margin compression was likely an independent driver of the closures. But costs have outlets—pass-through to prices, adjusting the average check—and demand itself evaporated first all the same. The collapse of signal value is the better primary driver; costs are better read as a secondary pressure layered on top.</p><p>One could object that expensive luxuries naturally fall first in a downturn. True. But omakase was not a small luxury—not "lipstick." The lipstick effect describes people who can no longer afford a big luxury shifting to a cheaper substitute one. A ₩<span class="num">250,000</span> dinner is not that substitute—it is the body being substituted away from. Utility spending (a meal) can't be cut; signal spending (display) is the first thing that can. As Professor Jeong Yeon-seung diagnoses it, consumers began routing money first to other activities or to building assets, rather than premium dining.</p><p>Which leaves one proposition. <strong>A status good that has gone common and lost its scarcity is not a defensive good but the first to break under a shock.</strong> Not every status good, though. True luxury with a hard barrier to entry—luxury brands, Michelin, members-only golf—holds or even rises in a downturn. What falls is the "mass premium" (masstige) the middle class overreached to buy—the aspirational good that has already lost its moat. Omakase was precisely the latter. A single line of falling search interest can't establish a "collapse" on its own; a mature trend can hold its consumption even as search fades. But because reservation rankings and closures broke together, it reads as a collapse. It wasn't taste alone that ended omakase. The wallet that paid for the signal closed first.</p><h2 id="sec-4">The Same Hand Went to the Buffet</h2><p>That closed wallet didn't vanish; it moved. While omakase fell, mid- and low-price buffets caught the rebound.</p><blockquote><p><strong>The buffet fills the seat omakase vacated</strong></p><div class="tablewrap"><table><thead><tr><th>Category</th><th>Omakase</th><th>Mid/low-price buffet</th></tr></thead><tbody><tr><td>Average check</td><td>Lunch ₩<span class="num">100,000–130,000</span> / Dinner ₩<span class="num">200,000–250,000</span></td><td>₩<span class="num">10,000–50,000</span> range</td></tr><tr><td>Trajectory</td><td><span class="num">2,593</span> closures · reservations #<span class="num">1</span> → out</td><td>Ashley Queens <span class="num">122</span> locations · <strong>₩500B revenue</strong> · target <span class="num">150</span> / VIPS <span class="num">25</span>→<span class="num">35</span></td></tr></tbody></table></div><p><em>Sources: Ministry of the Interior and Safety · CatchTable · E-Land Eats · CJ Foodville (as-of <span class="num">2025</span>–Jun <span class="num">2026</span>)</em></p></blockquote><p>Ashley Queens pulled in roughly ₩<span class="num">500</span> billion in revenue across <span class="num">122</span> locations last year and plans to grow to <span class="num">150</span> by <span class="num">2026</span>; VIPS, long in retreat, has expanded again from <span class="num">25</span> in <span class="num">2022</span> to <span class="num">35</span>.</p><p>Read this polarization as "two separate groups—one that quit the high end, one chasing value"—and you've seen only half. The pattern the aggregates suggest looks less like two groups splitting than like one wallet reordering its priorities. Koreans in their 20s and 30s, running thrift hacks and small luxuries at once, closed only the signal spending first under the macro shock and kept the utility spending. With no individual-level tracking data this is inference, not assertion—but the hand that quit omakase likely picked up the buffet plate.</p><p>Nor was the collapse total. If the hypothesis holds, the genuinely scarce top-tier counters survived; only the common middle died. The death of a signal sorts by tier.</p><p>Why Koreans in their 20s and 30s chose a dining counter, of all places, to confirm their standing isn't fully explained by economics. The critic Kim Heon-sik reads omakase as an "outlet for filling a void" in Korean dining culture—a two-way experience traded between chef and guest. This psychological hunger underlay why the stage for the signal was a narrow counter in particular—and so, when the signal cooled, the stage emptied fast too.</p><p>So omakase's obituary doesn't read as a food story alone. It is a record between the period when the signal beat utility and the period when utility beat the signal back. And if you operate or invest in premium, there's one thing to take from this. In a market built on signal, the <strong>speed of going common</strong> is itself the risk indicator. Whether the next signal good after the counter is running shoes or whisky, how fast it turns common is that market's remaining lifespan.</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li>Search interest (Naver DataLab) · Japanese-restaurant closures (Ministry of the Interior and Safety) · CPI/cost-of-living (Statistics Korea) — Asia Economy (2026-06-08), https://www.asiae.co.kr/en/article/economic-general/2026060810345158842 · Herald Economy, https://biz.heraldcorp.com/article/10768000 (as-of 2026.5)</li><li>CatchTable reservation rankings · mid/low-price buffets (Ashley Queens · VIPS) — Daum (2026-06-07), https://v.daum.net/v/20260607100152086 (as-of 2026.6)</li><li>Omakase coverage volume · venue count · business structure · conspicuous-consumption controversy — SBS, https://news.sbs.co.kr/news/endPage.do?news_id=N1007035301 (as-of 2023)</li><li>Omakase price-tier survey — ValueChampion, https://brunch.co.kr/@valuechampion/237 (as-of 2021)</li><li>Instagram posts · format proliferation — Seoul Economic Daily, https://www.sedaily.com/NewsView/26AXYPC52V (as-of 2022.9)</li><li>Japanese-restaurant closure comparison — Insight, https://www.insight.co.kr/news/557560 (as-of 2026.5)</li></ol></section><footer class="byline"><span class="ai-dot"></span><span>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</span></footer></article>]]></content:encoded></item>
<item><title>Friday Disappeared. The Work Didn't.</title><link>https://refract.blog/en/posts/%EC%A3%BC4%EC%9D%BC%EC%A0%9C-%EC%8B%A4%ED%97%98/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EC%A3%BC4%EC%9D%BC%EC%A0%9C-%EC%8B%A4%ED%97%98/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Etc</category><description>For a long time I believed time and work were a single body. The longer I sat at the desk, the more I believed I had done; even the dull listlessness of a late…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#6b7280"></span><span class="kx">Etc</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-27T16:31:17"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><div class="vcaveat"><span class="vc-l">Note</span><span>돌봄·젠더 차원(f7 가사/돌봄 분담) 미사용 — 비차단 nit</span></div><h1 class="title">Friday Disappeared. The Work Didn't.</h1><div class="body"><p class="lead">For a long time I believed time and work were a single body. The longer I sat at the desk, the more I believed I had done; even the dull listlessness of a late Friday afternoon I held onto as proof of diligence. So cutting five days to four would shave output by the same measure—that seemed obvious. Then several countries actually erased a day, and what broke was the equation.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">Cut It, and Nothing Broke</a><a class="jump" href="#sec-2">Read It One Way and You're Wrong</a><a class="jump" href="#sec-3">That Day Was Measurement, Not Work</a><a class="jump" href="#sec-4">Not a Novelty—a Curve That Stalled</a><a class="jump" href="#sec-5">Where Did the Vanished Time Go?</a></nav><h2 id="sec-1">Cut It, and Nothing Broke</h2><p>In the second half of <span class="num">2022</span>, in the United Kingdom, <span class="num">61</span> firms and roughly <span class="num">2,900</span> people held wages flat and cut working hours to four-fifths. The worry that revenue would fall came to nothing: six months on, revenue rose an average of <span class="num">1.4%</span> on a size-weighted basis and effectively held its ground. There are earlier cases. Since <span class="num">2015</span> Iceland had put the same question to some <span class="num">2,500</span> public-sector workers, and productivity and services held or even improved. The study that looked furthest ran last summer in the journal Nature Human Behaviour. Tracking <span class="num">2,896</span> people across <span class="num">141</span> organizations in six countries, it recorded that burnout, job satisfaction, and mental and physical health all improved—a change absent from the control firms that kept working the same hours. Even among the leaders, the people who hand out the work, nearly half reported productivity unchanged in their own accounts, and one in three said it had actually risen.</p><blockquote><p><strong>The UK four-day pilot — what was cut and what wasn't</strong> (<span class="num">61</span> firms · ~<span class="num">2,900</span> people, second half of <span class="num">2022</span>, <span class="num">6</span> months) · Hours −<span class="num">20%</span> (wages held at <span class="num">100%</span>) · Revenue +<span class="num">1.4%</span> (size-weighted, essentially flat) · Sick days −<span class="num">65%</span> · Reported lower burnout <span class="num">71%</span> · Turnover −<span class="num">57%</span> (year-over-year) · At close, <span class="num">92%</span> (<span class="num">56</span>/<span class="num">61</span> firms) decided to keep the four-day week</p><p><em>Source: Autonomy · <span class="num">4</span> Day Week Global, "UK Four-Day Week Pilot Results" (published <span class="num">2023-02</span>). As-of <span class="num">2023-02</span>.</em></p></blockquote><p>Once, and I would have written it off as chance. But when the same picture is drawn again and again across different continents and different industries, the thing to doubt is not the experiment—it is my premise.</p><h2 id="sec-2">Read It One Way and You're Wrong</h2><p>Still, to an eye that has watched the labor market for thirty years, the picture is not so clean. These firms did not simply lop off a day. Before they cut the hours came a reorganization—meetings culled, the way of working redrawn—and the participants were mostly small, self-selected, English-speaking firms that had raised their own hands. This is the result of an actively designed intervention on a self-selected sample. So you cannot read the preservation of output along a single line. They may have packed the same work more tightly into the remaining four days; it may be a novelty effect, briefly lifted by the awareness of being watched. To jump from "fine even when cut" to "rest makes the work go better" is to invent a causation the data does not hold. The direction of cause—that recovery lifted output—is fixed nowhere in this data.</p><p>And yet one thing remains. If a day could be removed without output collapsing, then in these firms, at least, the cord between hours logged at the desk and the value produced was not as taut as I had believed. Where that slack came from is, in fact, the experiment's real question.</p><h2 id="sec-3">That Day Was Measurement, Not Work</h2><p>Economics has an old joke. In <span class="num">1987</span> Robert Solow wrote that you can see the computer age everywhere but in the productivity statistics. It was the lament of an era when computers were going into every factory and office while measured productivity would not budge. The paradox was not a problem of technology. It was a problem of the ruler. When something is made but does not register on the books, we count the time put in instead of the result produced. When output is invisible, working hours stand in for it.</p><p>Knowledge work sits exactly there. There is no clean way to convert into hours the value of a single proposal, a block of code, one act of persuasion, so we have settled for the length of time at the desk as its substitute. What the four-day experiment actually shook was this substitution. To say output held even with a day removed is close to saying that some share of the missing day was, from the start, a stand-in for output—the time of meetings that drag on, of afternoons let slip waiting for a reply, the posture of waiting for work to happen. That the firms culled meetings first, before the trial, is the mark of that waiting-time cut out by hand.</p><p>So the weight of the question is not how many days you work. Does my fifth day produce output, or stop at the posture of waiting for that output? In work driven by deadlines, work that faces people directly, work where someone has to hold the post, the fifth day plainly makes something. The cord went slack precisely where output had slipped past the eye of measurement.</p><h2 id="sec-4">Not a Novelty—a Curve That Stalled</h2><p>Seen over the long run, this is not even a new event. Annual working hours in the industrial nations were nearly halved—from over <span class="num">3,000</span> in the late nineteenth century to around <span class="num">1,800</span> by the end of the twentieth. The five-day, forty-hour week we now enjoy is itself the product of a century of shortening. But that curve stopped somewhere in the 1970s. Productivity kept climbing afterward; only the falling hours stopped.</p><p>Keynes had already seen the next step in <span class="num">1930</span>. A hundred years on, he wrote, living standards in the advanced economies would be four to eight times higher, and people would work just fifteen hours a week. The forecast about living standards proved remarkably accurate. What missed was the time. We reached the abundance Keynes promised and never went toward the leisure he promised with it. The four-day experiment is therefore less an invention of the future than a belated question: can we push again at a curve that stalled half a century ago?</p><h2 id="sec-5">Where Did the Vanished Time Go?</h2><p>Where the erased day went was recovery. In the same UK trial, sick days fell <span class="num">65%</span>, seven in ten said their burnout had eased, and the number of people who left the company was <span class="num">57%</span> lower than in the same period the year before. The Nature study went a step further: the more hours an individual cut—especially those who cut more than eight hours a week—the larger the improvement.</p><p>These figures do not prove recovery to be the fuel of output. But the mere fact that recovery and the holding of output happened side by side unsettles the assumption that has set them against each other. We tend to place rest across from work and to reckon that we surrender something in proportion to how much of it we take. Yet output wrung out of people carries an invisible invoice, and that invoice arrives much later under the names of sick leave, turnover, and burnout. Give the day back, and the invoice thinned. Whether it truly vanished, though, or merely moved—from the individual's health to the company's books, and on to society's medical bills—remains to be seen.</p><p>When the experiment ended, <span class="num">92%</span> of the UK firms chose to carry on with the four-day week. That is a figure drawn only from the firms that ran to the finish, and if wages are unchanged, few will refuse an extra day off—so it cannot be entered as decisive evidence. Still, the fact remains that people who had once won their time back rarely went back to the old place.</p><p>This question is no longer only a matter for distant countries. In <span class="num">2025</span> the Korean government, too, staked <span class="num">27.6</span> billion won on a <span class="num">4.5</span>-day-week pilot, deciding to give each worker at a participating workplace between <span class="num">200,000</span> and <span class="num">600,000</span> won a month. According to reporting on the pilot's results, the average weekly working hours at participating workplaces fell from <span class="num">39.12</span> to <span class="num">34.48</span>—not a full day, but a little over half of one. There is no quantitative answer on output yet, but we, too, have begun to ask what to call that time.</p><p>So I find myself asking. That day, the one that could be cut without collapse—what had I been counting it as all along? Output, or a stand-in for output? Picturing the empty Friday desk, I still do not know the whole answer. But I think I have watched time and work—which I had so long taken to be a single body—quietly let go of each other's hands, in the place beyond the eye of measurement.</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li>UK four-day pilot results — Autonomy · 4 Day Week Global, "UK Four-Day Week Pilot Results" (revenue, sick days, burnout, turnover, retention; as-of 2023-02): <a href="https://autonomy.work/portfolio/uk4dwpilotresults/" target="_blank" rel="noopener noreferrer">autonomy.work</a> · <a href="https://www.4dayweek.com/uk-pilot-results" target="_blank" rel="noopener noreferrer">4dayweek.com</a></li><li>Six-country multinational trial (burnout, health, productivity, sample limits) — Fan, Schor et al., <em>Nature Human Behaviour</em> (2025-07): <a href="https://www.nature.com/articles/s41562-025-02259-6" target="_blank" rel="noopener noreferrer">nature.com</a> · via <a href="https://www.newsweek.com/four-day-workweek-boosts-well-being-mental-physical-health-2101639" target="_blank" rel="noopener noreferrer">Newsweek</a></li><li>Iceland public-sector pilot (2015–2019) — Autonomy (as-of 2021): <a href="https://autonomy.work/portfolio/icelandsww/" target="_blank" rel="noopener noreferrer">autonomy.work</a></li><li>Korea 4.5-day-week pilot budget and support — Ministry of Employment and Labor / Korea Policy Briefing (2025): <a href="https://www.korea.kr/news/policyNewsView.do?newsId=148956270" target="_blank" rel="noopener noreferrer">korea.kr</a> · working-hour change reporting <a href="https://www.koreanewstoday.co.kr/news/articleView.html?idxno=80652" target="_blank" rel="noopener noreferrer">koreanewstoday.co.kr</a></li><li>Keynes's 1930 forecast (15-hour week; living standards 4–8×) — J.M. Keynes, "Economic Possibilities for our Grandchildren" (1930): <a href="https://www.marxists.org/reference/subject/economics/keynes/1930/our-grandchildren.htm" target="_blank" rel="noopener noreferrer">original</a> · reappraisal <a href="https://www.bls.gov/opub/mlr/2024/beyond-bls/a-reappraisal-of-keyness-economic-possibilities-for-our-grandchildren.htm" target="_blank" rel="noopener noreferrer">BLS <em>Monthly Labor Review</em> (2024)</a></li><li>Century-long working-hours trend (~3,000h→1,800h, 1970s stagnation) — Huberman &amp; Minns (2007), via <a href="https://en.wikipedia.org/wiki/Working_time" target="_blank" rel="noopener noreferrer">Working time, Wikipedia</a></li><li>Solow productivity paradox (1987) — Robert Solow, <em>The New York Review of Books</em> (1987-07-12), commentary <a href="https://www.brookings.edu/articles/the-solow-productivity-paradox-what-do-computers-do-to-productivity/" target="_blank" rel="noopener noreferrer">Brookings</a></li></ol></section><footer class="byline"><span class="ai-dot"></span><span>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</span></footer></article>]]></content:encoded></item>
<item><title>AI Agents and the Accountability Gap: the Work Is Delegated, the Respondent Is Not</title><link>https://refract.blog/en/posts/ai%EC%97%90%EC%9D%B4%EC%A0%84%ED%8A%B8-%EC%9C%84%EC%9E%84/</link><guid isPermaLink="true">https://refract.blog/en/posts/ai%EC%97%90%EC%9D%B4%EC%A0%84%ED%8A%B8-%EC%9C%84%EC%9E%84/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Technology</category><description>A passenger asked Air Canada's website chatbot about a bereavement fare. The chatbot said the discount could be claimed retroactively, after the ticket was boug…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#1f9e8a"></span><span class="kx">Technology</span><span class="ksep">·</span><span class="kx">AI</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-28T00:23:08"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><div class="vcaveat"><span class="vc-l">Note</span><span>제도 앵커를 EU/캐나다(AI Act·PLD·AILD·Air Canada)로 한정 — 미국 respondeat superior 디테일·실현 책임소송 base rate는 범위 외(비차단). prism 통합이 섹션 순차라 직조 여지(비차단 nit).</span></div><h1 class="title">AI Agents and the Accountability Gap: the Work Is Delegated, the Respondent Is Not</h1><div class="body"><p class="lead">A passenger asked Air Canada's website chatbot about a bereavement fare. The chatbot said the discount could be claimed retroactively, after the ticket was bought; that was not the actual policy. The passenger relied on it, bought the ticket, and lost the difference. In the dispute, Air Canada made a remarkable argument—that the chatbot was "a separate legal entity that is responsible for its own actions." In February 2024, the British Columbia Civil Resolution Tribunal called this "a remarkable submission," dismissed it, and ordered the airline to pay. That chatbot only spoke. The next generation does not stop at speaking.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">Agents Act—and Get It Wrong Often</a><a class="jump" href="#sec-2">Responsibility Does Not Vanish—It Relocates</a><a class="jump" href="#sec-3">The Upside Is Delegated, the Downside Externalized</a><a class="jump" href="#sec-4">Where, Then, Does the Respondent Remain</a></nav><p>An AI agent is an LLM-based system that chooses its own tools and moves in a loop on feedback from its environment. It does not stop at generating text—it sends emails, buys things, runs code, operates software. It acts, rather than advises. The question posed by <a class="wikilink" href="https://refract.blog/en/posts/llm-%EA%B3%A0%EC%B0%B0/">its sibling piece on understanding</a> was "what corrects this model?" The moment the model stops at drafting and starts acting, the question shifts one notch. When it gets something wrong, who answers?</p><h2 id="sec-1">Agents Act—and Get It Wrong Often</h2><p>One thing first. It is true that agents are faster than people and, on some tasks, more consistent; people tire, forget, and look away, and machines do not. But accuracy is not the issue here. The issue survives conceding accuracy: who is responsible when it goes wrong. Low reliability only sets the timing of that question. The more often an agent errs, the more often the accident with no one to answer for it becomes real.</p><p>And agents get it wrong often. Start with reliability. On the agent benchmark τ-bench, even the best agent succeeds on all eight repeated attempts of the same task (pass^<span class="num">8</span>) only about <span class="num">25%</span> of the time—nearly <span class="num">60%</span> below its single-attempt rate, meaning the same instruction yields uneven results. Across both domains, even the single-attempt rate stays under <span class="num">50%</span>. Longer tasks get worse: by METR's measurements, the "time horizon" of tasks an agent finishes with <span class="num">50%</span> reliability is still short, and success drops steeply as tasks run longer (though that horizon is climbing fast). On TheAgentCompany, a Carnegie Mellon benchmark of <span class="num">175</span> real office tasks, the best model finished only about <span class="num">30%</span> of them fully autonomously, with no human intervention (per the September <span class="num">2025</span> leaderboard; <span class="num">24%</span> in the original December <span class="num">2024</span> paper).</p><p>These are not the numbers for a production agent fenced in by guardrails on a narrow job—they are the numbers for handing an open-ended professional task wholesale to autonomy. And autonomy is exactly what the market is now selling. Hand it an open task and even the best model finishes one in three. Yet delegation is spreading fast. Gartner forecasts that by <span class="num">2028</span>, <span class="num">33%</span> of enterprise software will embed agentic AI (up from under <span class="num">1%</span> in <span class="num">2024</span>), and that at least <span class="num">15%</span> of day-to-day work decisions will be made autonomously through it. The move to hand real decisions to an unreliable actor has already begun.</p><div class="tablewrap"><table><thead><tr><th>Measure</th><th>Result</th><th>Source · As-of</th></tr></thead><tbody><tr><td>τ-bench, best agent retail pass^<span class="num">8</span> (repeat consistency)</td><td>~<span class="num">25%</span> (≈<span class="num">60%</span> below single-attempt)</td><td>arXiv <span class="num">2406.12045</span>, <span class="num">2024-06</span></td></tr><tr><td>TheAgentCompany, best model fully autonomous completion</td><td>~<span class="num">30%</span> (<span class="num">175</span> real tasks; <span class="num">24%</span> in original paper)</td><td>CMU, <span class="num">2025-09</span></td></tr><tr><td>Enterprise software embedding agentic AI (Gartner forecast)</td><td><span class="num">33%</span> by <span class="num">2028</span> (from &lt;<span class="num">1%</span> in <span class="num">2024</span>)</td><td>Gartner, <span class="num">2025-06</span></td></tr></tbody></table></div><p><em>Table: Agent reliability and adoption. Sources—τ-bench (Sierra · Princeton), TheAgentCompany (CMU, arXiv <span class="num">2412.14161</span>), Gartner forecast. As-of <span class="num">2024-06</span> to <span class="num">2025-09</span>.</em></p><h2 id="sec-2">Responsibility Does Not Vanish—It Relocates</h2><p>Say there is an accident. The agent executes a wrong refund, or invents a policy and promises it to a customer. Responsibility sits among four candidates: the user who ran it, the company that deployed it, the provider that built the model, and the agent itself.</p><p>Cross off the last candidate first. An agent has no legal personhood. It cannot hold assets, enter contracts, or be sued—it is, in law, incapable of bearing responsibility. The philosopher Andreas Matthias named this the "responsibility gap" back in <span class="num">2004</span>: with self-learning autonomous machines, a structure arises in which neither manufacturer nor operator can fairly be held responsible for the machine's actions. The attempt to push responsibility onto the agent itself reached a courtroom once—that was Air Canada's submission above. It was a small-claims matter, about CAD <span class="num">$650</span>, a non-binding decision of an online civil-resolution tribunal; but the principle is general. A company answers for the words and actions of the tool it puts out to face its customers. This is no different from the old doctrine that a principal answers for what it had its agent do.</p><p>Among the remaining three, responsibility then forks into two channels that run in opposite directions. One channel collects at the party that faced the customer—the deployer (where Air Canada stood). The provider exits this channel by contract. Anthropic's consumer terms, for instance, provide outputs and actions "as is," disclaim any warranty of accuracy, and state that the user must not rely on outputs without independently confirming them, nor use them as the sole basis for high-stakes decisions such as financial ones. It is standard industry boilerplate. (Enterprise contracts, though, are negotiated, and their indemnity clauses can run the other way, back upstream.) So in the default case of a consumer or a small deployer, responsibility flows down the contract to the deployer.</p><p>The other channel runs back upstream. The revised EU Product Liability Directive explicitly brings software and AI within "product," places liability for a defect on the manufacturer—the party that built the model—and even eases the victim's burden of proof (disclosure of evidence, presumptions of defectiveness and causation). It is a structure that hauls the responsibility a disclaimer pushed downstream back up to the provider. The two channels run in exactly opposite directions.</p><p>No rule yet settles the crossing. The EU AI Act does split obligations between "provider" and "deployer," but that is an allocation of regulatory duties—conformity, transparency—not an allocation of civil liability for who compensates the victim. The attempt to tailor that civil channel to AI, the EU AI Liability Directive, was withdrawn in <span class="num">2025</span> for "no foreseeable agreement." And the Product Liability Directive does not apply until December <span class="num">2026</span>. The delegation is happening now; the bill on the upstream channel arrives late.</p><div class="tablewrap"><table><thead><tr><th>Candidate respondent</th><th>Bears it?</th><th>Why</th></tr></thead><tbody><tr><td>The agent itself</td><td>Cannot</td><td>No legal personhood—cannot be sued or pay damages</td></tr><tr><td>The model provider</td><td>Two directions</td><td>Consumer terms disclaim (push downstream) / product liability summons it back upstream</td></tr><tr><td>The user</td><td>Partly</td><td>Terms and case law impose a duty to confirm independently</td></tr><tr><td>The deploying company</td><td>Front line, customer-facing</td><td>The party that faced customers with the tool—the general doctrine of vicarious liability</td></tr></tbody></table></div><p><em>Table: The two channels of responsibility. Sources—Matthias (<span class="num">2004</span>), Moffatt v. Air Canada (<span class="num">2024</span> BCCRT <span class="num">149</span>), revised EU Product Liability Directive (<span class="num">2024</span>/<span class="num">2853</span>), provider terms. As-of <span class="num">2004</span> to <span class="num">2026-03</span>.</em></p><h2 id="sec-3">The Upside Is Delegated, the Downside Externalized</h2><p>Why hand decisions to an unreliable actor at all? Here economics answers. An agent's value lies in taking the human out of the loop. The work runs without a person inspecting it step by step, so it is fast and cheap. Autonomy is the saving. The upside, productivity, goes to the company that deployed the tool.</p><p>The trouble is the downside. When an agent causes harm, the cost falls first on the counterparty to the bad transaction, or the customer who believed the misinformation. And the machinery to manage that cost is still thin. By one governance survey, fewer than half of organizations (under <span class="num">48%</span>) monitor their AI systems for accuracy, misuse, or drift. The figure covers AI systems in general, but applied to agents that act on their own, the implication is heavier: a fair number of autonomous systems run without anyone watching what went wrong, or when.</p><p>One clear signal that the cost is real is that a product to sell it has appeared. In April <span class="num">2025</span>, an AI liability insurance policy from Armilla, backed by an underwriter at Lloyd's, launched. It covers losses—and the legal costs that follow—when an AI fails to perform as intended or produces critical errors, hallucinations, or inaccuracies. The risk has begun to be priced into premiums. Separately, Gartner forecasts that more than <span class="num">40%</span> of agentic AI projects will be canceled by the end of <span class="num">2027</span>, on rising costs, unclear value, and inadequate risk controls. That is a signal distinct from the liability question, but it is evidence that the economics of delegation are already not frictionless.</p><p>From here on is interpretation, not fact. The value of delegation and the accountability gap are not two events but two faces of a single act. The cost delegation cuts is human attention and labor—and the person who would have answered, by name, when something went wrong was sitting in that very seat. One person held both roles, so cutting the human to save the cost cuts the respondent along with them. Responsibility, then, cannot simply be added back for free after the fact. Seating a person back into the answerable role carries a floor cost that cannot be driven to zero—because the whole appeal of full autonomy was driving that very cost toward zero.</p><h2 id="sec-4">Where, Then, Does the Respondent Remain</h2><p>This analysis does not end in the abstract; it returns to the desk of the professional and the firm adopting agents.</p><p>By elimination, the conclusion is plain. The provider exits by contract, the agent cannot answer in law, and so the body the law first looks to as the respondent for a customer-facing accident is the company that deployed the tool. Delegation feels like an act of offloading a burden, but the circuit of responsibility closes back toward the deployer. So "where to keep a person answerable" is not a problem an engineer solves with precision—it is a governance and legal decision. Just as in <a class="wikilink" href="https://refract.blog/en/posts/%EC%98%A8%EB%94%94%EB%B0%94%EC%9D%B4%EC%8A%A4-ai/">the adjacent piece on infrastructure</a>, where the line between what runs where left the engineer's hands and became a decision of cost, legal, and product, the line of responsibility moves to the same place.</p><p>Concretely, it means putting a named person's sign-off in front of actions that are irreversible or high-consequence—moving money, making external commitments, deleting data—and keeping a trail that records what was done and when. It is a design choice about where to cut the scope of autonomy and where to stand a person.</p><p>In <a class="wikilink" href="https://refract.blog/en/posts/llm-%EA%B3%A0%EC%B0%B0/">the sibling piece on understanding</a>, the reason a person had to stay in the loop was correction: where no ground-truth signal returns, someone had to check whether the output was right. With an acting agent, the reason a person must stay is one layer heavier. It is to answer. Even a perfectly accurate agent needs a respondent, because responsibility is not a question of who was right but of who stands, by name, before the harm when it goes wrong.</p><p>So it closes on the signature question. Who bears it, and when? Responsibility has not vanished. Erased once at the agent, slipping past the provider on the contract, it lands at the nearest seat the law can find—usually the deploying company. Where even that cannot be reached (a small operator, across a border, harm diffused), it stays with the victim, with no one to answer. The timing is out of joint too. Delegation spreads now; the bill is carried in later, by lawsuits and regulation—delayed further where the tailored rule was withdrawn.</p><p>In <a class="wikilink" href="https://refract.blog/en/posts/%EC%9E%90%EC%9C%A8%EB%AC%B4%EA%B8%B0-%EC%9C%84%EC%9E%84/">the piece on lethal delegation</a>, when the final decision to kill was handed to a machine, the name that should have stood before the death disappeared. In handing everyday work to an agent, the same shape returns. Only the scale differs; the structure is one. The act of handing over erases the one who would answer. An agent stands in for the work. It does not stand in for the seat where someone answers, by name, when the work goes wrong. Who keeps that seat is not a question of technology but of how responsibility is designed.</p></div><section class="sources"><div class="src-l">Sources</div><div class="tablewrap"><table><thead><tr><th>#</th><th>Outlet (via)</th><th>Primary source</th><th>Link</th><th>As-of</th></tr></thead><tbody><tr><td><span class="num">1</span></td><td>Anthropic Research</td><td>Anthropic, "Building Effective Agents" (agent definition)</td><td>https://www.anthropic.com/research/building-effective-agents</td><td><span class="num">2024-12</span></td></tr><tr><td><span class="num">2</span></td><td>arXiv</td><td>Sierra · Princeton, τ-bench (<span class="num">2406.12045</span>)</td><td>https://arxiv.org/abs/<span class="num">2406.12045</span></td><td><span class="num">2024-06</span></td></tr><tr><td><span class="num">3</span></td><td>METR</td><td>METR, "Measuring AI Ability to Complete Long Tasks"</td><td>https://metr.org/blog/<span class="num">2025-03</span>-19-measuring-ai-ability-to-complete-long-tasks/</td><td><span class="num">2025-03</span></td></tr><tr><td><span class="num">4</span></td><td>arXiv</td><td>CMU et al., TheAgentCompany (<span class="num">2412.14161</span>)</td><td>https://arxiv.org/abs/<span class="num">2412.14161</span></td><td><span class="num">2025-09</span></td></tr><tr><td><span class="num">5</span></td><td>MES Computing (via)</td><td>Gartner (agentic AI forecast)</td><td>https://www.gartner.com/en/newsroom/press-releases/<span class="num">2025-06</span>-25-gartner-predicts-over-40-percent-of-agentic-ai-projects-will-be-canceled-by-end-of-2027</td><td><span class="num">2025-06</span></td></tr><tr><td><span class="num">6</span></td><td>CanLII / McCarthy Tétrault</td><td>BC Civil Resolution Tribunal, Moffatt v. Air Canada (<span class="num">2024</span> BCCRT <span class="num">149</span>)</td><td>https://www.canlii.org/en/bc/bccrt/doc/<span class="num">2024</span>/2024bccrt149/2024bccrt149.html</td><td><span class="num">2024-02</span></td></tr><tr><td><span class="num">7</span></td><td>Springer (Ethics and Information Technology)</td><td>Andreas Matthias, "The responsibility gap"</td><td>https://doi.org/<span class="num">10.1007</span>/s10676-004-3422-1</td><td><span class="num">2004</span></td></tr><tr><td><span class="num">8</span></td><td>EUR-Lex</td><td>EU, AI Act (Regulation (EU) <span class="num">2024</span>/<span class="num">1689</span>)</td><td>https://eur-lex.europa.eu/eli/reg/<span class="num">2024</span>/<span class="num">1689</span>/oj/eng</td><td><span class="num">2024-06</span></td></tr><tr><td><span class="num">9</span></td><td>EUR-Lex</td><td>EU, revised Product Liability Directive (Directive (EU) <span class="num">2024</span>/<span class="num">2853</span>)</td><td>https://eur-lex.europa.eu/eli/dir/<span class="num">2024</span>/<span class="num">2853</span>/oj/eng</td><td><span class="num">2024-10</span></td></tr><tr><td><span class="num">10</span></td><td>EP Legislative Train / Bird &amp; Bird (via)</td><td>European Commission, AI Liability Directive (AILD) withdrawal</td><td>https://www.europarl.europa.eu/legislative-train/theme-a-europe-fit-for-the-digital-age/file-ai-liability-directive</td><td><span class="num">2025-10</span></td></tr><tr><td><span class="num">11</span></td><td>WCR.Legal</td><td>(legal commentary) AI has no legal personhood</td><td>https://wcr.legal/ai-liability-false-statements/</td><td><span class="num">2026-03</span></td></tr><tr><td><span class="num">12</span></td><td>Anthropic</td><td>Anthropic, Consumer Terms of Service</td><td>https://www.anthropic.com/legal/consumer-terms</td><td><span class="num">2025-10</span></td></tr><tr><td><span class="num">13</span></td><td>PR Newswire / Tech Monitor (via)</td><td>Armilla (underwritten at Lloyd's, Chaucer), AI liability insurance</td><td>https://www.prnewswire.com/news-releases/armilla-launches-affirmative-ai-liability-insurance-with-lloyds-underwriter-chaucer-302442586.html</td><td><span class="num">2025-04</span></td></tr><tr><td><span class="num">14</span></td><td>IoT For All (via)</td><td>Pacific AI / Gradient Flow, <span class="num">2025</span> AI Governance Survey</td><td>https://www.iotforall.com/news/<span class="num">2025</span>-ai-governance-survey-reveals-critical-gaps-between-ai-ambition-and-operational-readiness</td><td><span class="num">2025-06</span></td></tr></tbody></table></div><hr><p><em>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</em> &lt;/content&gt;</p></section></article>]]></content:encoded></item>
<item><title>Stop and the Weight Comes Back: GLP-1, and the Real Constraint the Shortage Hid</title><link>https://refract.blog/en/posts/glp1-%EA%B3%B5%EA%B8%89%EB%82%9C/</link><guid isPermaLink="true">https://refract.blog/en/posts/glp1-%EA%B3%B5%EA%B8%89%EB%82%9C/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Technology</category><description>Two years ago, Wegovy and Ozempic were drugs you couldn't fill at the pharmacy. The U.S. FDA placed some Wegovy doses on its shortage list in March 2022, and Oz…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#1f9e8a"></span><span class="kx">Technology</span><span class="ksep">·</span><span class="kx">바이오</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-27T16:35:10"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><div class="vcaveat"><span class="vc-l">Note</span><span>비차단 nit만 — H2 5개(내용요구)·IRA 약가협상 미언급(범위)·f23 Mercer 단일출처(귀속·非PIVOTAL). 발행 차단 아님.</span></div><h1 class="title">Stop and the Weight Comes Back: GLP-1, and the Real Constraint the Shortage Hid</h1><div class="body"><p class="lead">Two years ago, Wegovy and Ozempic were drugs you couldn't fill at the pharmacy. The U.S. FDA placed some Wegovy doses on its shortage list in March 2022, and Ozempic in August 2022. That shortage is over. And where it lifted, a more important fact surfaced: stop the drug and the weight comes back. In the STEP 1 extension trial, participants who came off semaglutide regained about two-thirds of the weight they had lost within a year. The shortage had been hiding the real constraint. What was bound was not output—it was demand.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">The Shortage Demand Made—and What It Hid</a><a class="jump" href="#sec-2">The Competition Moves Off Efficacy</a><a class="jump" href="#sec-3">The Market Has Already Ruled</a><a class="jump" href="#sec-4">A Drug That Outgrows Its Category</a><a class="jump" href="#sec-5">What Ended and What Remains</a></nav><p>GLP-1 is an incretin hormone the gut releases when you eat. A GLP-1 receptor agonist mimics that signal—it raises the pancreas's insulin secretion and suppresses glucagon to lower blood sugar, and at the same time acts on the brain's satiety center and slows gastric emptying to cut appetite and weight. Semaglutide (Ozempic, Wegovy) acts on the single GLP-1 receptor; tirzepatide (Mounjaro, Zepbound) acts on two, GIP and GLP-1. The effect lasts only while the drug is taken. Stop the signal and the appetite returns.</p><h2 id="sec-1">The Shortage Demand Made—and What It Hid</h2><p>The cause was simple. Demand outran capacity. After Wegovy was approved for weight management in June <span class="num">2021</span>, demand surged; Novo Nordisk said that as of May <span class="num">2024</span> roughly <span class="num">25,000</span> people a week were starting Wegovy in the United States—about five times the December <span class="num">2023</span> figure.</p><p>The shortage lifted across <span class="num">2024</span> and <span class="num">2025</span>. The FDA declared the tirzepatide injectable shortage resolved on <span class="num">19</span> December <span class="num">2024</span> and the semaglutide injectable shortage on <span class="num">21</span> February <span class="num">2025</span>. Over the same span Novo invested heavily in capacity—<span class="num">$6.5</span> billion in the United States in <span class="num">2025</span>, and <span class="num">$16.5</span> billion to acquire Catalent, the fill-finish contractor.</p><p>Resolution did not end in a return to normal. During the shortage, pharmacy compounding—legally copying a drug in short supply—at one point supplied roughly <span class="num">30%</span> of U.S. GLP-1 volume. That copying stood on a single exception: "shortage." When the shortage lifted, the legal basis vanished, and the FDA imposed deadlines to stop compounding semaglutide (<span class="num">22</span> April <span class="num">2025</span> for 503A pharmacies, <span class="num">22</span> May for 503B facilities). In September <span class="num">2025</span> it sent more than <span class="num">55</span> warning letters to online sellers, and telehealth players like Hims and Ro exited the compounded-semaglutide business. Novo claimed that in its own testing the impurities in some compounded injectables ran as high as <span class="num">86%</span>. The <span class="num">30%</span> shadow market the shortage had legalized became illegal the moment the shortage ended.</p><p>The shortage lifted; the demand does not. Because once you stop the drug, the effect is gone.</p><blockquote><p><strong>Stop, and it comes back</strong> · STEP <span class="num">1</span> extension trial: about <strong>two-thirds</strong> of lost weight regained within a year of stopping semaglutide · Cleveland Clinic real-world analysis (~<span class="num">8,000</span> patients): about <strong><span class="num">55%</span></strong> of obesity patients who stopped GLP-1 regained weight after a year; <span class="num">45%</span> maintained or lost more <em>Sources: STEP <span class="num">1</span> extension (Wilding <span class="num">2022</span>) · Cleveland Clinic (Diabetes Obes Metab, <span class="num">2026-03</span>) · limited to trial and real-world conditions</em></p></blockquote><p>The drug manages a chronic condition—obesity. It does not cure it. A patient who starts once keeps getting the prescription, and demand does not come down even when manufacturing catches up. The shortage was a passing symptom of that demand.</p><h2 id="sec-2">The Competition Moves Off Efficacy</h2><p>Once supply leveled out, the variables that distinguish the drugs multiplied. Efficacy became the price of entry. In SURMOUNT-5, the head-to-head trial, mean weight loss at <span class="num">72</span> weeks on the maximum tolerated dose was −<span class="num">20.2%</span> for tirzepatide and −<span class="num">13.7%</span> for semaglutide. Revenue followed the same order: in <span class="num">2025</span>, Lilly's Mounjaro and Zepbound combined are estimated at roughly <span class="num">$36</span> billion, Novo's semaglutide franchise at roughly <span class="num">$33</span> billion.</p><p>The new differentiators sit outside efficacy. Price comes first. Semaglutide's compound patent expired in Canada on <span class="num">4</span> January <span class="num">2026</span>—a G7 first—and in India, China, and Brazil in April <span class="num">2026</span>. In the United States, the United Kingdom, and much of Europe it stays protected through <span class="num">2031</span>. In India, where the patent has lapsed, more than <span class="num">40</span> drugmakers are preparing copies, and the monthly price has fallen from <span class="num">10,000–16,000</span> rupees for the brand to as little as about <span class="num">1,290</span> rupees. A month of the same molecule splits nearly tenfold by region.</p><p>The route split, too. On <span class="num">22</span> December <span class="num">2025</span> the FDA approved oral semaglutide—a Wegovy pill, <span class="num">25</span> mg once daily—for weight management. The first oral GLP-1 obesity drug, it showed mean weight loss of <span class="num">16.6%</span> under adherence in the OASIS <span class="num">4</span> trial. On <span class="num">1</span> April <span class="num">2026</span>, Lilly's orforglipron (Foundayo) was approved. A small-molecule oral rather than a peptide, it reached only about <span class="num">11%</span> mean loss at its top dose in trials—but it opened a path you swallow instead of inject.</p><p>The indications widened, too. In the SELECT trial (more than <span class="num">17,600</span> participants), overweight and obese patients with prior cardiovascular disease and no diabetes who took semaglutide <span class="num">2.4</span> mg cut their risk of major cardiovascular events by <span class="num">20%</span> (<span class="num">6.5%</span> versus <span class="num">8.0%</span>). The FDA approved the indication. The pool of eligible patients widened beyond obesity and diabetes.</p><h2 id="sec-3">The Market Has Already Ruled</h2><p>Whether the drug that leads on efficacy also takes the market is decided outside efficacy. The capital markets have already priced that split in.</p><div class="tablewrap"><table><thead><tr><th>Metric</th><th>Novo (semaglutide)</th><th>Lilly (tirzepatide)</th></tr></thead><tbody><tr><td>Head-to-head weight loss (SURMOUNT-5)</td><td>−<span class="num">13.7%</span></td><td>−<span class="num">20.2%</span></td></tr><tr><td>GLP-1 / obesity market share (<span class="num">2026-02</span>)</td><td>~<span class="num">40%</span></td><td>~<span class="num">60%</span></td></tr><tr><td><span class="num">2026</span> revenue guidance</td><td>First decline in modern history (−<span class="num">5</span> to −<span class="num">13%</span>)</td><td><span class="num">$80–83</span> billion (+<span class="num">25%</span>)</td></tr><tr><td>Market cap</td><td>−<span class="num">75%</span> vs <span class="num">2024-06</span> peak (below ~<span class="num">$160</span> billion)</td><td>—</td></tr></tbody></table></div><p><em>Sources: SURMOUNT-5 (NEJM) · Lilly and Novo <span class="num">2026</span> guidance · share and market cap per CNBC / securities analysis, as-of <span class="num">2025</span> to <span class="num">2026-02</span></em></p><p>This is the first mover's fall. Novo, once the most valuable company in Europe, has seen its market cap drop roughly <span class="num">75%</span> from its June <span class="num">2024</span> peak to below about <span class="num">$160</span> billion by February <span class="num">2026</span>. While Lilly guides to roughly <span class="num">25%</span> growth in <span class="num">2026</span>, Novo has warned of the first revenue decline in its modern history. CagriSema, the next-generation obesity drug Novo brought as its counter, missed the primary endpoint in its head-to-head against Zepbound (REDEFINE <span class="num">4</span>), and the stock fell about <span class="num">16%</span> more right after the readout. The company that built first ceded share to the company that takes off more weight (Lilly about <span class="num">60%</span> to Novo about <span class="num">40%</span>).</p><h2 id="sec-4">A Drug That Outgrows Its Category</h2><p>Demand you cannot quit pushes the obesity drug out past the pharmaceutical category. By Danske Bank's analysis, Novo alone accounted for about half of Denmark's GDP growth in <span class="num">2024</span>, and the company employed roughly <span class="num">30,000</span> people. When the company wobbled, pharmaceuticals' contribution to Denmark's merchandise export growth sank from <span class="num">8.1</span> percentage points in <span class="num">2024</span> to <span class="num">1.3</span> percentage points in <span class="num">2025</span>. One company's trial results move a nation's growth rate. (The same structure—one actor moving an entire system—shows up in the <a class="wikilink" href="https://refract.blog/en/posts/%EC%82%BC%EC%84%B1-%ED%95%98%EC%9D%B4%EB%8B%89%EC%8A%A4-%EC%BD%94%EC%8A%A4%ED%94%BC/">KOSPI</a>, where half the index is two companies.)</p><p>Consumption moves, too. Households using GLP-1 cut grocery spending by an average of <span class="num">5.3%</span> within six months of starting, and by more than <span class="num">8%</span> among high-income households. About <span class="num">23%</span> of U.S. households have a user, and the industry estimates GLP-1 will account for about <span class="num">35%</span> of food-and-beverage sales by <span class="num">2030</span>.</p><p>It reaches the reader along two lines. On the paying side, U.S. Medicare will open a temporary "GLP-1 Bridge" from July <span class="num">2026</span> through the end of <span class="num">2027</span>, supplying the drug to eligible beneficiaries at a <span class="num">$50</span> monthly copay. As of <span class="num">2025</span>, <span class="num">49%</span> of U.S. employer health plans at firms with <span class="num">500</span> or more workers covered GLP-1 for weight loss, and at firms above <span class="num">20,000</span> workers about two-thirds did. "Does my insurance cover it" has become a real variable. In Korea, Wegovy launched in October <span class="num">2024</span> as a non-reimbursed drug (in the <span class="num">500,000</span>-won-a-month range) and Mounjaro in August <span class="num">2025</span>, and Novo cut its supply price by up to <span class="num">40%</span>. In December <span class="num">2024</span> the Ministry of Health and Welfare banned remote prescribing and dispensing of obesity drugs.</p><h2 id="sec-5">What Ended and What Remains</h2><p>The shortage is over. What ended was the shortage, not the demand. As long as the weight comes back when you stop, demand will not come down even when the plants catch up. On top of that, the field is rearranging—price (generics), route (oral), payment (insurance), capital (Novo, Lilly). In <span class="num">2025</span>, about <span class="num">12%</span> of U.S. adults had already used a GLP-1. The question the shortage was hiding is now clear: not who takes off more weight, but who can carry that un-quittable demand more cheaply, in a form easier to swallow, propped up by insurance.</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li><strong>Weight regain after stopping the drug</strong> — STEP 1 extension trial (Wilding et al., <em>Diabetes, Obesity and Metabolism</em>, 2022) · Cleveland Clinic real-world analysis (<em>Diabetes, Obesity and Metabolism</em>, 2026-03). <a href="https://www.medcentral.com/endocrinology/obesity/weight-maintenance-after-glp-1-ra-withdrawal-exposes-critical-research-gaps" target="_blank" rel="noopener noreferrer">via medcentral</a> · <a href="https://newsroom.clevelandclinic.org/2026/03/12/what-happens-when-patients-stop-taking-glp-1-drugs-new-cleveland-clinic-study-reveals-real-world-insights" target="_blank" rel="noopener noreferrer">clevelandclinic</a></li><li><strong>FDA shortage-resolution rulings and compounding crackdown</strong> (2024-12 · 2025-02 · 2025-09) — <a href="https://www.fda.gov/media/185526/download" target="_blank" rel="noopener noreferrer">FDA</a> · <a href="https://www.foley.com/insights/publications/2025/02/glp-1-drugs-fda-removes-semaglutide-from-drug-shortage-list/" target="_blank" rel="noopener noreferrer">Foley</a> · <a href="https://kffhealthnews.org/health-industry/glp1-weight-loss-drugs-telehealth-oversight-regulation-compounded-semaglutide/" target="_blank" rel="noopener noreferrer">KFF Health News</a></li><li><strong>Novo capacity expansion and new prescriptions</strong> (2024-05 · 2025) — <a href="https://www.biopharmadive.com/news/novo-nordisk-semaglutide-shortage-doses-available-us/731510/" target="_blank" rel="noopener noreferrer">BioPharma Dive</a> · <a href="https://www.cnn.com/2024/05/02/health/wegovy-weight-loss-drug-new-prescriptions/index.html" target="_blank" rel="noopener noreferrer">CNN</a></li><li><strong>Head-to-head and indication trials</strong> — SURMOUNT-5 (<em>NEJM</em>, 2025) <a href="https://pubmed.ncbi.nlm.nih.gov/40353578/" target="_blank" rel="noopener noreferrer">PubMed</a> · SELECT MACE (<em>NEJM</em>, 2024) <a href="https://www.tctmd.com/news/fda-grants-mace-reduction-indication-semaglutide" target="_blank" rel="noopener noreferrer">TCTMD</a></li><li><strong>Oral-drug approvals</strong> — oral semaglutide (2025-12, <a href="https://www.ajmc.com/view/fda-approves-oral-semaglutide-as-first-glp-1-pill-for-weight-loss" target="_blank" rel="noopener noreferrer">AJMC</a>) · orforglipron / Foundayo (2026-04, <a href="https://www.prnewswire.com/news-releases/fda-approves-lillys-foundayo-orforglipron-the-only-glp-1-pill-for-weight-loss-that-can-be-taken-any-time-of-day-without-food-or-water-restrictions-302731485.html" target="_blank" rel="noopener noreferrer">PR Newswire / Lilly</a>)</li><li><strong>Patent cliff and India generics</strong> (2026) — <a href="https://www.labiotech.eu/in-depth/novo-nordisk-semaglutide-patent-expiration-canada/" target="_blank" rel="noopener noreferrer">Labiotech</a> · <a href="https://www.cnbc.com/2026/03/23/novo-nordisk-cheap-weight-loss-drugs-india-generic-ozempic-wegovy-semaglutide.html" target="_blank" rel="noopener noreferrer">CNBC</a></li><li><strong>Novo vs Lilly market</strong> (market cap · 2026 guidance · share · CagriSema, 2026-02) — <a href="https://www.cnbc.com/2026/02/04/eli-lilly-novo-nordisk-earnings-glp1-market.html" target="_blank" rel="noopener noreferrer">CNBC</a> · <a href="https://www.cnbc.com/2026/02/23/novo-nordisk-stock-cagrisema-trial-fails-weight-loss.html" target="_blank" rel="noopener noreferrer">CNBC</a></li><li><strong>Denmark economic contribution</strong> (Danske Bank analysis, 2024–2025) — <a href="https://www.cnbc.com/2025/11/20/weight-loss-drugmaker-novo-nordisk-helps-drive-denmarks-fastest-growth-in-years.html" target="_blank" rel="noopener noreferrer">CNBC</a> · <a href="https://fortune.com/europe/2024/09/03/half-of-denmarks-gdp-growth-in-2024-will-be-thanks-to-novo-nordisk-analysts-predict/" target="_blank" rel="noopener noreferrer">Fortune</a></li><li><strong>Consumption and food-spending ripple</strong> (2025) — <a href="https://www.grocerydive.com/news/glp1s-weight-loss-food-beverage-sales-2030/806424/" target="_blank" rel="noopener noreferrer">Grocery Dive</a> · <a href="https://www.foodbusinessnews.net/articles/29532-glp-1-users-cut-food-spending-by-53" target="_blank" rel="noopener noreferrer">Food Business News</a></li><li><strong>Payer coverage</strong> — Medicare GLP-1 Bridge (2026-07–2027-12, <a href="https://www.cms.gov/newsroom/press-releases/coming-soon-cms-provide-50-monthly-access-glp-1-medications-medicare-beneficiaries" target="_blank" rel="noopener noreferrer">CMS</a>) · employer coverage (Mercer 2025 National Survey of Employer-Sponsored Health Plans) · U.S. usage rate (2025, <a href="https://www.rand.org/news/press/2025/08/nearly-12-percent-of-americans-have-used-glp-1-weight.html" target="_blank" rel="noopener noreferrer">RAND</a>)</li><li><strong>Korea</strong> — Wegovy and Mounjaro launches, supply price, remote-prescribing ban (2024–2025) — <a href="https://m.dailypharm.com/News/318830" target="_blank" rel="noopener noreferrer">데일리팜</a> · <a href="https://biz.newdaily.co.kr/site/data/html/2024/09/30/2024093000140.html" target="_blank" rel="noopener noreferrer">뉴데일리</a></li></ol></section><footer class="byline"><span class="ai-dot"></span><span>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</span></footer></article>]]></content:encoded></item>
<item><title>A Machine That Has Never Seen a Board Knows the Board — Understanding, Mimicry, or the Wrong Question?</title><link>https://refract.blog/en/posts/llm-%EA%B3%A0%EC%B0%B0/</link><guid isPermaLink="true">https://refract.blog/en/posts/llm-%EA%B3%A0%EC%B0%B0/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Technology</category><description>There is a neural network that was never taught a single rule of Othello. It was fed nothing but sequences of legal moves — game records, the bare transcript of…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#1f9e8a"></span><span class="kx">Technology</span><span class="ksep">·</span><span class="kx">AI</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-27T19:11:59"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><div class="vcaveat"><span class="vc-l">Note</span><span>톤 override — 기술 노드 preset(정보형)은 explainer용. 본 글은 "LLM은 이해하는가 흉내내는가"라는 <em>고찰(examination·reflection)</em> 레지스터라 정보형으로는 깊이가 죽는다. 그래서 철학 에세이의 사색 골격(만연·우유·1인칭 절제)에 기술 칼럼의 데이터 단정(수치·논문 f#)을 얹은 혼합 톤으로 간다. 빌드업·잠언투 결론은 여전히 금지. 계승론(f12)은 닫는 <em>명시적 전망</em>으로만.</span></div><h1 class="title">A Machine That Has Never Seen a Board Knows the Board — Understanding, Mimicry, or the Wrong Question?</h1><div class="body"><p class="lead">There is a neural network that was never taught a single rule of Othello. It was fed nothing but sequences of legal moves — game records, the bare transcript of play — and trained to predict the next one. No one ever told it the board is 8×8, or that pieces flip. And yet open the model up and you find, grown inside it, a representation that computes which piece sits where on the board right now. It knows the board without knowing the rules.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">When Mimicry Deepens, a Map Appears</a><a class="jump" href="#sec-2">Sutton's Blade</a><a class="jump" href="#sec-3">One Map, or a Bag of Heuristics?</a><a class="jump" href="#sec-4">The Wrong Question</a><a class="jump" href="#sec-5">The Bitter Lesson Turns on Its Author</a><a class="jump" href="#sec-6">So What Corrects the Tool?</a></nav><p>I keep stopping in front of this one scene. On the question of LLMs we split into two camps. One says the thing understands the world; the other says it merely mimics words a human once wrote. Which is the Othello machine? If it is mimicry, how does it know the board — and if it is understanding, why was it never taught the rules? This piece follows that fork, not to pick an answer, but to chase the possibility that the question itself has been set down in the wrong place.</p><h2 id="sec-1">When Mimicry Deepens, a Map Appears</h2><p>Start with the case for emergence. Propping up the weaker side as a straw man and knocking it over is not thinking, so begin with this camp's hardest result.</p><p>The first finding from the Othello experiment was subtle. A non-linear probe trained to reconstruct the board state had an error rate of <span class="num">26.2%</span> on a randomly initialized model, which fell to <span class="num">1.7%</span> once the model had finished training. Something like a board sits somewhere inside the network. A skeptic could fairly object here — <em>isn't the probe wringing the board out by force?</em> — and the objection was legitimate. Then a follow-up changed one thing, and the picture sharpened. Read the board not in absolute colors — black/white — but in player-relative coordinates — mine/yours/empty — and a simple linear probe alone reached over <span class="num">99%</span> accuracy. More than that: twist that linear direction artificially, and the model's next move changes causally. The representation is not merely smeared across the weights. The model reads it to choose its move.</p><div class="tablewrap"><table><thead><tr><th>Othello-GPT board reconstruction</th><th>Result</th></tr></thead><tbody><tr><td>Non-linear probe · randomly initialized model</td><td><span class="num">26.2%</span> error</td></tr><tr><td>Non-linear probe · trained model</td><td><span class="num">1.7%</span> error</td></tr><tr><td>Linear probe · player-relative coordinates (mine/yours/empty)</td><td><span class="num">99%</span>+ accurate; intervening on the linear direction changes behavior causally</td></tr></tbody></table></div><p><em>Table: the core evidence for the emergence camp. Sources — Li et al., Othello-GPT (ICLR <span class="num">2023</span>) · Neel Nanda, linear-representation analysis (<span class="num">2023</span>). As of <span class="num">2026-06</span>-27.</em></p><p>Nor is this peculiar to Othello. Gurnee and Tegmark opened up the Llama-2 family and showed that feeding it a city name spontaneously forms a linear representation corresponding to latitude and longitude, and feeding it an event forms one corresponding to the year. The larger the model, the more accurate the map — and you could even pick out the neurons that handle space and the neurons that handle time, separately.</p><p>Read only this far and the conclusion looks all but settled. Let mimicry run deep enough and a map grows inside it. To predict the next word well, it pays in the end to internalize the structure of the world those words point to, and so the model draws a scale model of the world without being asked. That is the reading you want to reach for.</p><h2 id="sec-2">Sutton's Blade</h2><p>Richard Sutton — a founder of reinforcement learning and a <span class="num">2024</span> Turing Award co-laureate — rejects that conclusion head-on. In the autumn of <span class="num">2025</span>, in a long conversation with Dwarkesh Patel, he pinned the LLM down as a "dead end." His logic does not fight over whether the representation exists. It cuts lower.</p><p>Sutton's distinction is this. What an LLM learns is <em>what a person will say next</em> — not <em>what will happen next in the world</em>. The two look like the same act of prediction, but they differ at the root. The former imitates the speech process of a human speaker; the latter knows how a physical environment responds to an action. So he calls the LLM not a model <em>of the world</em> but a model <em>of the human language-generation process</em>. Even when we say the Othello machine knows the board, that knowing was shaped indirectly, through external data — legal move sequences someone else handed it — not won by placing a stone itself, watching it flip, and learning from the result.</p><p>And decisively, in Sutton's view the LLM lacks three things: a goal, ground truth, and the ability to learn on the job — continual learning. Once pretraining ends, the weights freeze and only inference repeats. There is no structural mechanism by which today's mistake gets inscribed into tomorrow's weights and corrected. Even Patel granted that this absence of continual learning is "a genuine basic gap." He pushes back, though: because today's models are trained with reinforcement learning on tasks where the answer is verified — mathematical proofs, coding — the line between imitation and experience is not as clean as Sutton draws it.</p><h2 id="sec-3">One Map, or a Bag of Heuristics?</h2><p>The most refined voice doubting emergence comes not from Sutton but from the side of the cognitive scientist Melanie Mitchell. But push that doubt to its end and you reach not a denial of emergence but a more precise question.</p><p>Mitchell takes the linear-probe result from the Othello experiment seriously, but she does not cross from there to "there is a world model." Her objection was twofold. One: the non-linear probe is "too powerful" — the credit for reconstructing the board may belong to the probe's own computation rather than to the transformer. Two: when student researchers took it apart, the Othello model looked less like a single coherent board model than like a bundle of local rules scattered across the board — a "bag of heuristics." In fact the first edge was largely blunted by the follow-up linear-probe result (<span class="num">99%</span> with a computationally weak probe, plus causal intervention). So the live issue now is the second one: one map, or a bag of heuristics? Which is why Mitchell withholds judgment rather than ruling: "the claim that an abstract world model has emerged in LLMs is not yet supported by strong evidence."</p><p>The same probe experiment reads on one side as "evidence of a world model" and on the other as "evidence of a bag of heuristics." Not because the evidence is thin. Because we have never agreed on what to pack into the words "world model."</p><h2 id="sec-4">The Wrong Question</h2><p>After looking at it for a long time, the place I arrive is this. "Does the LLM have a world model?" is the wrong question, set down in the wrong place.</p><p>Frame it as representation-present-or-absent, and the emergence research has already supplied part of the answer. Something map-like is inside the model. Sutton's rebuttal does not, in fact, deny the existence of that map. What he strikes at is the map's <em>provenance</em> and its <em>correctability</em>. Where did it come from — someone else's text, or a result I obtained by acting? And when it is wrong, can the world correct it?</p><p>On that second point, one thing must be split apart. "Correct" has two layers. One is fixing the output mid-inference, inside the same session. The model reads a compile error and fixes its code; a person hands back a flawed draft and the next output differs. This in-context correction plainly happens. Patel's point about the blurred line between imitation and experience lands exactly here. But this correction is volatile — it vanishes when the session ends and leaves not a single character in the weights. The other layer is correction that congeals into the weights, so that next time the same mistake is made less often: persistent continual learning. What today's LLM lacks is not the first layer but precisely this second one.</p><p>So the boundary line sharpens — not "does correction occur?" but "does correction stay and accumulate?" Imagine a frozen network that represents the Othello board perfectly. It knows the board. Within any single game a person can correct it. But because that correction is never inscribed in itself, play a thousand games and the thousandth still fails in the same place the first did. The representation is there, but it has no capacity to be wrong <em>in the way that teaches itself.</em> One thing must be made clear here: a frozen network can be competent moment to moment — a calculator is corrected by nothing and yet does not err. Momentary competence and the capacity to improve oneself are different axes. So the line I mean to draw is not a definition of "intelligence in general." It is the line that separates the kind of intelligence we delegate trust to, and lean on more and more — intelligence that gets better over time. That line falls not at the static spot of "understanding versus mimicry" but at the dynamic spot of <strong>what corrects this model, and whether that correction stays.</strong></p><p>Sutton, citing the absence of continual learning and ground truth, calls the LLM a dead end. But even he still fights on the spot of "is the LLM a world model." What I mean to move is that spot itself. Posed as a static question — "does it have a world model" — the two camps only run parallel lines over the same probe result: one looks at the representation and says "it's there," the other looks at the provenance and calls it "mimicry," and they cross forever without meeting. Move the axis to "what corrects it, and whether that correction stays," and why the two read the same evidence in opposite directions is explained at a stroke: the representation is real but has no agency over itself, and the disagreement comes not from a shortage of evidence but from the fact that we never agreed on what "world model" means. Sutton's continual-learning point is one coordinate on this axis, not the axis itself. Where he struck rightly, I move the line to a more precise place and draw it again.</p><p>Seen this way, it becomes clear why the picture of reinforcement learning Sutton spent his life on is so different. The agent in RL acts upon an environment, takes back a ground-truth signal called reward, and corrects itself with that signal. The one thing the frozen Othello network can never do — the result coming back to correct the self — sits here in the dead center of the circuit. Sutton and colleagues pushed it further still, advancing the hypothesis that the single principle of reward maximization alone could underwrite the whole of natural and artificial intelligence ("Reward is enough"). Whether intelligence <em>is</em> reward maximization — there I do not follow him. A head-on rebuttal exists in the literature — that a single scalar reward is not enough — and that question stays open. But whether the grand picture is right or wrong, one thing remains: at the center of the reinforcement-learning circuit sits a loop in which the world corrects me, and in today's LLM that loop is severed at the level of the weights. And that severed loop is exactly where the axis I drew points.</p><h2 id="sec-5">The Bitter Lesson Turns on Its Author</h2><p>Go one step further, though, and a strange paradox surfaces.</p><p>In <span class="num">2019</span>, in "The Bitter Lesson," Sutton wrote the largest lesson of <span class="num">70</span> years of AI in a single line: general methods that leverage computation ultimately beat methods that build in human domain knowledge, and by a large margin. In chess, in Go, in speech recognition, systems with what humans believe they know hand-coded in led in the short run but collapsed in the long run before two methods that scale arbitrarily — search and learning. The sentence he left is like a blade: building in how we think we think does not work in the long run. We must plant not the <em>content</em> of discovery but the <em>capacity</em> to discover.</p><p>And it is this very blade that turns on the LLM. The LLM is a vast compression of all the text humanity has written — that is, of <em>what humans have discovered.</em> In Sutton's view that is no shining proof of the bitter lesson. It is a negative example, rather. The model's cognition is capped at the ceiling of human knowledge, and no animal in the natural world, he argues, learns by that kind of imitation.</p><p>This last premise, though, is contestable. The human is precisely the animal that learns by imitating at scale — through language, culture, and the game record — and the cumulative culture of <em>Homo sapiens</em> is itself a product of imitation learning. On that view, room opens to argue that the LLM, reasoning over text, is a kind of experiential learning too. Sutton's proposition that "imitation is a dead end" is less established doctrine than a still-contested issue. And the very fact that this dispute never ends is what underwrites my diagnosis. The line "imitation or experience" is, like "world model or not," a static question no one can settle. Shift to the correction axis and the dispute falls away — because whether the imitation is human or an LLM's, all you need ask is whether the result comes back, corrects the self, and accumulates.</p><p>Read the same evidence from three positions and it splits like this.</p><div class="tablewrap"><table><thead><tr><th>Lens</th><th>Emergence reading</th><th>Sutton / skeptic reading</th></tr></thead><tbody><tr><td>Technical</td><td>Board, space, and time representations arise spontaneously from move records and text alone; intervening on the linear direction changes behavior</td><td>Frozen weights, no continual learning, an observer that does not act → correction does not stay</td></tr><tr><td>Epistemic</td><td>To predict the next token well, internalizing world structure pays → mimicry into a map</td><td>The representation's provenance is someone else's text; a "human language-generation process" model, not a "world" model</td></tr><tr><td>Philosophical</td><td>The line between deep-enough mimicry and understanding is unclear; reserve judgment for want of strong evidence</td><td>Intelligence = goal, correction, agency; reward maximization is central, but its sufficiency is in dispute</td></tr></tbody></table></div><p><em>Table: the dialectic of three lenses dividing the same evidence. Sources — Othello-GPT (Li et al., ICLR <span class="num">2023</span>) · linear representations (Nanda et al., <span class="num">2023</span>) · space-and-time representations (Gurnee &amp; Tegmark, ICLR <span class="num">2024</span>) · Sutton interview (Dwarkesh, <span class="num">2025-09</span>-26) · Mitchell (<span class="num">2025</span>) · Reward is enough (Silver et al., <span class="num">2021</span>) and its rebuttal (Vamplew et al., <span class="num">2022</span>). As of <span class="num">2026-06</span>-27.</em></p><h2 id="sec-6">So What Corrects the Tool?</h2><p>This contemplation does not end in the abstract; it comes back to my desk. Most of us now use this model every day. We hand it a draft, have it write code, set it to summarize a source. If so, the question to ask is not the metaphysics of "does this understand the world?" but a far more practical sentence. <em>What corrects this output, and does that feedback channel exist?</em></p><p>Where the answer is verified on the spot — code that compiles, a calculation that comes out right, a function whose tests pass — the world returns the output quickly, right there. So delegation is relatively safe. Conversely, where no ground-truth signal of right and wrong comes back at once — a judgment, a strategy, the truth of a matter of fact, a decision that carries accountability — the correction channel is empty. That empty seat is exactly where a human must stay in the loop. (What disappears when this delegation is pushed all the way to a life-and-death decision is taken up separately in <a class="wikilink" href="https://refract.blog/en/posts/%EC%9E%90%EC%9C%A8%EB%AC%B4%EA%B8%B0-%EC%9C%84%EC%9E%84/">Who Pulled the Trigger — Autonomous Weapons and No One Left to Answer</a>.)</p><p>To be honest, one more layer has to go on top. A channel existing does not mean it is safe. Whether what that channel measures is the real answer is a further problem. Code that compiles but whose specification is wrong; a function that passes its tests but whose tests are themselves badly written — cleverly overfitting to a measurable signal is common. So the question refracts into two stages. <em>What corrects this output — and does what that correction measures really match what I want?</em> Ask not whether the model "understands" but <em>what tells it that it is wrong, and is that telling trustworthy</em> — and the line of how far to delegate and where to stop and inspect comes into focus.</p><p>Sutton goes further still, all the way to: the succession from humanity to AI is inevitable, so prepare for it rather than fear it. That is not a verified fact but one old scholar's forecast, and I do not follow him that far. But one thing he got right remains. To ask after the conditions of real intelligence is to ask not what the model knows but what corrects the model and whether that correction stays. A machine that knows the board without ever having seen one is a marvel. But until we ask what sets it right when it draws the board wrong, and whether that setting-right carries into the next game, we have not yet spoken of intelligence.</p></div><section class="sources"><div class="src-l">Sources</div><div class="tablewrap"><table><thead><tr><th>#</th><th>Outlet (via)</th><th>Primary source</th><th>Link</th><th>As of</th></tr></thead><tbody><tr><td><span class="num">1</span></td><td>incompleteideas.net</td><td>Richard Sutton, <em>The Bitter Lesson</em></td><td>http://www.incompleteideas.net/IncIdeas/BitterLesson.html</td><td><span class="num">2019-03</span>-13</td></tr><tr><td><span class="num">2</span></td><td>Dwarkesh Podcast</td><td>Richard Sutton interview ("dead end" · absence of continual learning)</td><td>https://www.dwarkesh.com/p/richard-sutton</td><td><span class="num">2025-09</span>-26</td></tr><tr><td><span class="num">3</span></td><td>Dwarkesh Podcast</td><td>Dwarkesh Patel, "Thoughts on Sutton" (rebuttal note)</td><td>https://www.dwarkesh.com/p/thoughts-on-sutton</td><td><span class="num">2025-09</span></td></tr><tr><td><span class="num">4</span></td><td>ACM</td><td><span class="num">2024</span> ACM Turing Award (Barto &amp; Sutton, reinforcement learning)</td><td>https://awards.acm.org/about/<span class="num">2024</span>-turing</td><td><span class="num">2025-03</span></td></tr><tr><td><span class="num">5</span></td><td>arXiv</td><td>Li et al., "Emergent World Representations" (Othello-GPT, ICLR <span class="num">2023</span>)</td><td>https://arxiv.org/abs/<span class="num">2210.13382</span></td><td><span class="num">2023</span></td></tr><tr><td><span class="num">6</span></td><td>neelnanda.io</td><td>Neel Nanda, "Othello-GPT Has A Linear Emergent World Representation"</td><td>https://www.neelnanda.io/mechanistic-interpretability/othello</td><td><span class="num">2023</span></td></tr><tr><td><span class="num">7</span></td><td>arXiv</td><td>Gurnee &amp; Tegmark, "Language Models Represent Space and Time" (ICLR <span class="num">2024</span>)</td><td>https://arxiv.org/abs/<span class="num">2310.02207</span></td><td><span class="num">2024</span></td></tr><tr><td><span class="num">8</span></td><td>AI: A Guide for Thinking Humans</td><td>Melanie Mitchell, "LLMs and World Models, Part <span class="num">2</span>"</td><td>https://aiguide.substack.com/p/llms-and-world-models-part-2</td><td><span class="num">2025</span></td></tr><tr><td><span class="num">9</span></td><td>Artificial Intelligence (Elsevier)</td><td>Silver et al., "Reward is enough" (v299, <span class="num">103535</span>)</td><td>https://www.sciencedirect.com/science/article/pii/S0004370221000862</td><td><span class="num">2021</span></td></tr><tr><td><span class="num">10</span></td><td>arXiv</td><td>Vamplew et al., "Scalar reward is not enough" (rebuttal)</td><td>https://arxiv.org/abs/<span class="num">2112.15422</span></td><td><span class="num">2022</span></td></tr><tr><td><span class="num">11</span></td><td>X (@RichardSSutton)</td><td>Richard Sutton, on AI succession (WAIC talk)</td><td>https://x.com/RichardSSutton/status/<span class="num">1700315838468043015</span></td><td><span class="num">2023-09</span></td></tr></tbody></table></div></section><footer class="byline"><span class="ai-dot"></span><span>This piece was analyzed and verified across multiple dimensions with AI, and reviewed by a human writer.</span></footer></article>]]></content:encoded></item>
<item><title>Starship's Reuse: Reuse Is Already Proven — Starship Isn't</title><link>https://refract.blog/en/posts/%EC%8A%A4%ED%83%80%EC%8B%AD-%EC%9E%AC%EC%82%AC%EC%9A%A9/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EC%8A%A4%ED%83%80%EC%8B%AD-%EC%9E%AC%EC%82%AC%EC%9A%A9/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Technology</category><description>A rocket that reaches orbit has, until now, mostly been thrown away after a single use. Starship means to break that premise. SpaceX's Starship is a two-stage…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#1f9e8a"></span><span class="kx">Technology</span><span class="ksep">·</span><span class="kx">우주</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-27T16:30:42"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><h1 class="title">Starship's Reuse: Reuse Is Already Proven — Starship Isn't</h1><div class="body"><p class="lead">A rocket that reaches orbit has, until now, mostly been thrown away after a single use. Starship means to break that premise. SpaceX's Starship is a two-stage, fully reusable launch vehicle, built so that both the first-stage Super Heavy booster and the upper-stage Starship vehicle are recovered and flown again. Both stages are built of stainless steel and burn methane and liquid oxygen in Raptor engines. The booster carries 33 Raptors; the upper stage, six.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">Recovery: Booster and Upper Stage Are Different Problems</a><a class="jump" href="#sec-2">How Far It Has Actually Gotten</a><a class="jump" href="#sec-3">The Economics of Reuse Are Already Proven — on Falcon 9</a><a class="jump" href="#sec-4">Starship's Numbers: Separating the First Drop from the Second</a><a class="jump" href="#sec-5">What Opens Up When Launch Is Cheap and Frequent</a></nav><p>But the question to ask of Starship is not "can it be reused." That reuse reshapes launch economics is already proven. The same company's Falcon <span class="num">9</span> proved it. The real question is how far Starship has <em>actually</em> gotten, and what is still assumption.</p><h2 id="sec-1">Recovery: Booster and Upper Stage Are Different Problems</h2><p>The first gate of reuse is recovery. On Starship, each stage is recovered differently.</p><p>The booster does not set down on landing legs. A pair of mechanical arms on the launch tower—the "chopsticks," or Mechazilla—catch the descending booster out of the air. Catch it with the tower instead of legs, and the spot where you caught it is already the launch pad. SpaceX's stated end-state is to refuel the returned booster on the pad and fly it again within roughly <span class="num">30</span> minutes (a target).</p><p>The upper stage is harder. It has to survive the heat of returning from orbital velocity into the atmosphere, and it has not so much as attempted a tower catch yet. Every upper stage to date has ended in a splashdown, settling onto the sea. The reuse design aims at both stages, but the only stage whose recovery has been demonstrated is the booster.</p><h2 id="sec-2">How Far It Has Actually Gotten</h2><p>Booster catch has been demonstrated. In October <span class="num">2024</span>, on Flight <span class="num">5</span>, the tower caught a booster for the first time ever; it succeeded again on Flight <span class="num">7</span> (January <span class="num">2025</span>) and Flight <span class="num">8</span> (March <span class="num">2025</span>), three catches so far. But the most recent flight shows the technique is not yet in a stable phase. The demonstration level, stage by stage, fits on a single page:</p><div class="tablewrap"><table><thead><tr><th>Stage</th><th>Recovery method</th><th>Demonstration level (as of <span class="num">2026-06</span>)</th></tr></thead><tbody><tr><td>Booster (1st stage)</td><td>Tower mid-air catch</td><td><span class="num">3</span> catches succeeded. But the newest V3's first flight, Flight <span class="num">12</span>, ended in a crash</td></tr><tr><td>Upper stage (2nd stage)</td><td>Recover after return (design)</td><td><strong>Zero</strong>. Every flight a sea splashdown; tower catch never attempted</td></tr><tr><td>Reflight</td><td>Refurbish and relaunch a recovered vehicle</td><td>On Starship, <strong>not demonstrated</strong> (recovery ≠ reuse)</td></tr></tbody></table></div><p><em>Table <span class="num">1</span>. Starship's reuse-demonstration ladder, stage by stage. Sources: Wikipedia (List of Starship launches, Flight test <span class="num">12</span>), space.com. As-of <span class="num">2026-06</span>.</em></p><p>Flight <span class="num">12</span>, on <span class="num">22</span> May <span class="num">2026</span>, was the first flight of the new V3 (Block <span class="num">3</span>) vehicle and the Raptor <span class="num">3</span> engine. The upper stage (S39) reached space, deployed <span class="num">22</span> Starlink simulators, survived reentry, and came down under control in the Indian Ocean (a controlled splashdown). One engine shut down <span class="num">36</span> seconds into ascent, but the rest finished the climb. The booster (B19), by contrast, spun abnormally after stage separation, lost most of its engines, and—with only one lighting for the landing burn—fell into the Gulf of Mexico at roughly <span class="num">1,450 km/h</span>. There was no tower catch. On <span class="num">27</span> May the FAA grounded Starship to investigate the booster anomaly. The cumulative record stands at <span class="num">7</span> successes and <span class="num">5</span> failures across <span class="num">12</span> flights (as of <span class="num">27</span> May <span class="num">2026</span>).</p><p>In sum, what Starship has demonstrated reaches only the first gate of reuse—<em>recovery</em>. The mid-air booster-catch technique is proven, but its repeatability wavered on the newest vehicle, and the upper stage has never once been recovered. The reflight step—refurbishing a recovered vehicle and launching it again—still lies ahead.</p><h2 id="sec-3">The Economics of Reuse Are Already Proven — on Falcon 9</h2><p>A common misconception has to be cut off here. "Does reuse really lower cost" is a question already answered. What answered it was not Starship but Falcon <span class="num">9</span>.</p><p>Falcon <span class="num">9</span> reuse is long past the demonstration stage. A single booster, B1067, flew its 35th flight on <span class="num">8</span> June <span class="num">2026</span>, the most reuse of any orbital-class booster ever, and the fleet has now passed <span class="num">650</span> cumulative reuse flights. The refurbishment turnaround has fallen too—from more than <span class="num">100</span> days on the early Block <span class="num">5</span> to roughly <span class="num">40</span> days on average in <span class="num">2025</span> (as short as the nine-day range). Reuse has become an industry, not a stunt.</p><p>What that industry did to the launch market was measured in orders of magnitude. The LEO launch price fell from roughly <span class="num">$54,500/kg</span> in the Space Shuttle era to roughly <span class="num">$1,500–2,720/kg</span> on a reusable Falcon <span class="num">9</span>—a drop of about 20x. The credit, of course, cannot go to reuse alone. It is the combined result of high flight cadence and in-house manufacturing, with reuse as the core driver. The texture of the cost shows up in ARK Invest's analysis too: an estimate that Falcon <span class="num">9</span> first-stage refurbishment cost fell from roughly $13M to roughly $1M over about five years. SpaceX's Gwynne Shotwell has said the company expects roughly <span class="num">30%</span> cost savings from first-stage reuse.</p><h2 id="sec-4">Starship's Numbers: Separating the First Drop from the Second</h2><p>The logic pushing Starship is cost. But the published numbers mix fact with target. The line that separates them is simple: <strong>the first order-of-magnitude drop, which has already happened</strong>, and <strong>the second order-of-magnitude drop, which Starship promises</strong>, carry different confidence grades.</p><div class="tablewrap"><table><thead><tr><th>Category</th><th>Unit price / figure</th><th>Status</th></tr></thead><tbody><tr><td>First drop (Space Shuttle → Falcon <span class="num">9</span>)</td><td><span class="num">$54,500/kg</span> → ~<span class="num">$2,720/kg</span> (~20x)</td><td><strong>Demonstrated fact</strong></td></tr><tr><td>Second drop (Starship target)</td><td>~<span class="num">$100–500/kg</span> (analysts' near-to-mid-term projection)</td><td><strong>Projection</strong></td></tr><tr><td>Starship long-term target</td><td><span class="num">$10/kg</span> (Musk)</td><td><strong>Target (unmet)</strong></td></tr><tr><td>Cost per launch</td><td>$100M (expendable configuration)</td><td><strong>Target (unmet)</strong></td></tr><tr><td>V3 payload</td><td>LEO <span class="num">100t</span>, reusable configuration</td><td><strong>Design / nominal figure</strong> (V3's first flight was Flight <span class="num">12</span>)</td></tr></tbody></table></div><p><em>Table <span class="num">2</span>. The two drops in launch price — the demonstrated first drop and the promised second. Sources: NASA NTRS (launch-price analysis), SpaceX (official), ARK Invest, analyst projections. As-of <span class="num">2026</span>. The first row (demonstrated) and the rest (target/projection) carry different confidence grades.</em></p><p>The first row and the rest must not be read in the same ink. Falcon <span class="num">9</span>'s 20x drop is something that happened; Starship's <span class="num">$100–500/kg</span> is something that has not happened yet. The second drop is a smaller multiple than the first one Falcon <span class="num">9</span> delivered against the Shuttle (roughly <span class="num">$2,720</span> → <span class="num">$100–500/kg</span>, <span class="num">5</span>–10x), but its premise is different. The first drop came from reusing the first stage alone; Starship's promise holds only if <em>both</em> stages are recovered and reflown fast. And that two-stage reuse—as the previous section showed—still has an upper stage that has never once been recovered.</p><p>In sum, the question changes. "Does reuse lower the unit price" is already proven. What is open is whether the <em>second</em> order-of-magnitude drop is as certain as the <em>first</em>. Starship's cost promises are the target and projection for that second drop. Starship has yet to post collateral for that promise, and Falcon <span class="num">9</span>'s precedent is filling the gap in its place.</p><h2 id="sec-5">What Opens Up When Launch Is Cheap and Frequent</h2><p>If the second drop actually materializes, the effect spreads past a single line item on launch price into the structure of missions themselves. There is a class of architecture that holds together only once launch is cheap and frequent enough.</p><p>The prime example is orbital propellant resupply. The Starship lunar lander (HLS) has to fill a propellant depot in LEO for a single Moon mission, and doing so takes roughly <span class="num">10</span>-odd tanker launches. This structure is hard to justify economically if launch is expensive—because it would mean throwing away ten-odd rockets per mission. Reuse changes that arithmetic. But this architecture still rests on assumption. The orbital propellant-transfer demonstration was scheduled for <span class="num">2026</span> but slipped, and as of March <span class="num">2026</span> it had not taken place; the Artemis III crewed landing, tied to that schedule, is set for some time after mid-2027.</p><p>Starship reuse, in the end, has to be read on two clocks. On the engineering clock, the catch of one stage—the booster—is proven, while the upper stage, stable repeatability, and reflight are unfinished. On the economic clock, the fact that reuse lowers launch price by an order of magnitude is already nailed down on Falcon <span class="num">9</span>, but that Starship adds a second drop on top of it is still a promise. The first clock has nearly run its course; the second has only just begun to move.</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li>SpaceX Starship / Flight test 12 / List of Starship launches — Wikipedia (flight facts, configuration, cumulative record; as-of 2026-05–06): <a href="https://en.wikipedia.org/wiki/Starship_flight_test_12" target="_blank" rel="noopener noreferrer">Flight test 12</a> · <a href="https://en.wikipedia.org/wiki/List_of_Starship_launches" target="_blank" rel="noopener noreferrer">List of launches</a> · <a href="https://en.wikipedia.org/wiki/SpaceX_Starship" target="_blank" rel="noopener noreferrer">SpaceX Starship</a></li><li>First mid-air catch of the Super Heavy booster (Flight 5) — space.com, 2024-10: <a href="https://www.space.com/spacex-starship-flight-5-launch-super-heavy-booster-catch-success-video" target="_blank" rel="noopener noreferrer">article</a></li><li>Flight 12 launch live updates — space.com, 2026-05-22: <a href="https://www.space.com/news/live/spacex-starship-flight-12-launch-updates-may-22-2026" target="_blank" rel="noopener noreferrer">article</a></li><li>Falcon 9 first-stage refurbishment cost estimate ($13M→$1M) — ARK Invest analysis: <a href="https://www.ark-invest.com/newsletters/issue-335" target="_blank" rel="noopener noreferrer">Newsletter 335</a></li><li>Falcon 9 reuse cost savings (roughly 30% expected, Shotwell) — SpaceNews: <a href="https://spacenews.com/spacexs-reusable-falcon-9-what-are-the-real-cost-savings-for-customers/" target="_blank" rel="noopener noreferrer">article</a></li><li>Falcon 9 booster operational record (35 flights on a single booster, 650+ cumulative, ~40-day turnaround) — Wikipedia (List of Falcon 9 first-stage boosters), as-of 2026-06: <a href="https://en.wikipedia.org/wiki/List_of_Falcon_9_first-stage_boosters" target="_blank" rel="noopener noreferrer">list</a></li><li>Order-of-magnitude drop in launch price (Space Shuttle $54,500/kg → reusable Falcon 9 ~$2,720/kg) — NASA NTRS "Recent Large Reduction in Space Launch Cost": <a href="https://ntrs.nasa.gov/citations/20200001093" target="_blank" rel="noopener noreferrer">NTRS</a> · supplementary: <a href="https://orbital-intel.com/launch-cost-history/" target="_blank" rel="noopener noreferrer">launch cost history</a> · <a href="https://spacenexus.us/guide/space-launch-cost-comparison" target="_blank" rel="noopener noreferrer">SpaceNexus comparison</a></li><li>LEO $10/kg target and launch-cost context — Benzinga (Musk's remarks) · Starship HLS propellant resupply / Artemis schedule — Wikipedia (Starship HLS): <a href="https://www.benzinga.com/news/22/09/28909310/elon-musk-calls-starship-an-incredible-enabler-for-science-launch-costs-at-a-highly-competitive-10kg" target="_blank" rel="noopener noreferrer">Benzinga</a> · <a href="https://en.wikipedia.org/wiki/Starship_HLS" target="_blank" rel="noopener noreferrer">Starship HLS</a></li></ol></section><footer class="byline"><span class="ai-dot"></span><span>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</span></footer></article>]]></content:encoded></item>
<item><title>On-Device AI: Cost and Jurisdiction, Not Chips, Draw the Line</title><link>https://refract.blog/en/posts/%EC%98%A8%EB%94%94%EB%B0%94%EC%9D%B4%EC%8A%A4-ai/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EC%98%A8%EB%94%94%EB%B0%94%EC%9D%B4%EC%8A%A4-ai/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Technology</category><description>Classifying a single photo no longer requires a round trip to a cloud server. It finishes on the processor built into your phone or laptop. That is on-device AI…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#1f9e8a"></span><span class="kx">Technology</span><span class="ksep">·</span><span class="kx">AI</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-27T16:29:33"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><h1 class="title">On-Device AI: Cost and Jurisdiction, Not Chips, Draw the Line</h1><div class="body"><p class="lead">Classifying a single photo no longer requires a round trip to a cloud server. It finishes on the processor built into your phone or laptop. That is on-device AI. The data never leaves the device, so privacy holds; it works without a network; and the round-trip latency disappears. The usual reading stops there—a story about chips and compression. But what gets pushed down to the device and what stays on the server, the line that actually decides this, is not drawn by silicon alone.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">Two Engineering Axes: NPUs and Quantization</a><a class="jump" href="#sec-2">The Models Running on Devices Now</a><a class="jump" href="#sec-3">Cost: Whose Silicon Absorbs the Inference?</a><a class="jump" href="#sec-4">Jurisdiction: Under Whose Law Does the Data Sit?</a><a class="jump" href="#sec-5">Who Draws the Line</a></nav><h2 id="sec-1">Two Engineering Axes: NPUs and Quantization</h2><p>Running a model on a device means solving two problems: fitting it inside limited memory and power (compression), and running it fast enough (acceleration).</p><p>Acceleration falls to the NPU—a chip specialized for neural-network operations like matrix multiplication. By one industry estimate, NPUs ship in more than <span class="num">80%</span> of Qualcomm's recent SoCs. The accelerators refresh every generation. On the Hexagon NPU in the Snapdragon <span class="num">8</span> Elite Gen <span class="num">5</span>, unveiled on <span class="num">24</span> September <span class="num">2025</span>, INT8 object detection finishes in roughly <span class="num">12–15 ms</span> on reference-device benchmarks.</p><p>Compression falls to quantization, which trims weight precision to cut memory and computation. The recipe for putting an LLM on a device has converged on a single path: train in <span class="num">16</span>-bit, then quantize to <span class="num">4</span>-bit for deployment. GPTQ in <span class="num">2022</span> and AWQ in <span class="num">2023</span> cut memory to roughly a quarter at <span class="num">4</span>-bit while preserving most of the quality, and INT8 loses almost nothing against FP32 across most production workloads. Some have pushed further. BitNet b1.<span class="num">58</span>, released by Microsoft in April <span class="num">2025</span>, is a <span class="num">1.58</span>-bit model that holds each weight to just three values—-1, <span class="num">0</span>, +<span class="num">1</span>. At the two-billion-parameter scale, its non-embedding memory comes to <span class="num">0.4 GB</span>, against <span class="num">1.4 GB</span> for a comparable Gemma-3 1B.</p><h2 id="sec-2">The Models Running on Devices Now</h2><p>On these two axes, billion-parameter models already sit inside real shipping hardware. Sparse architectures activate only a fraction of them at a time.</p><div class="tablewrap"><table><thead><tr><th>Model</th><th>Parameters</th><th>Memory / Notes</th><th>Source · As-of</th></tr></thead><tbody><tr><td>Apple AFM <span class="num">3</span> Core</td><td>3B (dense)</td><td>On-device default</td><td>Apple official, <span class="num">2026-06</span></td></tr><tr><td>Apple AFM <span class="num">3</span> Core Advanced</td><td>20B (sparse)</td><td>Only <span class="num">1</span>–4B active per request</td><td>Apple official, <span class="num">2026-06</span></td></tr><tr><td>Google Gemini Nano</td><td><span class="num">1</span>.8B / <span class="num">3</span>.25B</td><td>~<span class="num">1 GB</span> at <span class="num">4</span>-bit (per secondary reporting)</td><td>Secondary reporting, <span class="num">2026-06</span></td></tr><tr><td>Microsoft BitNet b1.<span class="num">58</span></td><td>2B</td><td><span class="num">1.58</span>-bit, <span class="num">0.4 GB</span> non-embedding</td><td>arXiv, <span class="num">2025-04</span></td></tr></tbody></table></div><p><em>Table: Scale of on-device commercial and open-weight models. Sources—Apple Machine Learning Research (AFM3), arXiv <span class="num">2504.12285</span> (BitNet), secondary reporting (Gemini Nano). As-of <span class="num">2025-04</span> to <span class="num">2026-06</span>.</em></p><p>These are a different weight class from the large models in the cloud. Which leaves a question. Being able to run a small-enough model on a device is one thing; having to push inference down to the device is another. Why push it down now?</p><h2 id="sec-3">Cost: Whose Silicon Absorbs the Inference?</h2><p>Cost answers first. Cloud inference prices have fallen fast. a16z calls the trend "LLMflation": GPT-4-class inference dropped from roughly <span class="num">$20</span> per million tokens in late <span class="num">2022</span> to about <span class="num">$0.40</span>, cheapening by some 10x a year at constant performance. The decline is not uniform. By Epoch AI's measurements, the rate ranges from 9x to 900x a year depending on task difficulty.</p><p>If unit prices have fallen this far, why push inference to the device at all? Scale. One industry analysis estimates that a single AI inference query costs an order of magnitude more than a traditional search, eroding the cloud provider's per-query margin. Cheaper unit prices do not erase the inference line on the provider's books when call volume explodes.</p><p>Push inference to the device and that cost leaves the provider's ledger and lands on the chip the user has already paid for. Inference shifts from the provider's operating expense to capital expense on user-owned silicon. This is the logic behind Apple's hybrid of on-device inference and its own Private Cloud Compute: avoid the data-center capital outlay (the supply ceiling on those data-center AI accelerators is set by <a class="wikilink" href="https://refract.blog/en/posts/%EB%B0%98%EB%8F%84%EC%B2%B4-%ED%9B%84%EA%B3%B5%EC%A0%95/">packaging</a>) and keep AI capex more conservative than rivals'.</p><h2 id="sec-4">Jurisdiction: Under Whose Law Does the Data Sit?</h2><p>Alongside cost, regulation redraws the line—because on-device AI's primary benefit, "the data never leaves the device," becomes a compliance asset.</p><p>The EU AI Act applies its high-risk-system obligations from <span class="num">2</span> August <span class="num">2026</span>. Penalties for violations reach up to <span class="num">7%</span> of global annual revenue or €<span class="num">35</span> million for prohibited practices. At the same time, the physical location of data is no guarantee. The U.S. CLOUD Act exposes data stored in the EU to American jurisdiction if the provider is U.S.-headquartered. Under <span class="num">2026</span> compliance readings, using "a U.S. hyperscaler's EU region" does not by itself satisfy data residency. By one industry report, roughly <span class="num">20%</span> of European companies have begun repatriating core data to in-region facilities.</p><p>When data never leaves the device, much of this problem never arises in the first place. And even when the cloud is unavoidable, the line gets redrawn. Apple Private Cloud Compute uses data only to process a request and stores nothing once the request ends; built on Apple Silicon and the Secure Enclave, it is designed so that not even Apple can reach it. It lifts the on-device principle of non-retention up into the cloud.</p><h2 id="sec-5">Who Draws the Line</h2><p>The limits are clear. Memory and power constraints keep devices to mostly small models, and low-bit quantization trades away some accuracy for the weight it sheds. At INT8 the loss is small, but the price climbs the further you trim the bits.</p><p>So what runs where is not settled by the chip's capability alone. Three forces draw the line together: how fast it has to be (latency), who absorbs the inference cost (cost incidence), and under whose law the data sits (jurisdiction). Work that is light and instant, or sensitive, or that must run offline goes to the device; heavy work goes to the server. On-device AI is not a technology that replaces the cloud—it is one that redraws the line between the two. And the decision about where that line falls has left the engineer's hands. Cost, legal, and product now make it together.</p></div><section class="sources"><div class="src-l">Sources</div><div class="tablewrap"><table><thead><tr><th>#</th><th>Outlet (via)</th><th>Primary source</th><th>Link</th><th>As-of</th></tr></thead><tbody><tr><td><span class="num">1</span></td><td>Apple Machine Learning Research</td><td>Apple (third-generation foundation models)</td><td>https://machinelearning.apple.com/research/introducing-third-generation-of-apple-foundation-models</td><td><span class="num">2026-06</span></td></tr><tr><td><span class="num">2</span></td><td>Apple Security Research</td><td>Apple (Private Cloud Compute)</td><td>https://security.apple.com/blog/private-cloud-compute/</td><td><span class="num">2024-06</span></td></tr><tr><td><span class="num">3</span></td><td>arXiv</td><td>Microsoft (BitNet b1.<span class="num">58</span> 2B4T)</td><td>https://arxiv.org/abs/<span class="num">2504.12285</span></td><td><span class="num">2025-04</span></td></tr><tr><td><span class="num">4</span></td><td>a16z</td><td>Guido Appenzeller, "LLMflation"</td><td>https://a16z.com/llmflation-llm-inference-cost/</td><td><span class="num">2024-11</span></td></tr><tr><td><span class="num">5</span></td><td>Epoch AI</td><td>Epoch AI (inference price trends)</td><td>https://epoch.ai/data-insights/llm-inference-price-trends</td><td><span class="num">2025</span></td></tr><tr><td><span class="num">6</span></td><td>European Commission</td><td>EU AI Act (regulatory framework)</td><td>https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai</td><td><span class="num">2026-06</span></td></tr><tr><td><span class="num">7</span></td><td>Lyceum Technology</td><td>US CLOUD Act / EU data residency</td><td>https://lyceum.technology/magazine/eu-data-residency-ai-infrastructure/</td><td><span class="num">2026-06</span></td></tr><tr><td><span class="num">8</span></td><td>Fortune / Kavout</td><td>Apple AI capex &amp; strategy (reporting)</td><td>https://fortune.com/<span class="num">2026</span>/<span class="num">02</span>/<span class="num">17</span>/why-apple-isnt-spending-big-on-ai-capex-commodity-integration-strategy/</td><td><span class="num">2026-02</span></td></tr><tr><td><span class="num">9</span></td><td>Aleph Zero Labs / Google for Developers</td><td>NPU, quantization, on-device benchmarks</td><td>https://www.alephzerolabs.com/blog/on-device-ai-2026-sub-20ms/</td><td><span class="num">2026-06</span></td></tr><tr><td><span class="num">10</span></td><td>Android Police</td><td>Google Gemini Nano specs (secondary reporting)</td><td>https://www.androidpolice.com/gemini-nano-guide/</td><td><span class="num">2026-06</span></td></tr></tbody></table></div></section><footer class="byline"><span class="ai-dot"></span><span>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</span></footer></article>]]></content:encoded></item>
<item><title>Packaging Sets the Ceiling on AI Accelerators: Why the Back End Became the Center of Gravity</title><link>https://refract.blog/en/posts/%EB%B0%98%EB%8F%84%EC%B2%B4-%ED%9B%84%EA%B3%B5%EC%A0%95/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EB%B0%98%EB%8F%84%EC%B2%B4-%ED%9B%84%EA%B3%B5%EC%A0%95/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Technology</category><description>Semiconductor manufacturing splits in two. The front end etches transistors into a wafer; the back end cuts, stacks, links, and tests the finished die into a pa…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#1f9e8a"></span><span class="kx">Technology</span><span class="ksep">·</span><span class="kx">반도체/후공정</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-27T17:31:29"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><div class="vcaveat"><span class="vc-l">Note</span><span>톤 — 기술 preset(건조·중립)에서 분석 칼럼체로 일부 드리프트(의도적 허용, 차기 tone 재합의 대상). 비차단 nit.</span></div><h1 class="title">Packaging Sets the Ceiling on AI Accelerators: Why the Back End Became the Center of Gravity</h1><div class="body"><p class="lead">Semiconductor manufacturing splits in two. The front end etches transistors into a wafer; the back end cuts, stacks, links, and tests the finished die into a package. True to the name, the back end was long treated as a low-value auxiliary step bolted onto the rear of the front end. Not anymore. The decisive constraint on how much AI hardware ships in 2026 is not wafer starts in the front end but packaging allocation in the back. The leading-edge front-end nodes are sold out too—but the constraint now setting the additional ceiling sits on the packaging side. When Nvidia GPUs run short, the cause is less that the logic die cannot be printed than that there is no packaging slot to bind that die with memory into a single block.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">The Pieces of the Back End: What's What</a><a class="jump" href="#sec-2">Why the Back End Became the Performance Engine</a><a class="jump" href="#sec-3">The Margin Flowed to Memory</a><a class="jump" href="#sec-4">Packaging Allocation Sets the Supply Ceiling</a><a class="jump" href="#sec-5">The Control Line Extended to HBM</a></nav><h2 id="sec-1">The Pieces of the Back End: What's What</h2><p>The back end comes down to one question: how do you place many dies close together inside a single package? The closer they sit, the faster the signals between them travel and the better the power efficiency. The approaches split broadly into <span class="num">2</span>.5D—placing dies side by side—and 3D—stacking them upward.</p><div class="tablewrap"><table><thead><tr><th>Component</th><th>What it is</th><th>Key technology</th></tr></thead><tbody><tr><td><strong><span class="num">2</span>.5D — CoWoS</strong></td><td>Logic die and HBM sit side by side on a silicon interposer, linked by TSVs (through-silicon vias) that run through the interposer. The standard package for AI accelerators</td><td>Silicon interposer + TSV</td></tr><tr><td><strong>3D — Hybrid bonding (SoIC)</strong></td><td>Dies stack upward, but copper bonds directly to copper with no solder bumps (microbumps). At a production pitch of <span class="num">6</span>µm, it narrows the line width by roughly <span class="num">5</span>–7x versus microbumps (<span class="num">30–40</span>µm). TSMC frames this as roughly 100x the interconnect density per unit area</td><td>Solderless Cu-Cu direct bonding</td></tr><tr><td><strong>HBM</strong></td><td>Memory that stacks DRAM dies vertically and links them through with TSVs to push up bandwidth. It is itself a product of 3D stacking (the back end)</td><td>Vertical DRAM stacking + TSV</td></tr><tr><td><strong>Chiplet</strong></td><td>A large chip is split into smaller function-specific dies, built separately, then relinked in the package. The linking spec is the open standard UCIe (founded in <span class="num">2022</span> by Intel, AMD, TSMC, Samsung, Arm, and others)</td><td>Standardized die-to-die link</td></tr><tr><td><strong>Test</strong></td><td>Before stacking, known-good dies (KGD) are sorted out. Stack a defective one and the healthy dies go to waste with it, so the more layers, the heavier the test burden</td><td>KGD screening</td></tr></tbody></table></div><p><em>Table sources: CoWoS structure — WikiChip (TSMC) / hybrid-bonding pitch and density — TSMC SoIC announcement (via Tom's Hardware) / UCIe — UCIe Consortium / as-of <span class="num">2026-06</span>. The "roughly 100x" is TSMC's figure for density per unit area; the linear pitch in the text (<span class="num">6</span>µm vs <span class="num">30–40</span>µm) is a <span class="num">5</span>–7x ratio.</em></p><p>These parts do not run separately—they nest inside one package. A single Nvidia AI accelerator places a logic die and several HBM stacks side by side on a CoWoS interposer, and each of those HBMs is itself built by stacking DRAM in 3D. The back end is where all of this binding happens.</p><h2 id="sec-2">Why the Back End Became the Performance Engine</h2><p>The answer lies on the front-end side. For decades, performance came from making transistors smaller—from Moore's law. When the cost and difficulty of that scaling hit a wall, the industry's standard roadmap (IRDS) shifted its axis. Call it "More than Moore": win density gains not from the transistor itself but from system integration—chiplets and 3D packaging.</p><p>The decisive technology here is hybrid bonding. Dies used to be linked by solder bumps (microbumps) spaced <span class="num">30–40</span>µm apart. Hybrid bonding removes the bumps and bonds copper directly to copper, narrowing the production pitch to <span class="num">6</span>µm. TSMC's roadmap targets <span class="num">4.5</span>µm in <span class="num">2029</span>, and 'SoIC-Next' targets <span class="num">3</span>µm in <span class="num">2027</span>.</p><p>This density matters because the 'wiring' between dies starts to approach the wiring density inside a chip. Dense enough, and two stacked dies behave, in effect, as a single chip. The boundary between chip and package blurs. The density gain the front end used to win by shrinking transistors, the back end now inherits by stacking dies. Integration became performance. The margin, the bottleneck, the control—every story in this piece follows from this one mechanism. Once the boundary dissolved, the money, the bottleneck, and the leverage were all drawn into the integration step that absorbed the performance.</p><p>This engine has a brake, though. The more you stack, the more the heat density per unit volume spikes. The practical ceiling on stack height is set first by the ability to pull heat out, not by the bonding pitch. As much as integration lifts performance, the next wall is heat.</p><h2 id="sec-3">The Margin Flowed to Memory</h2><p>When the performance engine moves, the margin moves with it. The advanced-packaging market is projected to grow from roughly <span class="num">$45</span> billion in <span class="num">2024</span> to roughly <span class="num">$79.4</span> billion in <span class="num">2030</span>, with <span class="num">2</span>.5D/3D expanding fastest at more than <span class="num">20%</span> a year (Yole projection). TSMC's advanced-packaging revenue is growing at roughly <span class="num">80%</span> a year as well. Its share of total revenue is still small, but it is the fastest-growing axis.</p><p>The picture is sharper on the memory side. HBM earns a far higher margin than ordinary DRAM, and it is sold out, its price locked in by forward contracts through <span class="num">2026</span>. The result is <a class="wikilink" href="https://refract.blog/en/posts/%EC%82%BC%EC%84%B1-%ED%95%98%EC%9D%B4%EB%8B%89%EC%8A%A4-%EC%BD%94%EC%8A%A4%ED%94%BC/">SK Hynix's <span class="num">2026</span> first-quarter results</a>.</p><div class="tablewrap"><table><thead><tr><th>Metric (SK Hynix <span class="num">2026</span> 1Q)</th><th>Figure</th><th>Status</th></tr></thead><tbody><tr><td>Revenue</td><td>~<span class="num">52.6</span> trillion won (record high)</td><td>Reported result</td></tr><tr><td>Operating profit</td><td>~<span class="num">37.6</span> trillion won (<span class="num">72%</span> operating margin)</td><td>Reported result</td></tr><tr><td>Comparison</td><td>Q1 operating profit &gt; full-year <span class="num">2024</span> operating profit (~<span class="num">23.5</span> trillion)</td><td>Reported result</td></tr><tr><td>HBM orders</td><td>Already exceed the next three years of planned capacity</td><td>Company statement</td></tr></tbody></table></div><p><em>Table source: SK Hynix <span class="num">2026</span> first-quarter earnings release (via CNBC, ninescrolls), as-of <span class="num">2026-04</span>-23.</em></p><p>One quarter's operating profit surpassed an entire year's from two years earlier. What turned a memory company into this was not transistor scaling alone. The decisive factor was integration—stacking dies on top of DRAM-cell scaling (the front end) to push up bandwidth—that is, HBM. HBM is a collaboration between the front end and the back end, and the center of gravity of the newly added value tipped toward the stacking side.</p><h2 id="sec-4">Packaging Allocation Sets the Supply Ceiling</h2><p>While the margin moved to the integration step, the supply ceiling came to be set there too. Building more AI accelerators requires CoWoS packaging slots—and those slots are short.</p><div class="tablewrap"><table><thead><tr><th>Item</th><th>Figure</th><th>Status</th></tr></thead><tbody><tr><td>TSMC CoWoS capacity</td><td>~<span class="num">75,000</span> wafers/month (<span class="num">2025</span>) → ~<span class="num">120,000–130,000</span> (<span class="num">2026</span> year-end exit rate)</td><td>Expansion projection</td></tr><tr><td><span class="num">2026</span> CoWoS demand</td><td>~<span class="num">1</span> million wafers/year (estimate)</td><td>Estimate</td></tr><tr><td>Nvidia share</td><td>~<span class="num">60%</span> of CoWoS locked up, over half of <span class="num">2026–27</span> expansion reserved</td><td>Estimate</td></tr><tr><td>Real bottleneck</td><td>Packaging allocation over wafer starts (front end)</td><td>Fact</td></tr></tbody></table></div><p><em>Table sources: CoWoS capacity and demand — siliconanalysts, oplexa compilation / Nvidia share — Digitimes / as-of <span class="num">2026</span>-Q1–Q2. Capacity and share are estimates/projections. Note the differing units: capacity is a monthly exit rate, demand is annualized.</em></p><p>Reconcile the numbers and it comes out like this. The <span class="num">120,000–130,000</span> figure is monthly capacity—and an exit rate reached only at the end of <span class="num">2026</span> at that. Average it over the year's ramp, and actual <span class="num">2026</span> supply falls short of the <span class="num">1</span>-million-wafer annual demand. That is why expansion does not break the sellout. Nvidia alone holds roughly <span class="num">60%</span> of CoWoS and has pre-reserved more than half of the expansion, filling the lines years deep. So the ceiling on GPU supply is set first by packaging allocation, not by the front end that prints the logic die.</p><p>Packaging is not the only constraint, of course. HBM supply itself, ABF substrates, and power delivery are all tight at the same time. Nor is CoWoS the only answer—alternatives like Intel's EMIB and Foveros, Samsung's I-Cube, and glass interposers become the variables that could ease the bottleneck. Still, at this moment the binding constraint that hits the ceiling first is CoWoS allocation.</p><p>Nor does this back end finish inside a single company. A large share depends on OSATs (outsourced assembly and test), and roughly <span class="num">73%</span> of OSAT revenue is concentrated in Asia. ASE and Amkor together hold more than <span class="num">40%</span>, and the top three hold more than <span class="num">60%</span>. Trade friction is pushing a dispersion toward Malaysia, Vietnam, and the Philippines. Even TSMC outsources some of packaging's simpler steps to ASE and Amkor. That the bottleneck has shifted to the back end also means it is concentrated in particular regions and a handful of firms.</p><h2 id="sec-5">The Control Line Extended to HBM</h2><p>When value and the bottleneck gather in the back end, that point becomes geopolitical leverage. Until now, semiconductor controls against China centered on front-end lithography equipment like EUV scanners. That equipment control stays in place—and the control line has extended one layer further, onto a back-end product.</p><p>In December <span class="num">2024</span>, the U.S. Commerce Department's BIS blocked exports of advanced HBM to China at the national level for the first time. The threshold: memory bandwidth density above <span class="num">2GB</span>/s/mm². The aim is to slow China's capacity to produce AI chips. The EUV-equipment control (front end) stays untouched, and a new product control was added on HBM—a back-end stacked memory. Just before the control took effect, Chinese firms including Huawei were reported to have stockpiled roughly <span class="num">7</span> million Samsung HBM units (estimated at over <span class="num">$1</span> billion). The side trying to block and the side trying to stockpile had made the same judgment about what the target was.</p><p>A target draws a fierce contest for share. In the second quarter of <span class="num">2026</span>, the HBM market stood at SK Hynix <span class="num">62%</span>, Micron <span class="num">21%</span>, and Samsung <span class="num">17%</span>—Micron overtaking Samsung. Full HBM4 production begins in the third quarter of <span class="num">2026</span>, and SK Hynix is projected to take the majority of the HBM4 volume going into Nvidia's next-generation accelerators.</p><div class="tablewrap"><table><thead><tr><th>Center of gravity</th><th>Old view (front end)</th><th>Now (back end)</th><th>Basis</th></tr></thead><tbody><tr><td>Performance engine</td><td>Transistor scaling</td><td>Integration (hybrid bonding, ~100x areal density)</td><td>IRDS, TSMC</td></tr><tr><td>Margin</td><td>Node scaling, foundry unit price</td><td>HBM high margin, SK Hynix <span class="num">72%</span> OPM</td><td>Yole, SK Hynix</td></tr><tr><td>Bottleneck</td><td>Wafer starts</td><td>CoWoS allocation sold out</td><td>siliconanalysts, oplexa</td></tr><tr><td>Control target</td><td>EUV equipment (still in force)</td><td>HBM/packaging product control added</td><td>BIS, CSIS</td></tr></tbody></table></div><p><em>Table sources: same as each section above (see ## Sources below). The geopolitics row is an "addition," not a "shift" (EUV control retained + HBM control newly created).</em></p><p>A line has to be drawn clearly, though. The back end has not replaced the front end. HBM, and the logic die placed on top of CoWoS, are in the end products the front end printed, and the front end's leading-edge nodes are just as sold out. More precisely, the center of gravity tipped not toward a single process step called 'the back end' but toward two distinct points—memory (HBM) and integration (packaging). What changed is the value chain's center of gravity. The last step that lifts performance, and the margin, bottleneck, and leverage that step generates, moved from etching transistors to integrating dies.</p><p>So the signals to watch when reading AI silicon change too. As much as how many nanometers the process node is, it now matters just as much who got how much packaging allocation, how HBM share is moving, and where the export-control line is drawn.</p><p>Go one step further: that the center of gravity "moved" means it converged on a few integration players. Performance, margin, bottleneck, and control leverage condense into TSMC's packaging, SK Hynix's HBM, and a handful of Asia-concentrated OSATs. Who holds those positions creates more pricing power than a node race like N2—and, at the same time, greater single-point-of-failure risk. The node-scaling headline is closer to a lagging indicator.</p><p>The question that remains is whether this convergence is structural or a passing feature of the AI cycle's peak. SK Hynix's <span class="num">72%</span> operating margin may be a cycle peak that mean-reversion is hard to escape. Whether this shift reverses depends on how fast CoWoS expansion catches up to demand, when the HBM forward contracts expire, and when the sellout clears. The 'back' in back end, at least for now, marks order, not importance.</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li>imec, "Is Moore's law dead?" (IRDS · More than Moore) — https://www.imec-int.com/en/semiconductor-education-and-workforce-development/microchips/moores-law/moores-law-dead (as-of 2026-06)</li><li>WikiChip, "Chip-on-Wafer-on-Substrate (CoWoS) — TSMC" — https://en.wikichip.org/wiki/tsmc/cowos (as-of 2026-06)</li><li>Tom's Hardware, "TSMC SoIC 3D stacking roadmap … 6-micron to 4.5-micron in 2029" (primary: TSMC announcement) — https://www.tomshardware.com/tech-industry/semiconductors/tsmc-soic-3d-stacking-roadmap-outlines-path-from-6-micron-pitches-today-to-4-5-micron-in-2029-fujitsus-monaka-cpu-to-benefit-from-face-to-face-chiplet-stacking (as-of 2026-02)</li><li>PatSnap, "Chiplet interconnect tech 2026: UCIe, HBM4 &amp; packaging" (primary: UCIe Consortium) — https://www.patsnap.com/resources/blog/articles/chiplet-interconnect-tech-2026-ucie-hbm4-packaging/ (as-of 2026-06)</li><li>Yole Group, "Advanced packaging market set to reach $79.4 billion by 2030" — https://www.yolegroup.com/press-release/advanced-packaging-market-set-to-reach-79-4-billion-by-2030/ (2030 projection)</li><li>Digitimes, "CoWoS capacity emerges as AI bottleneck … 80% CAGR" — https://www.digitimes.com/news/a20260410VL204/packaging-capacity-tsmc-nvidia-demand.html (as-of 2026-04)</li><li>Silicon Analysts, "Foundry Allocation Status Q1 2026 (CoWoS sold out)" — https://siliconanalysts.com/analysis/foundry-allocation-status-q1-2026 (as-of 2026-Q1)</li><li>Digitimes, "TSMC expands CoWoS capacity with Nvidia booking over half for 2026-27" — https://www.digitimes.com/news/a20251210PD218/tsmc-cowos-capacity-nvidia-equipment.html (as-of 2025-12)</li><li>CNBC, "SK Hynix posts record first-quarter profit" (primary: SK Hynix earnings release) — https://www.cnbc.com/2026/04/23/sk-hynix-earnings-ai-memory-shortage-hbm-demand.html (as-of 2026-04-23)</li><li>Counterpoint Research, "Global DRAM and HBM Market Share: Quarterly" — https://counterpointresearch.com/en/insights/global-dram-and-hbm-market-share (as-of 2026-Q2, published 2026-06-08)</li><li>CSIS, "Understanding the Biden Administration's Updated Export Controls" (primary: U.S. Commerce Department BIS) — https://www.csis.org/analysis/understanding-biden-administrations-updated-export-controls (as-of 2024-12)</li><li>CNN Business, "What is high bandwidth memory and why is the US trying to block China's access to it?" — https://www.cnn.com/2024/12/08/tech/us-china-hbm-chips-hnk-intl (as-of 2024-12)</li><li>Mordor Intelligence, "OSAT Market" / TEEPTRAK, "Semiconductor OSAT backend 2027" — https://www.mordorintelligence.com/industry-reports/osat-market · https://teeptrak.com/en/semiconductor-osat-backend-taiwan-malaysia-vietnam-2027/ (as-of 2025)</li><li>3D InCites, "Affordable and Comprehensive Design-for-Test of 3D Stacking Die Devices" — https://www.3dincites.com/2024/02/affordable-and-comprehensive-design-for-test-of-3d-stacking-die-devices/ (as-of 2024-02)</li></ol></section><footer class="byline"><span class="ai-dot"></span><span>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</span></footer></article>]]></content:encoded></item>
<item><title>SK hynix Has Passed Samsung. The KOSPI Is Now Two Companies</title><link>https://refract.blog/en/posts/%EC%82%BC%EC%84%B1-%ED%95%98%EC%9D%B4%EB%8B%89%EC%8A%A4-%EC%BD%94%EC%8A%A4%ED%94%BC/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EC%82%BC%EC%84%B1-%ED%95%98%EC%9D%B4%EB%8B%89%EC%8A%A4-%EC%BD%94%EC%8A%A4%ED%94%BC/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Economy</category><description>On 22 June, SK hynix overtook Samsung Electronics to close at number one by market capitalization on the KOSPI — South Korea's benchmark equity index — at ₩2,07…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#2f6fb0"></span><span class="kx">Economy</span><span class="ksep">·</span><span class="kx">자산시장</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-27T19:16:58"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><div class="vcaveat"><span class="vc-l">Note</span><span>코스닥 '거울상'은 자금흐름 직접 데이터 없는 정성 가설로 한정(f22 제도사실로 무게 이동). 컨센서스 초과 정량 call(mid-cycle EPS PER)은 미보강 — 정성 가드로 대체.</span></div><h1 class="title">SK hynix Has Passed Samsung. The KOSPI Is Now Two Companies</h1><div class="body"><p class="lead">On 22 June, SK hynix overtook Samsung Electronics to close at number one by market capitalization on the KOSPI — South Korea's benchmark equity index — at ₩2,079tn. The first reversal in 25 years. Except this "number one" counts common stock only. Add Samsung Electronics' preferred shares (about ₩180tn) and Samsung in aggregate is ₩2,246tn, still first. A market where the ranking flips on how you count a single line of common stock. The wobble itself foreshadows what the KOSPI has become. The top four names are half the index — and those four converge to just two companies.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">Earnings Carry the Rally</a><a class="jump" href="#sec-2">But the Index Is Two Companies</a><a class="jump" href="#sec-3">Strength Invites Selling</a><a class="jump" href="#sec-4">The KOSDAQ Is Closer to a Mirror Image</a><a class="jump" href="#sec-5">So, What to Watch</a></nav><h2 id="sec-1">Earnings Carry the Rally</h2><p>First, to be clear: this rally is not a valuation bubble. In 1Q26 SK hynix posted revenue of ₩<span class="num">52</span>.6tn and operating profit of ₩<span class="num">37</span>.6tn. A <span class="num">72%</span> operating margin, its first quarter above ₩50tn in revenue, the largest in its history. Numbers delivered in Q1, nominally the off-season. AI and HBM (high-bandwidth memory) demand drove those numbers.</p><p>Absolute profit is larger at Samsung. Samsung Electronics' 1Q26 operating profit, on a single reported basis, was ₩<span class="num">57</span>.2tn — ahead of SK. That is a composite result spanning foundry, mobile, and commodity DRAM. And yet the market sided with SK. What it priced was not the size of the profit but the purity of the growth that HBM represents.</p><div class="tablewrap"><table><thead><tr><th>Metric</th><th>Samsung Electronics</th><th>SK hynix</th></tr></thead><tbody><tr><td>1Q26 operating profit</td><td>₩<span class="num">57</span>.2tn (reported basis)</td><td>₩<span class="num">37</span>.6tn (OPM <span class="num">72%</span>)</td></tr><tr><td>Business mix</td><td>Composite (foundry, mobile, memory)</td><td>Memory / HBM-focused</td></tr><tr><td>Forward PER (mid-May)</td><td><span class="num">6</span>.77x</td><td><span class="num">6</span>.79x, first crossover</td></tr><tr><td>Forward PER, <span class="num">3</span> months earlier</td><td><span class="num">8</span>.08x</td><td><span class="num">5</span>.28x</td></tr><tr><td>KOSPI market cap (<span class="num">22</span> Jun, common)</td><td>—</td><td>₩<span class="num">2</span>,079tn, #<span class="num">1</span></td></tr><tr><td>Including preferred</td><td>₩<span class="num">2</span>,246tn, #<span class="num">1</span></td><td>—</td></tr></tbody></table></div><p><span class="cap">Table: Samsung vs SK hynix. Profit scale to Samsung, growth premium to SK. Samsung's ₩<span class="num">57</span>.2tn is a single reported basis (med); SK's ₩<span class="num">37</span>.6tn is the confirmed earnings figure (high). Sources — each company's 1Q26 earnings release (<span class="num">2026-04</span>), brokerage-consensus forward PER (mid-May <span class="num">2026</span>), Korea Exchange market cap (<span class="num">2026-06</span>-22).</span></p><p>Three months ago the gap stood at Samsung <span class="num">8</span>.08x forward PER, SK <span class="num">5</span>.28x — <span class="num">2.80</span> points. It inverted in three months. Even after that, SK's <span class="num">12</span>-month forward PER sits in the 6x range, below the global semiconductor average. And it holds even though, over the past year and a half, SK's shares have risen <span class="num">2.6</span> times as much as Samsung's. This is a rally where earnings pulled the price up, not where the price ran ahead of earnings. The engine is the cycle in which memory rose from a <a class="wikilink" href="https://refract.blog/en/posts/%EB%B0%98%EB%8F%84%EC%B2%B4-%ED%9B%84%EA%B3%B5%EC%A0%95/">back-end</a> supporting act to the heart of the system (2Q HBM share: SK <span class="num">62%</span>, Micron <span class="num">21%</span>, Samsung <span class="num">17%</span>).</p><p>But the very fact that the forward PER looks low in the 6x range is a trap. The denominator — <em>forward earnings</em> — already sits on a cycle-peak operating margin of <span class="num">72%</span>. Memory earns most at the peak, which is exactly when the PER looks lowest. The moment it looks cheap is the top — the oldest trap in cyclicals. The strength is genuinely earnings-backed. But if those earnings are a cycle peak, a low forward PER is not a basis for comfort but the opposite. Valuation risk does not separate from cycle risk. As we'll see, the risk this piece records in the downside scenario — that "the <span class="num">72%</span> margin runs in reverse" — is the underside of today's cheap-looking PER.</p><h2 id="sec-2">But the Index Is Two Companies</h2><p>The trouble is that this strength does not resemble the index as a whole.</p><p>The combined weight of the KOSPI's top four names — Samsung Electronics, SK hynix, Samsung Electronics preferred, and SK Square — swelled from <span class="num">38.83%</span> on <span class="num">2</span> January to <span class="num">49.49%</span> on <span class="num">6</span> May. Half the index. But by issuer, these four tickers are only two. Samsung Electronics preferred is Samsung's preferred stock; SK Square is the SK-affiliated holding company that owns the stake in SK hynix. Half of a KOSPI that looked like "four-name diversification" actually converges to two companies. Concentration disguised as diversification. Buy an ETF wearing the KOSPI label and half of it is a bet on these two.</p><p>A single day, <span class="num">6</span> May, shows what that means. The KOSPI surged <span class="num">6.45%</span>, but <span class="num">200</span> names rose and <span class="num">679</span> fell. The index set off fireworks while three-quarters of the market sat in the red. The index did not rise; the handful of names that hold it up rose. This is a snapshot of one +<span class="num">6%</span>-plus mega-rally day, but the structure sets the direction. As long as the top four make up half the index (<span class="num">49.49%</span>, as of <span class="num">6</span> May), the KOSPI is not a thermometer of the Korean economy but a derivative levered to the HBM cycle.</p><h2 id="sec-3">Strength Invites Selling</h2><p>Here the most counterintuitive thing happens. <strong>The more the index rises, the more foreigners sell.</strong></p><p>This year foreigners have net-sold roughly ₩120tn of Korean equities. In May alone the figure topped ₩44tn, and selling pressure carried into June. Numbers like these usually read as "foreigners are bearish on Korea." Yet the core driver the Street points to is not a bearish outlook but rebalancing. For global pension funds and asset managers that hold country weights constant, a sharp rally in Korean equities pushes Korea's weight in the portfolio past target. They then have to trim Korean stock mechanically. Selling out of strength.</p><p>Rebalancing is only one reading, the one that sits comfortably at home. To a foreign manager measuring returns in dollars, the won at <span class="num">1,540</span> per dollar is an FX loss that eats won-denominated returns, and hedging cost, the Korea discount — the long-standing gap at which Korean equities trade below global peers — and active de-risking pile onto the selling. ₩120tn YTD is not a figure that weight adjustment alone explains.</p><p>The exit is the exchange rate. On a weekly closing basis on <span class="num">24</span> June, the won passed <span class="num">1,540</span> per dollar for the first time in <span class="num">17</span> years and approached <span class="num">1,550</span> intraday. Foreign net selling of ₩11tn over the last four sessions drove that move. The Bank of Korea's policy rate, held at <span class="num">2.5%</span> for an eighth consecutive meeting (as of the May <span class="num">2026</span> meeting, against a hawkish Fed), offers little rate incentive to keep departing capital from leaving.</p><p>A weak won does not work in only one direction. Samsung and SK are exporters that book revenue in dollars, so the same <span class="num">1,540</span> inflates their won-translated earnings. Part of the very earnings that made the rally comes from this exchange rate. The currency is at once the exit draining capital from the index and the entrance feeding the chip profits that hold the index up. It cuts the same concentration both ways.</p><div class="tablewrap"><table><thead><tr><th>Actor</th><th>June action</th><th>Signal (as-of)</th></tr></thead><tbody><tr><td>Foreigners</td><td>Net sell (YTD ≈ ₩120tn)</td><td>Strength rebalancing, FX loss, de-risking (June)</td></tr><tr><td>Pension funds</td><td>Net sell ₩<span class="num">2</span>.31tn</td><td>Largest monthly in <span class="num">5</span> years, since Apr <span class="num">2021</span> (June)</td></tr><tr><td>Individuals</td><td>Net buy</td><td>Absorbing foreign / institutional supply (mid-June)</td></tr><tr><td>Won/dollar</td><td>Past <span class="num">1,540</span></td><td><span class="num">17</span>-year high, <span class="num">1,560</span> cited (<span class="num">24</span> Jun)</td></tr></tbody></table></div><p><span class="cap">Table: supply and demand inside a bull market. The big holders sell, individuals absorb. Sources — Korea Exchange investor-type trading (<span class="num">2026-06</span>), Seoul FX market (<span class="num">2026-06</span>-24).</span></p><p>Pension funds, too, net-sold ₩<span class="num">2</span>.31tn in June — the largest monthly figure since April <span class="num">2021</span>, five years. Foreigners sell into strength for weight reasons, pensions for profit-taking, and individuals absorb the supply. It is supply that stops once weights return to target, but the higher the index climbs, the more supply piles up to be reversed. That is why the market calls this "the paradox of the rising market."</p><p>Within June the center of gravity of that same foreign selling shifted once. Just two weeks earlier, on <a class="wikilink" href="https://refract.blog/en/posts/%EA%B8%88%EB%A6%AC%EC%9D%B8%ED%95%98-%EC%A2%8C%EC%A0%88/"><span class="num">8</span> June</a>, the KOSPI hit a -8.<span class="num">37%</span> circuit breaker as Samsung and SK fell about <span class="num">10%</span> each and the won was pushed to <span class="num">1,560</span> per dollar. Then the main driver was risk-off flight on a hawkish Fed and Middle East oil. Two weeks on, the same foreign selling and the same won weakness carried a larger share of rebalancing into the rally. That does not mean risk-off was gone: on <span class="num">26</span> June the KOSPI slumped again, -5.<span class="num">8%</span>, accompanied by a sidecar — a halt on program trading — and a circuit breaker. Inside the late-June foreign selling, rebalancing and risk-off were intermixed, and the <span class="num">26</span> June plunge is the evidence of that mixture. So read the direction off the single headline "foreigners are selling" and you read it wrong. You have to first separate what they are selling for.</p><h2 id="sec-4">The KOSDAQ Is Closer to a Mirror Image</h2><p>The shadow of this concentration is the KOSDAQ — Korea's tech-and-small-cap secondary exchange. We read "the KOSPI advances while the KOSDAQ falls" as a decoupling of two markets, but the two are the entrance and exit of a single flow. The relative vacuum left by capital sucked into large-cap semiconductors shows up in the KOSDAQ. This is not data that directly shows the capital moving; it is a reading that follows from the structure of the concentration, and I will not pin down the KOSDAQ's June level here.</p><p>The institutional side is what's well-supported. The KOSDAQ promotion-relegation system under discussion (a "premium," or first-division, league) is estimated to raise the semiconductor weight in the KOSDAQ150 from <span class="num">28.5%</span> to <span class="num">50.0%</span> in the premium market, and to cut healthcare from <span class="num">28.2%</span> to <span class="num">23.7%</span>. The market's structure is being redesigned to load in more semiconductor weight. A signal that the concentration is hardening past transient flow into index design.</p><h2 id="sec-5">So, What to Watch</h2><p>KOSPI <span class="num">8,900</span> is not a signal that the Korean economy has improved. And that <span class="num">8,900</span> is not even the current coordinate. It broke <span class="num">8,900</span> on <span class="num">18</span> June, right after a hawkish FOMC, but gave back roughly <span class="num">5%</span> from the high — <span class="num">8,471</span> on <span class="num">24</span> June, <span class="num">8,411</span> on <span class="num">26</span> June, with a sidecar and circuit breaker. At publication the index is not <span class="num">8,900</span> but in the <span class="num">8</span>,400s — and two circuit breakers (<span class="num">8</span> June -8.<span class="num">37%</span>, <span class="num">26</span> June -5.<span class="num">8%</span>) have each made that fragility real once. This number is not a coordinate for the whole Korean economy but a coordinate for two companies. The semiconductor cycle is one axis tied to the real economy through exports and capex, but the index does not represent that whole real economy. What ultimately sets the coordinate is not any macro indicator but the direction of the HBM cycle.</p><p>One more thing. Even that <span class="num">8,900</span>, converted into dollars, dulls the sense of a record. With the won at its weakest in <span class="num">17</span> years, the KOSPI a foreigner sees has not risen as much as the won-denominated record. A good part of the "all-time high" has evaporated in the exchange rate.</p><p>So the outlook is better seen as branches than as a verdict.</p><div class="tablewrap"><table><thead><tr><th>Scenario</th><th>Trigger</th><th>Mechanism</th></tr></thead><tbody><tr><td>Upside</td><td>HBM4 ramp + Samsung share recovery</td><td>Samsung begins volume HBM4 supply to Nvidia's "Vera Rubin" (<span class="num">3.3TB</span>/s). But Samsung today is third at <span class="num">17%</span>, behind even Micron (<span class="num">21%</span>), so a return to the <span class="num">30</span>%s is a large jump on the forecasts. If demand holds, the whole Korean memory pie expands.</td></tr><tr><td>Downside</td><td>Memory cycle / demand reversal</td><td>The operating leverage that produced the <span class="num">72%</span> margin runs in reverse. A slowdown in hyperscaler AI capex, or single-customer concentration on Nvidia, is the trigger. A multi-vendor field — Samsung's return plus Micron's ramp — drags down HBM ASP and margin. With half the index in semiconductors (<span class="num">49.49%</span>, <span class="num">6</span> May), it all falls together. Won weakness and foreign outflow persist on the rate gap, independent of the cycle.</td></tr><tr><td>Uncertainty</td><td>HBM4 share allocation</td><td>UBS forecasts SK takes ~<span class="num">70%</span> of Rubin's HBM4; Counterpoint forecasts Samsung's recovery to the <span class="num">30</span>%s. The split between the two decides the fate of the two market caps. That the index's largest weight (Samsung) is third in HBM is the index's asymmetric risk.</td></tr></tbody></table></div><p><span class="cap">Table: scenarios, not a verdict. All are verifiable propositions; which one held will be settled as HBM4 volume production proceeds. Sources — Samsung announcement, UBS, Counterpoint (<span class="num">2026</span>, forecast), SK 1Q26 earnings (<span class="num">2026-04</span>), KRX (<span class="num">2026-05</span>~<span class="num">06</span>). Not investment advice.</span></p><p>The reader's order of checks follows from this. Watch three exposures rather than the KOSPI level. First, the HBM cycle. Is my position a function of memory's cycle? Second, the won. As long as foreign rebalancing continues, won weakness proceeds independently of the index. Third, concentration. Is the KOSPI index you believed to be "Korea diversification" actually a position that stakes half on a single semiconductor bet? This concentration has produced passive holders' return so far, and the same concentration is their risk.</p><p>The strength is real and the fragility is real. They are the same fact. One concentration — that half the index is two companies — both makes this rally and imperils it. So the next time you see the headline "KOSPI all-time high," ask once more. Did Korea rise, or did two companies rise — and only in won?</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li>SK hynix 1Q26 results (revenue ₩52.6tn, op. profit ₩37.6tn, OPM 72%) — SK hynix earnings release, 2026-04 · via <a href="https://news.skhynix.co.kr/q1-2026-business-results/" target="_blank" rel="noopener noreferrer">SK hynix Newsroom</a>, <a href="https://www.thelec.kr/news/articleView.html?idxno=55559" target="_blank" rel="noopener noreferrer">TheElec</a></li><li>Samsung Electronics 1Q26 results (revenue ₩133.87tn, op. profit ₩57.2tn, single reported basis) — Samsung Electronics earnings release, 2026-04 · via <a href="https://www.thelec.kr/news/articleView.html?idxno=55934" target="_blank" rel="noopener noreferrer">TheElec</a></li><li>Forward PER crossover (SK 6.79 vs Samsung 6.77; 3 months earlier 8.08 vs 5.28) — brokerage consensus, mid-May 2026 · via <a href="https://newsroom.stockplus.com/breaking-news/16174" target="_blank" rel="noopener noreferrer">Stockplus</a>, <a href="https://www.sedaily.com/article/20043830" target="_blank" rel="noopener noreferrer">Seoul Economic Daily</a></li><li>SK hynix #1 by market cap (common stock ₩2,079tn, first in 25 years) / Samsung ₩2,246tn including preferred — Korea Exchange, 2026-06-22 · via <a href="https://zdnet.co.kr/view/?no=20260622153943" target="_blank" rel="noopener noreferrer">ZDNet Korea</a>, <a href="https://news.nate.com/view/20260622n30754" target="_blank" rel="noopener noreferrer">Nate</a>, <a href="https://www.lcnews.co.kr/news/articleView.html?idxno=203804" target="_blank" rel="noopener noreferrer">LCNews</a></li><li>SK up 2.6x Samsung over 1.5 years — Korea Exchange · via <a href="https://www.fnnews.com/news/202606211734200249" target="_blank" rel="noopener noreferrer">FN News</a></li><li>Top-4 weight 49.49% (5/6), breadth (+6.45% day, 200 up / 679 down), KOSDAQ promotion-relegation system — Korea Exchange, 2026-05~06 · via <a href="https://www.shinyoung.com/files/20260127/f2f1c34945b57.pdf" target="_blank" rel="noopener noreferrer">Shinyoung Securities strategy report</a>, <a href="https://www.fnnews.com/news/202606221135312729" target="_blank" rel="noopener noreferrer">FN News</a></li><li>KOSPI total market cap ₩6,706tn, index levels (6/18 break above 8,900 ~ 6/26 8,411) — Korea Exchange, 2026-06 · via <a href="https://www.indexergo.com/series/?frq=D&amp;idxDetail=20200" target="_blank" rel="noopener noreferrer">INDEXerGO</a>, <a href="https://www.newspim.com/news/view/20260618000222" target="_blank" rel="noopener noreferrer">Newspim</a></li><li>6/8 KOSPI -8.37% circuit breaker, won/dollar 1,560 — KRX, Seoul FX, 2026-06-08 · via <a href="https://www.tradingkey.com/analysis/stocks/more/261951350-kospi-crash-circuit-breaker-samsung-sk-hynix-broadcom-guidance-fed-hikes-retail-leverage-krw-outflow-tradingkey" target="_blank" rel="noopener noreferrer">TradingKey</a></li><li>Foreign net selling (YTD ₩120tn, May ₩44tn), rebalancing, won 17-year high at 1,540 — Korea Exchange, Seoul FX, 2026-06 · via <a href="https://biz.newdaily.co.kr/site/data/html/2026/06/09/2026060900111.html" target="_blank" rel="noopener noreferrer">Newdaily Biz</a>, <a href="https://www.polinews.co.kr/news/articleView.html?idxno=735265" target="_blank" rel="noopener noreferrer">Polinews</a>, <a href="https://www.hankyung.com/article/2026062461401" target="_blank" rel="noopener noreferrer">Hankyung</a></li><li>Pension funds June net sell ₩2.31tn (5-year high), individuals net buy — Korea Exchange, 2026-06 · via <a href="https://www.sedaily.com/article/20059921" target="_blank" rel="noopener noreferrer">Seoul Economic Daily</a></li><li>Bank of Korea policy rate 2.5% (8 consecutive holds, as of the May 2026 meeting) — Bank of Korea, 2026-05 · <a href="https://www.bok.or.kr/portal/singl/baseRate/list.do?dataSeCd=01&amp;menuNo=200643" target="_blank" rel="noopener noreferrer">policy rate history</a></li><li>HBM share 2Q26 (SK 62, Micron 21, Samsung 17) — Counterpoint, 2026-06-08 · <a href="https://counterpointresearch.com/en/insights/global-dram-and-hbm-market-share" target="_blank" rel="noopener noreferrer">Counterpoint</a></li><li>HBM4 volume production, Samsung Rubin supply (3.3TB/s), share forecasts (UBS, Counterpoint) — Samsung announcement, UBS, Counterpoint, 2026-05~06 · via <a href="https://www.e-focus.co.kr/news/articleView.html?idxno=3002439" target="_blank" rel="noopener noreferrer">E-Focus</a>, <a href="https://www.g-enews.com/article/Global-Biz/2026/05/202605080644316380fbbec65dfb_1" target="_blank" rel="noopener noreferrer">Global Economic</a></li></ol></section><footer class="byline"><span class="ai-dot"></span><span>This piece was analyzed and verified across multiple dimensions with AI, and reviewed by a human editor.</span></footer></article>]]></content:encoded></item>
<item><title>Bitcoin ETFs: The Outflows Stopped, the Price Won't Follow</title><link>https://refract.blog/en/posts/%EB%B9%84%ED%8A%B8%EC%BD%94%EC%9D%B8-etf-%EC%9E%90%EA%B8%88/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EB%B9%84%ED%8A%B8%EC%BD%94%EC%9D%B8-etf-%EC%9E%90%EA%B8%88/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Economy</category><description>The longest redemption run since launch. From 15 May to 3 June, the U.S. spot Bitcoin ETFs bled roughly $4.4 billion over 13 straight trading days—the longest s…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#2f6fb0"></span><span class="kx">Economy</span><span class="ksep">·</span><span class="kx">자산시장</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-27T16:30:44"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><h1 class="title">Bitcoin ETFs: The Outflows Stopped, the Price Won't Follow</h1><div class="body"><p class="lead">The longest redemption run since launch. From 15 May to 3 June, the U.S. spot Bitcoin ETFs bled roughly $4.4 billion over 13 straight trading days—the longest streak since they listed in January 2024. Now that the redemptions have eased, the price has not climbed back. On 24 June Bitcoin sat at about $62,729, below the roughly $63,800 it held on 5 June when the outflows stopped. The real story is elsewhere. Flows turn green and the price still drifts down—a gap that is not coincidence but structure.</p><p>First, flow and price on one chart.</p><div class="tablewrap"><table><thead><tr><th>Date</th><th>ETF net flow (category)</th><th>Bitcoin price</th></tr></thead><tbody><tr><td><span class="num">5</span>/<span class="num">15–6</span>/<span class="num">3</span> (<span class="num">13</span> days)</td><td><strong>approx -$<span class="num">4.4</span> billion</strong> · longest redemption streak since launch</td><td>—</td></tr><tr><td><span class="num">6</span>/<span class="num">5</span></td><td>+<span class="num">$3.05</span> million · first net inflow in <span class="num">13</span> days, almost entirely IBIT</td><td>approx <span class="num">$63,800</span></td></tr><tr><td><span class="num">6</span>/<span class="num">12</span></td><td>+<span class="num">$85.85</span> million · all <span class="num">12</span> funds positive, <span class="num">2</span>/<span class="num">3</span> IBIT</td><td>—</td></tr><tr><td><span class="num">6</span>/<span class="num">18</span> (weekly)</td><td>weekly -$<span class="num">227</span> million · -87% from peak · but June is a 6th straight week of net outflow, MTD approx -$<span class="num">2.1</span> billion</td><td>—</td></tr><tr><td><span class="num">6</span>/<span class="num">23</span></td><td>+<span class="num">$39.2</span> million · daily turn signal</td><td>—</td></tr><tr><td><span class="num">6</span>/<span class="num">24</span></td><td>—</td><td>approx <span class="num">$62,729</span> · approx -1.<span class="num">7%</span> vs <span class="num">6</span>/<span class="num">5</span></td></tr></tbody></table></div><p><em>Flows = aggregate of the U.S. spot Bitcoin ETF category (BlackRock's IBIT and others). Sources: CoinDesk, Blockmedia, news.bitcoin.com, CoinStats tallies; as-of <span class="num">2026-05</span>-15–<span class="num">06-24</span>.</em></p><p>Read the table down its columns: the flow column turns from red to green while the price column settles one notch lower. That mismatch is the whole of this piece.</p><p>Over the <span class="num">13</span> days of redemptions, the category's aggregate assets under management slid from about <span class="num">$104.29</span> billion to <span class="num">$80.40</span> billion, and the Bitcoin those funds held shrank to roughly <span class="num">1.277</span> million coins. At the center of the bleed sat a single fund: BlackRock's IBIT. IBIT alone shed more than <span class="num">$2.7</span> billion in net outflows over five weeks; on one tally its worst week ran about <span class="num">$980</span> million, with a single day losing roughly <span class="num">$448</span> million—the largest one-day outflow for any fund in the category. Then, into June, the bleeding eased: aggregate weekly outflows fell from <span class="num">$1.72</span> billion to <span class="num">$316</span> million to <span class="num">$227</span> million, an <span class="num">87%</span> collapse from the peak. One thing to keep straight, though. Even with daily inflows back, June was a sixth consecutive week of net outflow, and the month-to-date total still ran about -$<span class="num">2.1</span> billion. The money has not fully returned; the pace of the bleed has only slowed, and sharply.</p><p><strong>Out via IBIT, in via IBIT.</strong></p><blockquote><p>Of the category's roughly <span class="num">$2.44</span> billion in net inflows in April, <span class="num">$1.71</span> billion belonged to IBIT alone—about <span class="num">70%</span>. The metric called "Bitcoin ETF flows" is, in practice, close to "IBIT's flows."</p></blockquote><p>If the other funds are the choir, BlackRock carries the melody. A convenient signal, and a fragile structure. Let a handful of one fund's institutional clients turn their position and the whole category's direction flips—which is exactly how much this "flow" wobbles, closer to noise than to signal.</p><p><strong>And yet better flows did not lift the price.</strong> Weekly outflows shrank <span class="num">87%</span>, and on <span class="num">23</span> June daily flow swung back to a <span class="num">$39.2</span> million net inflow—yet the price settled at <span class="num">$62,729</span>, below the <span class="num">$63,800</span> mark where the redemptions had ended. Not a crash. At roughly <span class="num">1.7%</span>, the gap sits inside ordinary volatility. The point is not the size but the direction. The bull case assumed that once the bleeding stops the price firms up; across this stretch, that assumption did not hold.</p><p>Go one layer deeper and the assumption looks loose from the start. A large share of weekly ETF "inflows" is not conviction that Bitcoin will rise. It is arbitrage. Buy the spot ETF and sell an equal size of CME Bitcoin futures—a delta-neutral basis trade in which the ETF long and the futures short cancel each other's price exposure and the position pockets only the rate spread (the basis) between them, made possible at scale by the ETF's arrival. On the data this registers as the same "ETF net inflow," but it is neutral to Bitcoin's price, and when the basis narrows it unwinds at once and flows back out as "outflow." In practice, weekly ETF flows moved with leveraged funds' new futures shorts at a correlation of <span class="num">0.70</span>, and about half of the variance in weekly flows was explained by those new shorts alone. One analysis settled it: using weekly returns to predict ETF flows came out "statistically indistinguishable from zero." Flows returning without the price following is not a bug but a design—because half of the weekly flow was never a price signal to begin with.</p><p>That does not make ETF demand a phantom. The same analysis puts the arbitrage net position at only about <span class="num">$1</span> billion of the roughly <span class="num">$55</span> billion accumulated since launch, with the rest steady directional buying. What churns with the basis is the <em>weekly</em> flow. The <em>cumulative</em> base holds. So one analyst reads this outflow not as panic but as cyclical profit-taking—institutional demand's floor intact, with rational profits taken once the macro turned. On a cumulative view that holds up. Net inflows into the category since launch still exceed <span class="num">$58.7</span> billion, and IBIT's assets alone top <span class="num">$66</span> billion. Losing <span class="num">$4.4</span> billion over <span class="num">13</span> days did not break the base. Over the long run this <span class="num">$58.7</span> billion has underwritten the bull market, and across that span flows moved in the same direction as the price.</p><p><strong>So where is the price ceiling pinned?</strong> Outside the ETFs. The <span class="num">24</span> June decline was not about redemptions. It reads as the market pricing in a global tech-stock selloff and Fed expectations that had tilted hawkish again. The Fed pulling back this year's cut expectations I've set out separately (<a class="wikilink" href="https://refract.blog/en/posts/%EA%B8%88%EB%A6%AC%EC%9D%B8%ED%95%98-%EC%A2%8C%EC%A0%88/">rate cuts deferred</a>). The ceiling on risk assets is pressed down there. One more thing layers on top. Over the same stretch that Bitcoin ETFs were losing money, altcoin ETFs were drawing it in. XRP ETFs took in <span class="num">$106.6</span> million over seven straight weeks of net inflows, HYPE pulled <span class="num">$27.95</span> million, and Solana swung from outflow to inflow. The money had not left crypto. It had only changed seats, from Bitcoin to alts. Bitcoin's price was unusually heavy because the macro ceiling and this rotation worked on it together. Read "Bitcoin ETF outflow = exit from crypto" and you have seen only half.</p><p>So how should this outflow be read? Read the end of the outflows as a price bottom and you have misread it. June's data says as much—flows began to turn and the price did not follow. More precisely: using the <em>weekly</em> ETF-flow number as a trade trigger at all is mistaking noise for signal. Half of that number is the inhale and exhale of basis arbitrage, and a handful of one fund's (IBIT's) institutional clients move it. An investor with a long horizon should watch three things before next week's net-inflow headline. Whether the cumulative base breaks. Whether the basis has narrowed enough to force unwinds. And when the Fed lifts that ceiling. The ceiling hangs on rates and rotation, not on ETF flows.</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li>13-day -$4.4 billion outflow streak, end of streak, first net inflow — CoinDesk, "Bitcoin and Ether ETFs end record multi-billion outflow streak" (2026-06-05) / MetaMask News, market-structure overview (2026-06)</li><li>6/12 net inflow, all 12 funds positive — news.bitcoin.com (2026-06), CoinReaders (2026-06-12)</li><li>Weekly outflow -87% collapse, 6th straight week of net outflow, alt-ETF rotation — Blockmedia (2026-06-18)</li><li>IBIT 5-week loss, largest single-day outflow, cumulative $58.7 billion, $66 billion AUM, "cyclical profit-taking" reading — Investing.com, "Bitcoin's $3.4B ETF bleed looks more cyclical than structural" (2026-06) / spotedcrypto, nestree IBIT tallies (2026-06)</li><li>AUM, holdings, April IBIT 70% concentration — spotedcrypto/nestree tallies (2026-04~06)</li><li>Price ($63,800, $62,729), 6/23 turn signal, 6/24 hawkish repricing — CoinStats (2026-06-24)</li><li><strong>Weekly ETF flow ≈ half basis arbitrage (correlation 0.70), cumulative is genuine directional</strong> — IOSG (Darko), "Bitcoin ETF Flows Are Driven by Arbitrage, Not Belief" (MetaEra; via KuCoin News, 2026-06)</li><li><strong>Delta-neutral cash-and-carry basis trade enabled by spot ETFs</strong> — CME Group OpenMarkets, "Spot ETFs Give Rise to Crypto Basis Trading" (2025)</li></ol></section><footer class="byline"><span class="ai-dot"></span><span>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</span></footer></article>]]></content:encoded></item>
<item><title>Before the Fed Rewrote Its Dot Plot, Korea's Market Had Already Broken</title><link>https://refract.blog/en/posts/%EA%B8%88%EB%A6%AC%EC%9D%B8%ED%95%98-%EC%A2%8C%EC%A0%88/</link><guid isPermaLink="true">https://refract.blog/en/posts/%EA%B8%88%EB%A6%AC%EC%9D%B8%ED%95%98-%EC%A2%8C%EC%A0%88/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Economy</category><description>On June 8, the KOSPI opened down 8.37% and tripped the circuit breaker. Samsung Electronics and SK Hynix bled 10% each, and the won slid toward 1,560 against th…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#2f6fb0"></span><span class="kx">Economy</span><span class="ksep">·</span><span class="kx">거시경제</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-27T16:31:33"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><h1 class="title">Before the Fed Rewrote Its Dot Plot, Korea's Market Had Already Broken</h1><div class="body"><p class="lead">On June 8, the KOSPI opened down 8.37% and tripped the circuit breaker. <a class="wikilink" href="https://refract.blog/en/posts/%EC%82%BC%EC%84%B1-%ED%95%98%EC%9D%B4%EB%8B%89%EC%8A%A4-%EC%BD%94%EC%8A%A4%ED%94%BC/">Samsung Electronics and SK Hynix</a> bled 10% each, and the won slid toward 1,560 against the dollar. The Fed did not erase "a cut this year" from its dot plot and switch hands to a hike until nine days later, on June 17. The order is backward. Korea's market knew the answer and moved on it before the Fed made it official.</p><p>Start with what the Fed did. It held the policy rate at <span class="num">3.5–3.75%</span>. The real event was the dot plot. The <span class="num">2026</span> median, which had pointed to a cut at <span class="num">3.4%</span> in March, climbed to <span class="num">3.8%</span> in June—flipping the whole direction—while any cut slid out to <span class="num">2027–2028</span>. The distribution is blunter still: <span class="num">8</span> for hold, <span class="num">1</span> for a cut, <span class="num">9</span> penciling in a hike. Seventeen of eighteen members saw inflation risk to the upside. Kevin Warsh, the new chair, trimmed guidance at his first meeting and left the door open to a hike. Underneath it: oil that jumped from <span class="num">$65</span> to <span class="num">$115</span> a barrel in three weeks on a Hormuz blockade, and supply-driven inflation back above <span class="num">2%</span>.</p><p>That is the headline. What matters is <em>which market the decision reaches, and at what speed.</em> The same shock keeps a different clock in each channel.</p><div class="tablewrap"><table><thead><tr><th>Channel</th><th>Speed</th><th>Signal · figure (as-of)</th><th>Arrival</th></tr></thead><tbody><tr><td>FX</td><td>Immediate</td><td>USD/KRW ~<span class="num">1,560</span>, foreign outflow (<span class="num">6</span>/<span class="num">8</span>)</td><td>✅ Arrived</td></tr><tr><td>Korean equities</td><td>Immediate</td><td>KOSPI −<span class="num">8.37%</span> · circuit breaker, Samsung · Hynix −<span class="num">10%</span> (<span class="num">6</span>/<span class="num">8</span>)</td><td>✅ Arrived</td></tr><tr><td>US short rates</td><td>Immediate</td><td><span class="num">2</span>-year +<span class="num">11bp</span> (intraday &gt;<span class="num">16bp</span>, largest Fed-day move since <span class="num">2008</span>) (<span class="num">6</span>/<span class="num">18</span>)</td><td>✅ Arrived</td></tr><tr><td>US credit spreads</td><td>Delayed</td><td>IG <span class="num">74bp</span> · HY <span class="num">267bp</span> = cycle low (19th %ile) (<span class="num">6</span>/<span class="num">22</span>)</td><td>⏳ Not yet priced</td></tr><tr><td>Corporate refinancing</td><td>Delayed</td><td>Maturity wall <span class="num">$1</span>.35T (<span class="num">2026</span>), body <span class="num">2027–28</span></td><td>⏳ In transit</td></tr><tr><td>Employment</td><td>Last</td><td>Private +117k/month, still strong (May)</td><td>⏳ Not yet arrived</td></tr></tbody></table></div><p><span class="cap">Table: One shock, arrival speed by channel. Sources — US SEP·UST (Federal Reserve / CNBC, <span class="num">2026-06</span>-18), KRX·FX (TradingKey, <span class="num">2026-06</span>-08), ICE BofA OAS (Mariemont, <span class="num">2026-06</span>-22), maturity wall (PitchBook·MarketMinute, <span class="num">2026</span>). As-of marked in each cell.</span></p><p><strong>The fast channels have already passed through Korean assets.</strong> When the US <span class="num">10</span>-year cleared <span class="num">4.5%</span> again, money drained out of risk assets, and the exit ran through the currency and the KOSPI. For an emerging market, a rise in US rates is a pump that pulls capital out. Won weakness and foreign selling are that pump's immediate output. This is why Korea's market moved ahead of the Fed—FX and equities do not wait for fundamentals; they reprice in real time to a single notch in the global rate.</p><p>Inside US Treasuries, too, the fast side and the slow side parted. On FOMC day the <span class="num">2</span>-year jumped <span class="num">11bp</span>—its intraday move the largest on a Fed meeting day since March <span class="num">2008</span>—while the <span class="num">10</span>-year sat near <span class="num">4.47%</span>, barely budged. The short end screams and the long end is pinned: a textbook flattening. The market has priced "tighter now, but cooling the economy in the end."</p><p><strong>The slow channels are still asleep.</strong> FX and equities are screaming this loud, and the US credit market is unmoved. Investment-grade spreads sit at <span class="num">74bp</span> and high-yield at <span class="num">267bp</span>—both parked at a cycle low, the 19th percentile. That is a price that pays almost nothing for policy risk. Against one shock, one market points to a circuit breaker and the other to calm.</p><p>Why this gap cannot hold is written into the refinancing calendar. <span class="num">$1.35</span> trillion in nonfinancial corporate bonds mature this year, and the body of the maturity wall stacks up in <span class="num">2027–2028</span>. This is the stretch where cheaply borrowed money comes back at expensive rates. A company whose borrowing cost has risen cuts capital investment and expansion first; the weight then descends into earnings, and last of all into hiring. Employment still running at +117k a month is not a reassuring signal—it is the channel that arrives last in this chain.</p><p>So the reader's question has to move off the timing of a cut. <strong>Will the credit market end up following the risk that FX and equities have already priced, or will FX and equities turn out to have overreacted?</strong> This is not a matter of taste but a proposition that gets tested. Pass through the <span class="num">2027–2028</span> maturity wall with high-yield spreads still at today's lows, and the slow channel refinanced harmlessly; let spreads blow out to stress levels, and the second shoe has dropped. Which of the two it was becomes clear only after the fact.</p><p>The order of inspection follows from this. If you hold a bet on a cut, move the calendar to <span class="num">2027</span>. After that, it is not direction but <em>sensitivity</em>. Work down the list: assets exposed to the won, then sectors with heavy refinancing dependence, then long-duration positions. The losses in the fast channels are already booked. What is not yet decided is the slow channel—and credit spreads will show the answer first.</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li>Fed rate decision · statement (hold 3.5–3.75%, dot plot) — Federal Reserve press release, 2026-06-17 · via <a href="https://www.cnbc.com/2026/06/17/fed-interest-rate-decision-june-2026.html" target="_blank" rel="noopener noreferrer">CNBC</a>, <a href="https://www.stocktitan.net/articles/fed-rate-decision-june-17-2026" target="_blank" rel="noopener noreferrer">StockTitan</a></li><li>Dot-plot distribution · median (3.4→3.8) · upside risk 17/18 — Federal Reserve SEP, 2026-06-17 · via StockTitan, <a href="https://mariemontcapital.com/june-2026-fomc-meeting/" target="_blank" rel="noopener noreferrer">Mariemont Capital</a></li><li>Warsh's first meeting · guidance — 2026-06-17 · <a href="https://www.cnn.com/2026/06/17/business/live-news/federal-reserve-interest-rate-kevin-warsh" target="_blank" rel="noopener noreferrer">CNN</a>, <a href="https://www.cnbc.com/2026/06/18/treasury-yields-investors-warsh-fed-interest-rates.html" target="_blank" rel="noopener noreferrer">CNBC</a></li><li>Treasury curve (2yr +11bp · largest Fed-day move since 2008, 10yr flat, 2s10s flattening) — UST market, 2026-06-18 · <a href="https://www.cnbc.com/2026/06/18/treasury-yields-investors-warsh-fed-interest-rates.html" target="_blank" rel="noopener noreferrer">CNBC</a>, Mariemont</li><li>USD/KRW 1,560 · foreign outflow · KOSPI −8.37% circuit breaker · Samsung/SK Hynix −10% — KRX·FX, 2026-06-08 · <a href="https://www.tradingkey.com/analysis/stocks/more/261951350-kospi-crash-circuit-breaker-samsung-sk-hynix-broadcom-guidance-fed-hikes-retail-leverage-krw-outflow-tradingkey" target="_blank" rel="noopener noreferrer">TradingKey</a></li><li>Credit spreads (IG 74bp · HY 267bp, 19th percentile · multi-decade lows) — ICE BofA OAS, 2026-06-22 · Mariemont, <a href="https://www.briefs.co/news/hawkish-fed-could-squeeze-credit-spreads-near-multi-decade-lows/" target="_blank" rel="noopener noreferrer">Briefs</a></li><li>Corporate maturity wall ($1.35T 2026, body 2027–28, CRE $900B) · Middle East oil ($65→$115) — <a href="https://pitchbook.com/news/articles/2026-us-high-yield-outlook-volume-to-tick-higher-amid-looming-maturity-wall" target="_blank" rel="noopener noreferrer">PitchBook</a>, <a href="https://www.financialcontent.com/article/marketminute-2026-3-18-the-2026-credit-crunch-geopolitical-shocks-and-the-maturity-wall-collide" target="_blank" rel="noopener noreferrer">MarketMinute</a></li><li>High-rate → corporate transmission mechanism — <a href="https://www.usbank.com/investing/financial-perspectives/market-news/how-do-rising-interest-rates-affect-the-stock-market.html" target="_blank" rel="noopener noreferrer">U.S. Bank</a> · private employment recovery (+117k) — <a href="https://www.goodmorningamerica.com/news/story/jobs-report-set-show-hiring-slowdown-continued-2026-129990325" target="_blank" rel="noopener noreferrer">Good Morning America</a></li></ol></section><footer class="byline"><span class="ai-dot"></span><span>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</span></footer></article>]]></content:encoded></item>
<item><title>Passive Crossed Half the Market. Who Took Over the Judgment?</title><link>https://refract.blog/en/posts/%ED%8C%A8%EC%8B%9C%EB%B8%8C-%EC%9E%90%EB%B3%B8%EB%B0%B0%EB%B6%84/</link><guid isPermaLink="true">https://refract.blog/en/posts/%ED%8C%A8%EC%8B%9C%EB%B8%8C-%EC%9E%90%EB%B3%B8%EB%B0%B0%EB%B6%84/</guid><pubDate>Sat, 27 Jun 2026 09:00:00 +0900</pubDate><category>Economy</category><description>An index fund is not a promise to beat the market. It is a promise to buy it—to hold whatever the index holds, without asking what is dear and what is cheap. Fo…</description><content:encoded><![CDATA[<article><div class="kicker"><span class="dot2" style="background:#2f6fb0"></span><span class="kx">Economy</span><span class="ksep">·</span><span class="kx">자산시장</span><span class="ksep">·</span><span class="kx">2026.06.27</span></div><div class="verify"><span class="vmark" aria-hidden="true"></span><span class="vchip ok"><span class="vt">✓</span>Fact-checked</span><span class="vchip ok" title="pass@2026-06-28T00:11:46"><span class="vt">✓</span>Code-verified<span class="vsub">validate.py</span></span><span class="vpill ship">Published</span></div><div class="vcaveat"><span class="vc-l">Note</span><span>삼분구조 모티프(가격/무엇/감시)는 의도적 구조이며 4번째 차원(쏠림)이 깨줌; 반사성은 원인주장 아닌 해석으로 한정 — 둘 다 비차단 nit</span></div><h1 class="title">Passive Crossed Half the Market. Who Took Over the Judgment?</h1><div class="body"><p class="lead">An index fund is not a promise to beat the market. It is a promise to <em>buy</em> it—to hold whatever the index holds, without asking what is dear and what is cheap. For an individual, a sound choice: lower cost, instant diversification. But that promise <em>not to judge</em> has now crossed half of all fund assets. At the end of 2023, U.S. passive fund assets reached about $13.29 trillion and passed active funds (about $13.23 trillion) for the first time on record. The gap has widened since. That is where the problem starts. Someone still has to price securities and monitor companies—and the people who used to do it have stepped off the field. The judgment has not vanished. It has only changed seats. This piece follows where it went.</p><nav class="toc"><span class="toc-l">Contents</span><a class="jump" href="#sec-1">Who Sets the Price?</a><a class="jump" href="#sec-2">Who Decides What Gets Bought?</a><a class="jump" href="#sec-3">Who Monitors the Companies?</a><a class="jump" href="#sec-4">The Money That Could Lean Against Concentration Has Thinned</a><a class="jump" href="#sec-5">So, Who Took It On?</a></nav><p>First, the terrain in a few numbers.</p><div class="tablewrap"><table><thead><tr><th>Metric</th><th>Figure</th><th>As-of</th></tr></thead><tbody><tr><td>U.S. passive vs active fund assets</td><td>passive <strong><span class="num">$13</span>.29T</strong> &gt; active <span class="num">$13</span>.23T (first crossover on record)</td><td><span class="num">2023-12</span>-31</td></tr><tr><td>Passive share (after crossover)</td><td>above half · gap widening</td><td><span class="num">2024–25</span></td></tr><tr><td>S&amp;P <span class="num">500</span> top-10 weight by market cap</td><td>about <strong><span class="num">40.7%</span></strong> (record · ~<span class="num">19%</span> at end-2015)</td><td><span class="num">2025-12</span>-31</td></tr><tr><td>Big Three combined S&amp;P <span class="num">500</span> stake</td><td>about <strong><span class="num">20–22%</span></strong> (<span class="num">5.2%</span> in <span class="num">1998</span>)</td><td><span class="num">2017–2021</span></td></tr><tr><td>Big Three votes cast at S&amp;P <span class="num">500</span> meetings</td><td>about <strong><span class="num">25%</span></strong></td><td><span class="num">2018–2021</span></td></tr></tbody></table></div><p><em>Sources: Morningstar (assets), S&amp;P DJI · FactSet (concentration), Bebchuk &amp; Hirst (Big Three). As-of dates as labeled.</em></p><p>The numbers all point one way. Money pools into the "judgment-free" side, yet for the market to function someone must still judge. That judgment has relocated to three places: the desk that prices, the desk that decides what gets bought, and the desk that monitors companies.</p><h2 id="sec-1">Who Sets the Price?</h2><p>Passive money does not buy and sell on information. It buys because the index holds it. So the work of pricing—of impounding which stock is cheap and which is dear, i.e. price discovery—falls on the active investors who remain. The thinner that crowd, the fewer shoulders carry the burden of setting the price.</p><p>Here a <span class="num">40</span>-year-old theorem kicks in. In <span class="num">1980</span>, Grossman and Stiglitz proved that an informationally efficient market is impossible: if prices already reflect all information, the payoff to gathering it falls to zero, so no one gathers it, and prices lose their information again. The market must always keep someone digging. Active management cannot, in theory, go to zero. However large passive grows, price discovery does not disappear—it concentrates onto a few.</p><p>Whether that concentration has broken the market, the data does not speak with one voice. One study finds that as passive ownership rises, the degree to which prices pre-impound earnings fell about <span class="num">16%</span>, with a <span class="num">15</span>-percentage-point rise in passive ownership explaining <span class="num">33–40%</span> of that decline. Another points the opposite way: as indexing grows, information <em>production</em> clearly falls (Google searches −<span class="num">3.8%</span>, regulatory-filing views −<span class="num">14.1%</span>, analyst reports −<span class="num">10.8%</span>), yet price efficiency itself is statistically unchanged—because the remaining few active investors arbitrage prices back into line. The two findings reconcile on top of Grossman-Stiglitz. The <em>number of people</em> digging for price falls; the <em>function</em> of getting the price right holds up on fewer shoulders.</p><p>In <span class="num">2019</span> Michael Burry likened passive to the synthetic CDOs of the pre-crisis years, warning that "passive investing has removed price discovery from the equity markets." "Removed" is an overstatement. What the data supports is not removal but concentration. Concentration, though, carries its own bill. The thinner the shoulders holding the price, the thinner the countervailing judgment left to catch it when those few are wrong or pull out at once. The crowd riding the index takes the outcome without ever sitting in on the call.</p><h2 id="sec-2">Who Decides What Gets Bought?</h2><p>An index is not a fact of nature. Someone writes it. A handful of index providers—S&amp;P Dow Jones, MSCI, FTSE Russell—decide by rule which companies go in and which come out. Scholars argue these providers hold a "private authority" over capital allocation, a de facto gatekeeper power: constructing an index is not neutral engineering but a political choice. Because a single inclusion decision becomes a flow of money.</p><p>In December <span class="num">2020</span>, Tesla was added to the S&amp;P <span class="num">500</span>. It was the largest addition on record, and index funds had to buy roughly <span class="num">$90</span> billion of Tesla shares <em>mechanically</em>—regardless of any portfolio manager's view (an S&amp;P analyst estimate). The inclusion-day closing auction was the largest ever, with about <span class="num">69</span> million shares trading at <span class="num">$695</span>. One committee's decision forced tens of billions in buying. A rule change exerts the same force. When MSCI added mainland Chinese A-shares to its emerging-markets index in <span class="num">2018–2019</span> and raised the inclusion factor from <span class="num">2.5%</span> to <span class="num">20%</span>, that ratio adjustment alone moved passive money mechanically.</p><p>The judgment of "what to buy" is delegated here, to a rule. The index investor does not pick stocks. They have handed that work to the few committees who wrote the rule that picks them.</p><h2 id="sec-3">Who Monitors the Companies?</h2><p>The third desk is governance. To hold a stock is to bear the duty of monitoring management and casting a vote—but an index fund never sells, so it becomes a permanent shareholder. And those permanent shareholders have bunched into a few hands. BlackRock, Vanguard, and State Street—the Big Three—together hold about <span class="num">20–22%</span> of S&amp;P <span class="num">500</span> companies, nearly four times the <span class="num">5.2%</span> of <span class="num">1998</span>. Stronger than the stake is the vote. Because they vote nearly all of their shares while many retail holders do not, the Big Three actually cast about <span class="num">25%</span> of the votes at S&amp;P <span class="num">500</span> meetings. The authors project that share rising to about <span class="num">34%</span> within a decade and about <span class="num">41%</span> within two.</p><p>The man who understood this structure better than anyone sounded the alarm. Jack Bogle—Vanguard's founder, the inventor of the index fund—wrote in <span class="num">2018</span> that "it seems only a matter of time until index mutual funds cross the <span class="num">50%</span> mark," and that he did not believe such a concentration of corporate control in a few institutions "would serve the national interest." The warning of the designer watching his own tool cross a threshold.</p><p>There are attempts to hand it back. BlackRock introduced pass-through Voting Choice so clients can cast votes themselves. But the scale shows the delegation has only partly returned. Of <span class="num">$6.9</span> trillion in index-equity assets under management, <span class="num">$3.3</span> trillion is eligible to choose—yet clients who actually took up the vote represent about <span class="num">$784</span> billion, a quarter of the eligible pool. The rest is still voted by BlackRock's desk. Monitoring has not vanished. It is simply being carried, thinly, by a few stewardship desks splitting thousands of annual meetings among them.</p><h2 id="sec-4">The Money That Could Lean Against Concentration Has Thinned</h2><p>The top-10 weight of the S&amp;P <span class="num">500</span> reached about <span class="num">40.7%</span> at the end of <span class="num">2025</span>, a record—more than double the level of a decade earlier (about <span class="num">19%</span>) and well past the dot-com peak of <span class="num">2000</span> (about <span class="num">26%</span>). Passive did not create this concentration; above all it is the earnings and prices of those mega-cap tech names that lifted it. But by construction—cap-weighted—passive money buys the largest names more, in proportion to weight. Which means it never moves against the concentration. The countervailing judgment that trims what has grown dear and adds what has gone cheap thins out precisely as the market tilts one way. Not the hand that built the crowding, but the seat where the hand that could have stopped it is emptying out.</p><h2 id="sec-5">So, Who Took It On?</h2><p>That passive is the right choice for an individual does not change. The problem is the fallacy of composition. When one person's rational choice—to delegate judgment—becomes the majority's, the work of pricing and monitoring does not go vacant; it relocates to a few seats. Price is taken on by a thinning active fringe, what-to-buy by the rules of a few index providers, monitoring by the voting desks of the Big Three. The responder did not disappear; the response was delegated to a few.</p><p>The bill arrives when those few are wrong. When thin price discovery lets a mispricing stand, when one committee's inclusion rule herds money to one side, when a few stewards vote thousands of companies thinly. The crowd riding the index bears the result together, while its channel to weigh in on the call is structurally thin. The act of handing off always erases someone who answers (<a class="wikilink" href="https://refract.blog/en/posts/%EC%9E%90%EC%9C%A8%EB%AC%B4%EA%B8%B0-%EC%9C%84%EC%9E%84/">delegating lethal force</a>). What passive has erased is the dispersed responder who would have judged the price and the company.</p><p>For an investor with a long horizon, what matters is not next quarter's return. How far the passive share goes, how high the top-name concentration climbs, what the index providers' inclusion rules make the market buy and sell, and whether the few who hold the vote actually give it back—these are the larger variables. The judgment you delegated is being made for you right now, by someone. Knowing who that someone is—that, too, is part of index investing.</p></div><section class="sources"><div class="src-l">Sources</div><ol class="src-list"><li>U.S. passive fund assets pass active for the first time ($13.29T vs $13.23T) — Morningstar, "It's Official: Passive Funds Overtake Active Funds" (US Fund Flows, as-of end-2023) / via CNBC, "Passive investing rules Wall Street now…" (2024-01-18)</li><li>S&amp;P 500 top-10 weight about 40.7% (record at end-2025) · ~19% at end-2015 · ~26% at the 2000 dot-com peak — S&amp;P Dow Jones Indices · FactSet data (via RBC Wealth Management, "The Great Narrowing"; Pensions &amp; Investments; as-of 2025-12-31)</li><li>Big Three (BlackRock, Vanguard, SSGA) combined S&amp;P 500 stake about 20–22% (5.2% in 1998) · about 25% of votes cast · projected 34/41% — Bebchuk &amp; Hirst, "The Specter of the Giant Three" (Boston University Law Review, 2019) and "Big Three Power, and Why It Matters" (2022)</li><li>Impossibility of an informationally efficient market (theory anchor) — Grossman &amp; Stiglitz, "On the Impossibility of Informationally Efficient Markets," American Economic Review 70(3):393–407 (1980)</li><li>Rising passive ownership → price informativeness down about 16% (supporting evidence) — Marco Sammon, "Passive Ownership and Price Informativeness" (HBS / Review of Financial Studies)</li><li>Indexing lowers information production but leaves price efficiency unchanged (counter-evidence) — Coles, Heath &amp; Ringgenberg, "On Index Investing," Journal of Financial Economics (2022)</li><li>Index providers' "private authority" (de facto capital-allocation gatekeepers) — Petry, Fichtner &amp; Heemskerk, "Steering capital: the growing private authority of index providers," Review of International Political Economy 28(1):152–176 (2021)</li><li>Tesla added to S&amp;P 500 (2020-12-21) · ~$90 billion of mechanical buying (estimate) · closing auction ~69M shares at $695 — S&amp;P Dow Jones Indices / Bloomberg (2020-12)</li><li>MSCI emerging-markets inclusion of China A-shares (2018–2019) · inclusion factor 2.5%→20% — MSCI (via Driehaus)</li><li>BlackRock Voting Choice scale ($3.3T eligible of $6.9T index-equity AUM · about $784B participating) — BlackRock, "2025 Global Voting Spotlight" (as-of 2025-06-30, via Harvard Law corpgov)</li><li>Jack Bogle's warning ("only a matter of time…50% mark" · "[not] serve the national interest") — John C. Bogle, Wall Street Journal op-ed (2018-11-29)</li><li>Michael Burry, passive = synthetic CDO analogy · "removed price discovery" (opinion) — Michael Burry (Bloomberg interview, 2019-09-04; via CNBC)</li></ol></section><footer class="byline"><span class="ai-dot"></span><span>Analyzed and verified multi-dimensionally with AI; reviewed by the author.</span></footer></article>]]></content:encoded></item>
</channel>
</rss>
