and that's largely because it's not a collaborative document workflow, but a codebase workflow

and nip numbers have extremely complex, contextual relationships that are hard to follow without simply reading everything and then digging through all the PRs as well just to find out if you should put something in a field or expect something in a field or not

mostly it's a problem for client devs also, which also really reinforces my point about how while you all are busy making clients you are also gatekeeping the specs

seems like a recipe for loss of focus to me