<?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>TEN Brief</title>
  <link>https://tenbrief.com/en</link>
  <description>Ten verified stories a day</description>
  <language>en</language>
  <atom:link href="https://tenbrief.com/en/feed.xml" rel="self" type="application/rss+xml"/>
  <item>
    <title>Son takes All-Star MVP in 35 minutes</title>
    <link>https://tenbrief.com/en/2026/08/01/son-allstar-mvp</link>
    <guid isPermaLink="true">https://tenbrief.com/en/2026/08/01/son-allstar-mvp</guid>
    <pubDate>Sat, 01 Aug 2026 09:00:00 GMT</pubDate>
    <category>Sports</category>
    <description>Son scored twice in 35 minutes to win MLS All-Star MVP on 29 July</description>
    <content:encoded><![CDATA[<p>Son Heung-min played 35 minutes of the MLS All-Star Game on 29 July, scored twice inside three minutes, and left with the most valuable player award on his first appearance in the fixture. For a league still arguing about whether marquee signings translate into results, the more useful question is what the surrounding numbers say about his first year at LAFC.</p>
<h2 id="the-match">1. The match</h2>
<p>Both goals came early and close together — the 20th and 23rd minutes. He was withdrawn at the interval of a match designed around rotation, which is why the 35-minute figure appears in every account: two goals in that window is an unusually dense return even for an exhibition.</p>
<p>All-Star games are not evidence of much on their own. The reason this one is worth noting is that it sits inside a run rather than standing apart from it.</p>
<h2 id="the-season-so-far">2. The season so far</h2>
<div class="table-wrap"><table>
<thead><tr><th scope="col">Metric</th><th scope="col">Figure</th></tr></thead>
<tbody>
<tr><th scope="row">All-Star Game goals</th><td>2 in 35 minutes</td></tr>
<tr><th scope="row">Consecutive league games scored</th><td>3</td></tr>
<tr><th scope="row">Goals in all competitions</th><td>5</td></tr>
<tr><th scope="row">LAFC current run</th><td>4 straight wins</td></tr>
<tr><th scope="row">LAFC points</th><td>33, second in the Western Conference</td></tr>
<tr><th scope="row">Next opponent</th><td>Vancouver Whitecaps, also on 33 points</td></tr>
</tbody>
</table></div>
<p>The consecutive-scoring run is the number that matters more than the MVP award. Three straight league games with a goal, inside a four-match winning sequence, is the difference between a signing that sells shirts and one that moves a table position. LAFC went from mid-table to second during that stretch.</p>
<h2 id="what-is-at-stake-on-saturday">3. What is at stake on Saturday</h2>
<p>The Vancouver fixture on 2 August Korean time is a straight swap for position: both clubs are on 33 points, and the winner takes clear second with a claim on the lead.</p>
<p>There is a second layer to it. Vancouver eliminated LAFC in last season&#39;s playoffs, which gives the match a shape beyond the standings. Squad availability had not been published at the time of writing, so how much of that history actually gets settled on the pitch is not yet knowable.</p>]]></content:encoded>
  </item>
  <item>
    <title>HBM4 vs HBM3E: what doubles, and why it matters</title>
    <link>https://tenbrief.com/en/2026/08/01/hbm4-vs-hbm3e</link>
    <guid isPermaLink="true">https://tenbrief.com/en/2026/08/01/hbm4-vs-hbm3e</guid>
    <pubDate>Sat, 01 Aug 2026 09:00:00 GMT</pubDate>
    <category>Tech</category>
    <description>HBM4 doubles the I/O count to 2,048, delivering over 2TB/s per stack against HBM3E's 1.2TB/s</description>
    <content:encoded><![CDATA[<p>Every major memory supplier has now moved HBM4 out of the lab. SK hynix said on its Q2 2026 earnings call that it began shipping HBM4 in the second quarter and had closed long-term supply agreements with roughly ten customers; Samsung shipped commercial HBM4 in February; Micron has said its 12-high ramp is running at twice the pace of HBM3E. The generation that succeeds HBM3E as the default memory for AI accelerators is here. What follows is what actually changed, drawn from the JEDEC standard and supplier statements rather than roadmap slides.</p>
<h2 id="what-changed">1. What changed</h2>
<p>The headline change is the width of the road, not the speed limit. Under JESD270-4, HBM4 doubles the I/O count from 1,024 to 2,048 and independent channels from 16 to 32. Per-stack bandwidth therefore roughly doubles without pushing per-pin speed to a difficult place — a deliberate choice, because signal integrity and power both degrade quickly as pin rates climb.</p>
<p>The second change is less visible and matters more for the industry&#39;s structure. The base die that sits underneath the stack and manages data flow moves from a memory process to a foundry logic process. That allows far more capable control circuitry, and it makes memory vendors dependent on foundry partners for a component they previously made themselves. The boundary between memory manufacturing and logic manufacturing is now blurred in a way it was not two generations ago.</p>
<h2 id="the-numbers">2. The numbers</h2>
<p>JEDEC sets the standard pin rate at 8Gbps, which yields roughly 2TB/s per stack. SK hynix has stated it achieved operation above 10Gbps; a straight conversion puts that near 2.5TB/s, though no supplier publishes a throughput figure at that speed. Against HBM3E 12-high — 36GB at roughly 1.2TB/s — the per-stack gap is close to a doubling, and suppliers cite power efficiency gains above 40% versus the prior generation.</p>
<div class="table-wrap"><table>
<thead><tr><th scope="col"></th><th scope="col">HBM3E</th><th scope="col">HBM4</th></tr></thead>
<tbody>
<tr><th scope="row">I/O pins</th><td>1,024</td><td>2,048</td></tr>
<tr><th scope="row">Independent channels</th><td>16</td><td>32</td></tr>
<tr><th scope="row">Pin speed</th><td>up to 9.6Gbps</td><td>8Gbps standard; above 10Gbps demonstrated</td></tr>
<tr><th scope="row">Bandwidth per stack</th><td>about 1.2TB/s</td><td>over 2TB/s</td></tr>
<tr><th scope="row">Stack height and capacity</th><td>12-high, 36GB in production</td><td>up to 16-high, 64GB in spec</td></tr>
<tr><th scope="row">Base die</th><td>memory process</td><td>foundry logic process</td></tr>
<tr><th scope="row">Power</th><td>—</td><td>over 40% better efficiency (supplier figure)</td></tr>
</tbody>
</table></div>
<p>That gap is the whole argument for the generation. An accelerator&#39;s usable throughput is bounded by how fast it can be fed, not by how fast it can multiply — a large language model reads its entire parameter set from memory for each token it produces. Doubling bandwidth per stack moves the ceiling directly. Higher stacks and a logic base die do raise unit cost, and market researchers broadly expect HBM4 to price above HBM3E, but no supplier has published a number.</p>
<h2 id="what-is-still-open">3. What is still open</h2>
<p>Several things commonly reported as settled are not. The 12nm-class foundry process said to be used for SK hynix&#39;s base die has not been confirmed by the manufacturer. Pricing is entirely unpublished. The timing for 16-high 64GB parts — allowed by the spec but not yet in volume — remains unannounced, as does the schedule for HBM4E, for which samples have shipped against a 2027 production target.</p>
<p>Heat is the constraint least discussed and most likely to bind. Stacking higher and clocking faster raises total dissipation even as efficiency per bit improves, and cooling design increasingly decides which parts a customer can actually deploy. SK hynix has said it is developing an approach it calls iHBM that lowers thermal resistance by more than 30%; nothing comparable has been detailed publicly by its competitors.</p>]]></content:encoded>
  </item>
  <item>
    <title>Deleveraging: why selling ends in a rally</title>
    <link>https://tenbrief.com/en/2026/08/01/deleveraging-explained</link>
    <guid isPermaLink="true">https://tenbrief.com/en/2026/08/01/deleveraging-explained</guid>
    <pubDate>Sat, 01 Aug 2026 09:00:00 GMT</pubDate>
    <category>Economy</category>
    <description>Deleveraging is debt reduction; once forced selling ends, supply pressure lifts</description>
    <content:encoded><![CDATA[<p>On 31 July the Korean market rose 17.91% in a session, and most explanations reached for earnings or the currency. Those helped. The larger mechanism was that a forced seller finished selling. This piece explains that mechanism, because it recurs and because it is routinely mistaken for a change in fundamentals.</p>
<h2 id="what-deleveraging-is">1. What deleveraging is</h2>
<p>Deleveraging means reducing debt relative to assets. A company can do it by selling a division or issuing shares. A leveraged fund almost always does it by selling positions, and usually not on a schedule of its own choosing.</p>
<p>The trigger is typically a margin call. A fund borrowing against its portfolio must maintain collateral above a threshold. When prices fall, the collateral value falls, and the lender demands more. If the fund cannot post cash, it sells.</p>
<p>The critical property is that this selling is price-insensitive. A fund meeting a call sells what it can move, not what it judges overvalued. Liquid, widely held large-caps go first — which is why a liquidation drags down exactly the names that look least deserving of it.</p>
<h2 id="why-it-feeds-on-itself-then-stops">2. Why it feeds on itself, then stops</h2>
<div class="table-wrap"><table>
<thead><tr><th scope="col">Stage</th><th scope="col">What happens</th></tr></thead>
<tbody>
<tr><th scope="row">Trigger</th><td>Prices fall, collateral value drops, lender issues a margin call</td></tr>
<tr><th scope="row">Forced sale</th><td>Fund sells liquid positions regardless of valuation</td></tr>
<tr><th scope="row">Feedback</th><td>Selling pushes prices lower, tightening collateral further</td></tr>
<tr><th scope="row">Acceleration</th><td>More calls, more forced sales, volumes spike</td></tr>
<tr><th scope="row">Exhaustion</th><td>Position closed or book transferred; the seller is gone</td></tr>
<tr><th scope="row">Rebound</th><td>Remaining buyers face no forced supply; prices move sharply</td></tr>
</tbody>
</table></div>
<p>The loop in the middle is why declines from liquidations are steeper than the news justifies. The exit at the bottom is why the rebound is equally disproportionate. Nothing improved. One participant stopped selling.</p>
<p>The 31 July session fits the pattern precisely. Foreign investors bought about 7.2 trillion won net after weeks of selling. Retail investors sold roughly 8.25 trillion won into that bid. Neither side had new information about Korean companies; the supply that had been overwhelming the bid was simply no longer there.</p>
<h2 id="what-this-does-not-tell-you">3. What this does not tell you</h2>
<p>A liquidation ending is not a valuation signal. It says the technical pressure has lifted, not that prices are correct. Markets that rebound off the end of forced selling frequently give back part of the move once ordinary two-way trading resumes.</p>
<p>It is also difficult to identify in real time. Traders described the July unwind as finished only after the rebound, and whether the book was fully absorbed remains an interpretation rather than a confirmed fact. Estimates of the position&#39;s size vary widely enough that no figure is used here. The practical lesson is narrower: when a decline is driven by a seller who has to sell, the relevant question is how much is left, not what the assets are worth.</p>]]></content:encoded>
  </item>
  <item>
    <title>Korea's heat alerts: the three tiers</title>
    <link>https://tenbrief.com/en/2026/08/01/korea-heat-alerts</link>
    <guid isPermaLink="true">https://tenbrief.com/en/2026/08/01/korea-heat-alerts</guid>
    <pubDate>Sat, 01 Aug 2026 09:00:00 GMT</pubDate>
    <category>Life &amp; Health</category>
    <description>Advisory is 33C felt, warning 35C for two days, critical 38C for one day</description>
    <content:encoded><![CDATA[<p>Korea rebuilt its heat alert system on 1 June 2026, the first structural change in eighteen years. Two months later the new top tier was in force across the southeast while a station in Yangsan recorded 41.4C. This is a reference piece on what the tiers mean and what the clinical response actually is, because both are routinely reported in fragments.</p>
<h2 id="the-three-tiers">1. The three tiers</h2>
<p>The system runs on felt temperature — the heat index combining air temperature and humidity — rather than air temperature alone. That matters in a Korean summer, where humidity frequently makes 33C feel considerably worse than the same reading in a dry climate.</p>
<div class="table-wrap"><table>
<thead><tr><th scope="col">Tier</th><th scope="col">Threshold (felt)</th><th scope="col">Duration required</th></tr></thead>
<tbody>
<tr><th scope="row">Advisory</th><td>33C</td><td>two or more consecutive days expected</td></tr>
<tr><th scope="row">Warning</th><td>35C</td><td>two or more consecutive days expected</td></tr>
<tr><th scope="row">Critical</th><td>38C</td><td>a single day expected</td></tr>
</tbody>
</table></div>
<p>The duration column is the part most often dropped in reporting, and it is the design decision that matters. Advisory and warning both require a sustained pattern, on the reasoning that consecutive hot days compound physiological load. The critical tier abandons that requirement: a single forecast day at 38C is enough, because at that level the risk is acute rather than cumulative.</p>
<h2 id="what-to-do">2. What to do</h2>
<p>For heat exhaustion — heavy sweating, weakness, nausea, headache, but consciousness intact — move to shade or air conditioning, loosen clothing, and give cool water or an electrolyte drink in small amounts.</p>
<p>For suspected heat stroke, the response is different and time-critical. The distinguishing signs are a body temperature above 40C, skin that is hot and often dry rather than sweating, and altered consciousness — confusion, slurred speech, collapse.</p>
<ul><li>Call 119 immediately. Do not wait to see whether the person improves.</li><li>Move them into shade and remove excess clothing.</li><li>Cool aggressively with ice packs at the neck, armpits and groin, where large vessels run close to the surface.</li><li>Do not give fluids to anyone unconscious or unable to swallow reliably. Aspiration is a real risk.</li></ul>
<p>The distinction matters because heat stroke has a mortality curve measured in tens of minutes. Cooling before the ambulance arrives is not optional first aid; it is the intervention.</p>
<h2 id="where-the-season-stands">3. Where the season stands</h2>
<p>Cumulative heat-illness cases reached 1,638 with 12 deaths as of 31 July. Officials described the death toll as running at roughly 75% of the equivalent point last year, against higher peak temperatures — which suggests the alert changes and the cooling-centre network absorbed part of the load, though that is an inference rather than a measured effect.</p>
<p>These totals are provisional. Korean heat-illness deaths are reclassified after cause-of-death review, so the final figure will not be settled until autumn. The temperature record that triggered the first critical alerts is covered in a companion piece published the same day.</p>]]></content:encoded>
  </item>
  <item>
    <title>Korea orders a 190,000-building fire audit</title>
    <link>https://tenbrief.com/en/2026/08/01/factory-fire-audit</link>
    <guid isPermaLink="true">https://tenbrief.com/en/2026/08/01/factory-fire-audit</guid>
    <pubDate>Sat, 01 Aug 2026 03:00:00 GMT</pubDate>
    <category>Issues</category>
    <description>Korea will inspect 190,000 factories and warehouses and spend 1.45tn won over five years</description>
    <content:encoded><![CDATA[<p>Korea announced on 31 July what it describes as its first comprehensive fire-safety review of industrial buildings. The package covers roughly 190,000 factories and warehouses and commits 1.45 trillion won of support over five years. It is worth reading for two reasons: the scale is unusual, and several of the rules it announces do not yet have dates attached.</p>
<h2 id="what-was-announced">1. What was announced</h2>
<p>The measure came out of the emergency economic committee rather than a single ministry, which signals both the political weight attached to it and the number of agencies that have to coordinate. Three components matter.</p>
<p>The first is the survey itself. About 190,000 buildings are to be inspected between September 2026 and the end of 2027, sequenced so that the highest-risk structures go first.</p>
<p>The second is money. 1.45 trillion won over five years is earmarked to help operators — mostly small and mid-sized — pay for the retrofits the survey will identify. Without it the standards would function as an unfunded mandate on exactly the operators least able to absorb one.</p>
<p>The third is the standards themselves: tighter requirements for exterior cladding, detection systems and sprinklers.</p>
<h2 id="the-numbers">2. The numbers</h2>
<div class="table-wrap"><table>
<thead><tr><th scope="col">Item</th><th scope="col">Figure</th></tr></thead>
<tbody>
<tr><th scope="row">Buildings to be surveyed</th><td>about 190,000</td></tr>
<tr><th scope="row">Survey period</th><td>September 2026 – December 2027</td></tr>
<tr><th scope="row">Financial support</th><td>1.45 trillion won over five years</td></tr>
<tr><th scope="row">Triggering incident</th><td>Daejeon plant fire, March, 14 deaths</td></tr>
<tr><th scope="row">Second incident</th><td>Incheon logistics centre fire, July</td></tr>
</tbody>
</table></div>
<p>The two fires are the reason the package exists in this form. The March fire at an auto-parts plant in Daejeon killed 14 people. The July logistics centre fire in Incheon followed while the response to the first was still being drafted. Korean industrial fire policy has historically moved after casualties rather than before, and this sequence follows that pattern.</p>
<h2 id="what-is-still-open">3. What is still open</h2>
<p>The effective dates are the gap. Announcing tightened cladding, detector and sprinkler standards without saying when they bind leaves the most consequential part of the package undefined. Operators cannot plan retrofits against a rule that has no commencement date, and the 1.45 trillion won cannot be allocated against a schedule that does not exist.</p>
<p>The underlying source document could not be opened, so the figures here rest on four press reports cross-checked against one another rather than on the ministry release. The phased breakdown of survey volume — how many buildings in each half-year — appears in only one outlet and is therefore not reproduced. Anyone relying on these numbers for planning should wait for the official text.</p>]]></content:encoded>
  </item>
  <item>
    <title>Senate blocks Iran war powers, 49-50</title>
    <link>https://tenbrief.com/en/2026/08/01/senate-iran-war-powers</link>
    <guid isPermaLink="true">https://tenbrief.com/en/2026/08/01/senate-iran-war-powers</guid>
    <pubDate>Sat, 01 Aug 2026 03:00:00 GMT</pubDate>
    <category>World</category>
    <description>The Senate rejected a motion on the Iran war powers resolution 49-50 on 30 July</description>
    <content:encoded><![CDATA[<p>The United States Senate voted 49-50 on 30 July against discharging a resolution that would have limited the president&#39;s authority to use force against Iran. The margin is the story: three Republicans crossed party lines to support it, which in most weeks would have been enough, and it still failed because one Democrat went the other way.</p>
<h2 id="what-was-voted-on">1. What was voted on</h2>
<p>The measure was S.J.Res.181, introduced by Senator Kirsten Gillibrand under the War Powers Resolution. Procedurally, the vote was not on the resolution itself but on a motion to discharge it from the Foreign Relations Committee, where it had been referred and where it remains.</p>
<p>This distinction matters for reading the result. A discharge motion is a test of whether the chamber wants to consider a question at all. Failing one does not kill the underlying resolution; it leaves it where it was.</p>
<h2 id="the-arithmetic">2. The arithmetic</h2>
<div class="table-wrap"><table>
<thead><tr><th scope="col"></th><th scope="col">Count</th></tr></thead>
<tbody>
<tr><th scope="row">For discharge</th><td>49</td></tr>
<tr><th scope="row">Against</th><td>50</td></tr>
<tr><th scope="row">Total cast</th><td>99</td></tr>
<tr><th scope="row">Republicans voting for</th><td>Paul, Collins, Murkowski</td></tr>
<tr><th scope="row">Democrats voting against</th><td>Fetterman</td></tr>
</tbody>
</table></div>
<p>Three Republican defections is a meaningful number. Rand Paul&#39;s position on executive war powers is long-standing and predates this administration; Susan Collins and Lisa Murkowski represent a narrower institutionalist strand. Against that, John Fetterman&#39;s vote with the majority continued a pattern he has held on Middle East questions since the conflict began.</p>
<p>Ninety-nine votes were cast, so one senator was absent. The official roll-call record was not reachable, so that member is not identified here.</p>
<h2 id="what-is-still-open">3. What is still open</h2>
<p>Democrats have forced comparable votes almost weekly since hostilities began in February. The strategy is less about winning any single vote than about building a record and keeping the authorisation question in front of the chamber. On that measure the 49-50 result is closer than most.</p>
<p>The ceiling on the strategy is structural. Even a resolution that passed both chambers would face a presidential veto, and overriding one requires two-thirds in each — a threshold nowhere near reach at these margins. What a one-vote loss does establish is that the coalition is no longer purely partisan, which changes the arithmetic if the conflict escalates or if public opinion moves.</p>]]></content:encoded>
  </item>
  <item>
    <title>HBM4 ramp: the race turns to supply</title>
    <link>https://tenbrief.com/en/2026/08/01/hbm4-mass-production</link>
    <guid isPermaLink="true">https://tenbrief.com/en/2026/08/01/hbm4-mass-production</guid>
    <pubDate>Sat, 01 Aug 2026 03:00:00 GMT</pubDate>
    <category>Tech</category>
    <description>SK hynix began HBM4 shipments in Q2 and targets HBM4E production in 2027</description>
    <content:encoded><![CDATA[<p>Every major memory supplier has now moved HBM4 into production, which changes what the competition is about. For two years the question was who could build it. From this quarter the question is who can hold yield while shipping volume, and that is a different contest with different winners.</p>
<h2 id="where-each-supplier-stands">1. Where each supplier stands</h2>
<p>SK hynix said on its second-quarter call that HBM4 mass-production shipments began in the quarter, that second-half volumes will expand, and that long-term supply agreements are in place with roughly ten customers. The stock hit its daily limit on the news.</p>
<p>Samsung got there first in calendar terms, shipping commercial HBM4 in February and stating an intent to more than triple HBM revenue year over year.</p>
<p>Micron has framed its position in rate-of-change terms: its 12-high ramp is running at roughly twice the pace of its HBM3E ramp, with related revenue already past $1bn.</p>
<p>Three different claims, three different metrics — which is itself the point. No supplier is choosing to compete on the same axis.</p>
<h2 id="the-timeline">2. The timeline</h2>
<div class="table-wrap"><table>
<thead><tr><th scope="col">Milestone</th><th scope="col">Supplier</th><th scope="col">Timing</th></tr></thead>
<tbody>
<tr><th scope="row">First commercial HBM4 shipment</th><td>Samsung</td><td>February 2026</td></tr>
<tr><th scope="row">Mass-production shipment begins</th><td>SK hynix</td><td>Q2 2026</td></tr>
<tr><th scope="row">Second-half volume expansion</th><td>SK hynix</td><td>H2 2026</td></tr>
<tr><th scope="row">Long-term agreements signed</th><td>SK hynix</td><td>about ten customers</td></tr>
<tr><th scope="row">HBM4E customer samples</th><td>SK hynix</td><td>H1 2026</td></tr>
<tr><th scope="row">HBM4E production target</th><td>SK hynix</td><td>2027</td></tr>
</tbody>
</table></div>
<p>The gap between first shipment and volume shipment is where the money is. Being first to ship a qualified part matters for design wins; being able to supply that part at yield decides revenue. Accelerator makers commit a year or more ahead, so the supplier that can guarantee volume takes the socket even if it was second to qualify.</p>
<h2 id="what-is-still-open">3. What is still open</h2>
<p>The HBM4E production quarter has not been disclosed. The company target is 2027, and market talk of an accelerated schedule is not confirmed by anything the company has said.</p>
<p>Contract detail is thinner than the headlines suggest. Official material refers to about ten customers; some reports say eleven with five-year terms. Volume and pricing are not public in any of them. Micron has published nothing on HBM4E timing at all. The technical differences that make this generation matter — the doubled interface and the logic base die — are covered in a companion piece published the same day.</p>]]></content:encoded>
  </item>
  <item>
    <title>Korea's KOSPI jumps 17.91% in one day</title>
    <link>https://tenbrief.com/en/2026/08/01/kospi-record-rally</link>
    <guid isPermaLink="true">https://tenbrief.com/en/2026/08/01/kospi-record-rally</guid>
    <pubDate>Fri, 31 Jul 2026 21:00:00 GMT</pubDate>
    <category>Economy</category>
    <description>The KOSPI closed 17.91% higher on 31 July, its largest single-day gain ever</description>
    <content:encoded><![CDATA[<p>Korean equities had spent most of July going one direction. On 31 July they went the other, and further in a single session than they ever had. The KOSPI closed at 6,595.45, up 1,001.89 points or 17.91% — the largest one-day move by both measures since the index began in 1980. What follows separates the three things that happened at once, because they are usually reported as one.</p>
<h2 id="what-moved">1. What moved</h2>
<p>Three forces arrived on the same day, and only one of them was news.</p>
<p>The first was the end of a forced seller. A leveraged fund had been liquidating Korean positions through July, and reports that a larger firm had taken over its book removed the overhang. Nothing about Korean company fundamentals changed; the marginal seller simply stopped.</p>
<p>The second was earnings. SK hynix said on its second-quarter call that HBM4 mass-production shipments had begun and that long-term supply agreements were signed with roughly ten customers. The stock hit its 30% daily limit, its first under the price band in force since June 2015.</p>
<p>The third was the currency. A firmer won raises the dollar value of Korean holdings for foreign investors, which matters when those investors are deciding whether to re-enter.</p>
<h2 id="the-numbers">2. The numbers</h2>
<div class="table-wrap"><table>
<thead><tr><th scope="col"></th><th scope="col">Figure</th></tr></thead>
<tbody>
<tr><th scope="row">Close</th><td>6,595.45</td></tr>
<tr><th scope="row">Point gain</th><td>1,001.89</td></tr>
<tr><th scope="row">Percentage gain</th><td>17.91%</td></tr>
<tr><th scope="row">Foreign net buying</th><td>about 7.2 trillion won</td></tr>
<tr><th scope="row">Retail net selling</th><td>about 8.25 trillion won</td></tr>
<tr><th scope="row">Previous record gain</th><td>far below both measures</td></tr>
</tbody>
</table></div>
<p>The flow direction is the part worth holding onto. Foreigners bought roughly 7.2 trillion won net after weeks of selling; retail investors sold about 8.25 trillion won into that bid. The exact figures differ by outlet — 7.2196, 7.2412 and 7.2499 trillion won all appear — because settlement timing differs, so the round number is the honest one until the exchange publishes its final tally.</p>
<h2 id="what-is-still-open">3. What is still open</h2>
<p>Whether the liquidation is actually complete is an interpretation, not a fact. Brokerages moved quickly to describe the session as a floor-forming event, but no one outside the funds involved knows how much stock remains to be sold. The size of the liquidating book is itself disputed: reports put it above $20bn or near $45bn at peak, which is a wide enough range that no figure is used here.</p>
<p>A one-day move of this size also says something about liquidity rather than value. When a forced seller leaves a market that has already thinned out, prices can travel a long way on modest volume. The mechanics of that process, and why the rebound tends to follow the selling rather than accompany it, are covered in a companion piece published the same day.</p>]]></content:encoded>
  </item>
  <item>
    <title>Korea sets an all-time heat record</title>
    <link>https://tenbrief.com/en/2026/08/01/korea-heat-records</link>
    <guid isPermaLink="true">https://tenbrief.com/en/2026/08/01/korea-heat-records</guid>
    <pubDate>Fri, 31 Jul 2026 21:00:00 GMT</pubDate>
    <category>Life &amp; Health</category>
    <description>Yangsan hit 41.4C on 31 July, the highest temperature ever recorded in Korea</description>
    <content:encoded><![CDATA[<p>Korea has recorded 40C before, but never in July, and never as high as it did at the end of this one. Between 29 and 31 July a single station in Yangsan, in the country&#39;s southeast, logged three consecutive days above 40C and finished with 41.4C — the highest temperature in the national record. For readers outside Korea the interest is less the number than the mechanism, because the same setup is now recurring across East Asia.</p>
<h2 id="what-happened">1. What happened</h2>
<p>The sequence was compressed. On 29 July Yangsan reached 40.3C, the first time any Korean station had touched 40C during July. On 30 July it did it again, which had never happened on consecutive days. On 31 July it reached 41.4C.</p>
<p>The cause was a stacking of two systems. The North Pacific high, which normally dominates the Korean summer, was overlaid by the Tibetan high pushing east at higher altitude. Two warm air masses sitting on top of each other suppress vertical mixing, so heat accumulates near the surface through the night as well as the day. Tropical-night counts — nights where the minimum stays above 25C — reached a record for the season.</p>
<h2 id="the-numbers">2. The numbers</h2>
<div class="table-wrap"><table>
<thead><tr><th scope="col">Date</th><th scope="col">Station</th><th scope="col">Temperature</th><th scope="col">Note</th></tr></thead>
<tbody>
<tr><th scope="row">29 July</th><td>Yangsan</td><td>40.3C</td><td>first July 40C on record</td></tr>
<tr><th scope="row">30 July</th><td>Yangsan</td><td>above 40C</td><td>first consecutive 40C days</td></tr>
<tr><th scope="row">31 July</th><td>Yangsan</td><td>41.4C</td><td>national all-time high</td></tr>
</tbody>
</table></div>
<p>Health effects tracked the temperature closely. Cumulative heat-illness cases reached 1,638 with 12 deaths. Officials described the death toll as running at roughly 75% of the comparable point last year — lower, but against a higher temperature, which suggests the alert system and cooling-centre network absorbed part of the load.</p>
<p>Korea revised its heat alert structure on 1 June this year, adding a third and highest tier. The criteria and the clinical response are covered in a companion reference piece published the same day.</p>
<h2 id="what-is-still-open">3. What is still open</h2>
<p>The death figures are provisional. Korean heat-illness deaths are reclassified after cause-of-death review, and the final number for the season will not be known until autumn. The 75% comparison is therefore a running estimate rather than a settled result.</p>
<p>Whether this is a new plateau or a single extreme is also unresolved. One station reaching 41.4C does not by itself establish a trend, and the overlapping-high pattern that produced it is not guaranteed to repeat. What is established is that the July ceiling moved: a threshold that had never been crossed in that month was crossed three days running.</p>]]></content:encoded>
  </item>
  <item>
    <title>HBM: the AI memory bottleneck</title>
    <link>https://tenbrief.com/en/2026/08/01/hbm-reference</link>
    <guid isPermaLink="true">https://tenbrief.com/en/2026/08/01/hbm-reference</guid>
    <pubDate>Fri, 31 Jul 2026 21:00:00 GMT</pubDate>
    <category>Tech</category>
    <description>HBM stacks DRAM vertically for bandwidth; HBM4 moves over 2TB/s per stack</description>
    <content:encoded><![CDATA[<p>Every discussion of AI hardware eventually arrives at memory, usually without explaining why. This is a reference piece on HBM — what it is, why it became the constraint on accelerator performance, and who controls the supply. It is written to be linked to rather than read once.</p>
<h2 id="what-hbm-is">1. What HBM is</h2>
<p>Conventional computer memory sits in modules some distance from the processor, connected by a relatively narrow bus. That arrangement is flexible and cheap, and its bandwidth ceiling is low.</p>
<p>High Bandwidth Memory takes the opposite approach. Between four and sixteen DRAM dies are stacked vertically and connected by through-silicon vias — copper channels drilled straight through each die rather than routed around its edge. The stack sits immediately beside the processor on a shared interposer.</p>
<p>Two things follow. The connection is extremely wide, because thousands of vertical channels can run through a stack where only a few hundred traces would fit on a board. And it is very short, which cuts the energy cost per bit moved. Bandwidth rises by an order of magnitude; packaging complexity and cost rise with it.</p>
<h2 id="why-it-became-the-bottleneck">2. Why it became the bottleneck</h2>
<p>An accelerator&#39;s usable throughput is set by how fast it can be fed, not by how fast it can multiply. A large language model reads its entire parameter set from memory for each token it produces. Arithmetic units sit idle waiting for data.</p>
<p>This is why generational HBM specifications track AI capability more closely than transistor counts do.</p>
<div class="table-wrap"><table>
<thead><tr><th scope="col">Generation</th><th scope="col">Interface</th><th scope="col">Bandwidth per stack</th><th scope="col">Status</th></tr></thead>
<tbody>
<tr><th scope="row">HBM2E</th><td>1,024-bit</td><td>about 460GB/s</td><td>legacy</td></tr>
<tr><th scope="row">HBM3</th><td>1,024-bit</td><td>about 819GB/s</td><td>shipping</td></tr>
<tr><th scope="row">HBM3E</th><td>1,024-bit</td><td>about 1.2TB/s</td><td>volume, 12-high 36GB</td></tr>
<tr><th scope="row">HBM4</th><td>2,048-bit</td><td>over 2TB/s</td><td>in production, up to 16-high 64GB in spec</td></tr>
</tbody>
</table></div>
<p>The HBM4 step is structural rather than incremental. Doubling the interface width to 2,048 bits roughly doubles bandwidth without forcing per-pin speeds into a region where signal integrity and power degrade sharply. Its base die also moves from a memory process to a foundry logic process, which makes memory suppliers dependent on foundry partners for a component they used to make themselves.</p>
<h2 id="who-controls-supply">3. Who controls supply</h2>
<p>Three companies make HBM at volume. On Q2 2025 shipment share, Counterpoint put SK hynix at 62%, Micron at 21% and Samsung at 17%. No fourth supplier is near qualification, and the barrier is not lithography but packaging yield — stacking sixteen dies with thousands of vias each, without a single fatal defect, is a manufacturing problem few can solve economically.</p>
<p>That concentration is the strategic fact. When one supplier holds roughly three-fifths of a component that gates AI accelerator performance, its capacity decisions propagate into the availability and price of AI compute worldwide.</p>
<p>Two caveats on the numbers. Shipment-share estimates come from a single research firm and differ from revenue-based rankings, since generation mix affects average selling price. And no supplier publishes HBM pricing, so any cost comparison across generations rests on market research rather than disclosure.</p>]]></content:encoded>
  </item>
</channel>
</rss>