Wiki

Meeting 2026 05 22

Participants. Michell Zappa, Roy Bekhuis

Transcript. Granola share · chat with transcript (auth required)

Community platform vision

Location- and subject-based social network → Instant community.
- Combines three stakeholders: government, residents, entrepreneurs.
- "Democratic system of what needs to be done in a certain area."
- Cascading location model: house → street → neighborhood → city.
- Dynamic system combining themes with geographic boundaries.
Core differentiator from existing platforms.
- Not owned by government or company — owned by society.
- User controls what they see vs. algorithmic feeds.
- Focuses on building better communities, not personal opinions.
- Virtual world supports physical-world interactions.

Question types for community engagement:
1. Themes to be addressed (neighborhood priorities).
2. Feedback on government plans.
3. Goals and budget allocation (e.g. €300,000 neighborhood budget).
4. Event coordination and planning.
Subject classification system:
- Wiki-style ontology with related-subjects navigation.
- Content → subject classification using AI.
- Taxonomy approach (e.g. Healthcare with sub-categories).
- Metadata model based on existing frameworks.
Moderation approach:
- Formal communities: moderated by physical-world community boards.
- Informal communities: Reddit-style open-source model.
- Moderation board also meets in physical world.

Built on open-source foundations.
- OpenStreetMap for visual mapping.
- Government open data for postal codes, street information.
- Amsterdam's extensive open-data platform integration.
Event aggregation challenge.
- Bootstrap with existing government / municipal events.
- Need to aggregate Facebook, Meetup, Luma event data.
- Events as primary hook to drive platform adoption.
Map view as central interface.
- Everything geotagged and location-aware.
- Zoom in / out based on user interest and scope.
- No current aggregate view exists across platforms.

Roy's tasks:
1. Meeting with Minouche (innovation lead) within two weeks.
2. Gauge city-government interest and potential support.
3. Explore funding opportunities through municipal channels.
Michell's tasks:
1. Revise prototypes based on this briefing.
2. Update wiki with refined scope and focus.
3. Ready for follow-up discussion in 1–2 weeks.
Team building identified as critical success factor.
- Roy's previous attempt failed due to lack of organizational backing.
- Need project manager, advisory roles, technical team.
- Requires foundation / association structure (unprecedented in Netherlands).
Domain secured: uitwijken.nl ("from the neighborhood"). See Vision for the current framing.
Follow-up meeting: Friday, same time next week.

See History for the broader timeline.