Second pass at: The storage lookup and where its data comes from

On the subject in the title: Second pass at: The storage lookup and where its data comes from Working notes rather than a conclusion.

Two things I would like separated before anyone answers on storage lookup, because they get bundled and then argued about as one thing.

The first is descriptive: what has actually been observed, by whom, and how. The second is causal: why. I am asking about the first only.

Answering the question post #9 raises rather than the one it answers.

The most useful improvement to any of these tools would be a plain-language statement of what it assumes. Assumptions are where the disagreements live.

Posting it because the silence on this was starting to look like agreement.

Confirming post #11 from a second method, which matters more than confirming it from a second person.

On storage lookup: the maintained page in the documentation commons covers the general case with citations and a review date, which is more reliable than any reply here including this one.

Whatever the answer on storage lookup turns out to be, the method for getting there is the same: state the assumption, do the arithmetic in public, invite the correction.

Where a calculator and your own arithmetic disagree, the productive move is to find which step differs rather than to decide which is right.

I have changed my mind on this once already, so take it as current rather than settled.

The version of storage lookup that circulates here is a simplification of a simplification. It is not wrong, but it has lost the conditions under which it holds, and those conditions are where the interesting cases live.