Document the methodology (thinking about design choices)

[drewdeponte]

In my mind this is explaining things like the fact that we make choices to force integration as early and quickly as possible to stay as close to a single shared truth as possible, and keeping conflict surface area small and reasonable to manage.

Or the choice to manage the concept of dependency strictly by position within the stack rather than making the user build a DAG of branches or someother structure to understand the dependencies.

This probably boils down to what the goals of the project are overall eventually. But I think having something that explains these goals and tangible examples and choices that have been made to align with the goals makes it far more real for people.

[drewdeponte]

I recently created an audio recording and transcript talking about this, https://drewdeponte.com/blog/git-patch-stack-goals/

It might be a good reference to create something more formal.