Concepts

Concepts answers a single question about how something in Apple’s stack really works, and it answers it with a diagram we drew ourselves rather than one redrawn from a WWDC slide.

The rule for this pillar is that the explanation has to survive contact with the machine. If we claim unified memory changes how swap behaves, there is a memory-pressure reading in the article showing it. If we claim the efficiency cores pick up a particular kind of work, there is a core-residency trace. An explanation that cannot be demonstrated on hardware we own is a guess with confident formatting, and it does not ship here.

These pieces are deliberately narrow. One idea per article, no survey posts, no "everything you need to know about" roundups. A reader should finish knowing exactly one thing more than when they started, and should be able to reproduce the check themselves in a few minutes.

The diagrams here are drawn for the article they appear in. None is redrawn from a WWDC slide or traced from someone else's illustration, and none is decoration: if removing a diagram costs the article nothing, it gets removed rather than kept for the look of it. A diagram earns its place by showing a relationship the prose can only assert, which usually means relative magnitude, ordering, or the fact that two things people treat as one are actually separate.

A recurring theme across this pillar is that macOS reports the same quantity several different ways, and the differences between those reports are where the interesting behaviour hides. Memory has at least six categories and none of them is the one people look at. Storage is described in two unit systems by tools that both call their output GB. Battery capacity has three values. In each case the confusion is not a bug, it is two honest answers to two different questions, and knowing which question you asked is the whole skill.

Nothing in this pillar depends on privileged access or on tools you have to install. Every reading quoted here comes from a utility that shipped with the operating system, which means a reader can confirm or contradict any claim in a few seconds. That constraint rules out some subjects entirely, and the ones it leaves are the ones worth writing about.

Length here follows the idea rather than a target. Some mechanisms are settled in nine hundred words and padding them out would only bury the point; others genuinely need the space and get it. Where an article is short it is because the question was narrow, not because the work stopped early.

If you are reading a Concepts piece to solve a problem you are having right now, the Fixes section is probably the faster route, and each article links across where the two overlap. This pillar is for the case where the fix worked and you want to know why, which is the knowledge that stops the next problem being a surprise.