HAAM Labs · Concept Directory
What would a trustworthy interface for swimmable cities look like?
This concept explores how cities could connect verified water-quality data, public access, ecology, and community evidence. It is an information-architecture prototype, not live swimming-safety guidance.
Safety notice
Do not use this concept page to decide whether to enter the water
Conditions can change quickly. A production service would require current official feeds, local governance, and clearly accountable safety communication.
Always consult local authorities and current on-site warnings before swimming. The cities below are design-research examples rather than status reports.
Information model
Four layers that belong in one public experience
A single quality score is too blunt. People need provenance, context, access information, and a clear account of uncertainty.
Water conditions
Latest verified sample, measurement time, source, confidence, weather context, and clearly separated official warnings.
Access and inclusion
Entry points, steps or ramps, changing facilities, public transport, seasonal access, and accessibility notes.
Local ecology
Biodiversity context, sensitive habitats, pollution sources, restoration work, and guidance for low-impact use.
Community evidence
Moderated observations, photographs, corrections, local campaigns, and a visible distinction between reports and measurements.
Concept directory
Cities and questions worth studying
These entries identify research directions. They intentionally avoid making claims about current water conditions.
Harbour
Copenhagen
How can swimming become ordinary public infrastructure?
Fjord
Oslo
How do access, ecology, and urban development share the shoreline?
Seine
Paris
How should major clean-up investment become transparent to residents?
Spree
Berlin
How can civic campaigns make water-quality progress legible?
East River
New York
What information would make new swimming infrastructure trustworthy?
Thames
London
How should changing conditions and local restrictions be communicated?
Trust architecture
Rules for a production pilot
The interface should become less confident when the evidence becomes weaker.
- Never describe water as safe without a current, attributable official source.
- Show timestamps and sampling locations beside every measurement.
- Keep community reports visually distinct from laboratory or sensor data.
- Explain uncertainty and missing data instead of manufacturing a simple score.
- Design multilingual, low-bandwidth, keyboard-accessible views from the start.
- Give local authorities and community partners a documented correction path.