The Checklist for Leading at the Edge

"Eight lines, each priced by a lesson. Not Apple's list — nobody outside Apple has one — but a list the physics allows, which is the only kind a household can write."

The Eight

This track set out to say why the pool stops at 512 GB with price removed, and each lesson left an item on the table. The code block is the table: eight things Apple would have to do, in this quest's judgment, to keep leading at the edge, each tied to the lesson that priced it and to a reason a sentence long. A wider bus at the same bandwidth per gigabyte — more channels or LPDDR6's geometry — because the package's edge is the constraint the wire lesson found. A terabyte on the next die rather than a new bus, because density is where capacity actually comes from and the memory vendors' 2026 calendar already has the die. A capacity tier behind a coherent link, the shape the rivals ship, which needs the page-table machinery macOS already uses for one tier. Flash routing per prompt exposed to every runtime, because Apple has it in a phone and the Mac's runtimes do not. A wire between Macs ten times wider than Thunderbolt 5, or the honesty to say the pool is one package. Batching and a prefix cache in the platform, the two things that make cloud long-context economical and that the edge lacks. The 95%'s workloads productized — summary, translation, dictation, photo tagging, the short-context, latency-tolerant jobs the household already runs on its fleet. And a price the 95% will pay, which the first lesson's memory market makes the one item on the list Apple does not control.

What Is Silicon and What Is Software

Read the list by who does the work. Two items are memory vendors' — the die and the pin rate — and Apple's job on them is to be first to qualify. Two are packaging — the bus width and the wire — and they are Apple's alone, at the cost the ladder lesson measured for the last doubling. Three are software — the tier's page table, the flash routing, the batch and prefix cache — and they are the cheapest and the least shipped, because the population that would use them on a Mac is the tail the doctrine described. One is price, and it is the market's. The household's reading, carried into the next track, is that the silicon half of the list is on a calendar Apple can read but not set, and the software half is on no calendar at all until the workloads that need it are the body of the market. That is why the direction can be right and the time not now: the list is real, half of it is dated, and the other half waits on a population.

The Household's Homework, Alongside Apple's

A household cannot widen a bus. What it can do is the reader's Mac card: know its bytes per token, its bandwidth, its working set and its wire; run the four physics-track experiments; sort its jobs by the referee's line; keep a store, run a hub, and label what is an operation and what is an experiment. Every item on Apple's list has a row on the card that says what it would change here — a doubled pool would admit one model the household does not want at the speed it would run; a wider bus would speed every model it runs; a flash router would make the store's largest file usable; a wider wire would make the second Studio a tier instead of a mirror. The card is the household's checklist, and its last row is the next track's: what the machine is for when every cloud is down, and how long to wait, with what term, for the list above to shorten.