The design and motivations document is pretty long but doesn’t really describe the design. Things like which language you use aren’t the design, they’re more li

The design and motivations document is pretty long but doesn’t really describe the design. Things like which language you use aren’t the design, they’re more like design constraints and the environment in which the design happens. The document about branching strategy [1] is closer to what I’d expect of a design doc. But it avoids the hard problem of how live merges to the child branch work. What happens when a large refactoring automatically happens in the background while you’re in the middle of editing? In a fast-moving repo, it seems like new compile errors could spontaneously appear at any time, or tests could start breaking on their own. It seems like it would be frustrating to debug. [1] https://github.com/ScottArbeit/Grace/blob/main/docs/Branching%20strategy.md https://github.com/ScottArbeit/Grace/blob/main/docs/Branchin...