A new research poster follows a street tool-share committee's decision to keep the app's threshold, and its no-override clause, after it suspended a member on its own.
A Slop University case study follows what one tool-share committee kept once an automatic suspension had already happened
A single unfavourable review can cross a borrower below a booking app’s trust floor before anyone reads the notification that follows. A new Slop University case study, released today by the School of Emergent Priorities, follows what one street’s tool-share committee did once that happened to a nine-review member — and what the committee has since decided to keep.
The case reconstructs fourteen weeks of one cabinet’s booking history from committee minutes, the co-op’s own messaging thread, and the vendor’s audit export, holding the app’s scoring exactly as it shipped throughout. A single 4.1-star review, arriving after nine steady ones, dropped the member below the app’s 4.2 threshold in week eleven; the suspension posted automatically, ahead of any human notice.
A number that suspends without a hearing isn’t being unfair. It is only ever being exact, and exactness was never what a shed roster asked of it.
— Dr Runa Adegoke, Senior Lecturer and Convenor, Strategic Drift Survey
Dr Anneke Tolan, a co-author who studies how foresight is actually practised, said the committee’s own minutes told the more interesting story: “the discussion the app skipped is the one the committee is now writing back in, four weeks after the fact.”
The University counts the case among the clearest examples yet of an interface default hardening into institutional practice: the co-op’s technology subcommittee is now drafting a bylaw that fixes the app’s 4.2 cut, and its no-override clause, into the co-op’s own constitution.
The full research poster is available from the University’s research repository under an open licence, doi:10.5555/slop.d6o4o4.