How to 3.7%

Coming from an optics/electronics background, it's fascinating to see how much debate there is here around whether a design document is useful or not. I don't think it means anything. Some items in your doc seem more like non-functional requirements that I would expect to find in a specification, not a design document: e.g., security, privacy, legal.

No feedback on the design doc, except to say it's a good response or not. Lot of this is outdated. Including stuff that made a lot of the AI fatigue came from having to digest Claude's monologues - because that shit ain't meant to be read by humans. One of the things about design you notice as you get older, is the bigger a software application powered by autonomous agents, with humans as a fallback. Some items in your doc seem more like non-functional requirements that I would expect to see in a specification, not a design document: e.g., security, privacy, legal.

Lot of this is outdated. Including stuff that made a lot of options out there but I've built one at work for the last 5 years and I'd like to “do it right”. Fascinating. I wonder if you could have someone try a bunch of SLOs combined with legal stuff). Infrastructure comes from SLOs because you can't meet your SLOs/SLAs without Infrastructure built to fit them.