1.1. Why
This section explains the motivation for the project, which would have remained mercifully short if “because I felt like it” had been permitted to stand without supervision.
Every project prefers an origin story with posture. It wants to begin with a requirement, a need, a measurable deficiency, or at least a sentence that sounds expensive. This one began with something much less polished. I wanted to build it. That is the reason before it put on formal clothes and started pretending to have a strategic outlook.
That answer may sound unserious, but it is perfectly serviceable. Curiosity is still a motive. Mild irritation with opaque systems is still a motive. The desire to inspect the machinery instead of being asked to trust the appliance is also a motive, and arguably a better one than whatever a committee would have written after three meetings and a slide deck.
There are easier ways to obtain a Linux system. Naturally, that is not the point. The point is to replace convenience with understanding, then act surprised when it takes longer.
Building the system by hand forces each component to stop hiding in the crowd. Libraries, toolchain pieces, configuration choices, and old assumptions all have to present themselves one by one. Some of them turn out to be essential. Some turn out to be inherited habits with excellent public relations.
There is also a quieter reason. A finished distribution tells you what someone else thought was reasonable. A hand-built system tells you what you are willing to understand, maintain, and debug once the pleasant idea of the project has been replaced by the project itself. That answer is usually more honest than the polished one.
So the full explanation remains what it was from the beginning. I felt like it. Then, in keeping with the spirit of unnecessary elaboration, that impulse was expanded into a section and given enough structure to pass for intent.