Thirty seconds pass. A minute. The monitor waits.

This is not a story about a missing document. The license is in there, somewhere, buried under the accumulated weight of records filed with no organizing principle beyond "put it behind this tab." The problem is not that the binder lacks content. The problem is that the binder was designed -- if one can call it designed -- for storage, not for retrieval.

And that distinction, between designing for storage and designing for retrieval, is the single most important architectural principle this lesson teaches. A binder designed for storage answers one question: "Where do I put this?" A binder designed for retrieval answers a different, harder question: "Where will someone look for this -- including someone who has never seen this binder before?"

Every design decision in this lesson flows from that principle.

Thirty seconds pass. A minute. The monitor waits.

This is not a story about a missing document. The license is in there, somewhere, buried under the accumulated weight of records filed with no organizing principle beyond "put it behind this tab." The problem is not that the binder lacks content. The problem is that the binder was designed -- if one can call it designed -- for storage, not for retrieval.

And that distinction, between designing for storage and designing for retrieval, is the single most important architectural principle this lesson teaches. A binder designed for storage answers one question: "Where do I put this?" A binder designed for retrieval answers a different, harder question: "Where will someone look for this -- including someone who has never seen this binder before?"

Every design decision in this lesson flows from that principle.