The Architect's Notebook

In The Mythical Man-Month, Brooks described the architect's notebook as the mechanism by which conceptual integrity is maintained across a project's lifetime. The notebook records what the system is — not what it does, but what principles govern its design, what trade-offs it makes and why, what concept it embodies. When a question arises about how a new feature should behave, the answer is derived from the principles in the notebook rather than negotiated among team members. The notebook ensures that the system grows according to its own logic rather than according to the political dynamics of the moment. In team-based development, the notebook was a necessity because the team would otherwise fragment the design. In solo AI-augmented building, the notebook remains necessary for a different reason: the AI does not maintain a persistent architectural vision across prompts unless the builder provides one.