Cologne subculture · Version 1.1 · · Architecture proposal
Category: Infrastructure
Art of Urban Life
Infrastructure.
🔊 Listen to this article
An audio recording is not yet available for this article.
A collection of independently operated WhatsApp groups does not automatically become a platform. But shared data, clear roles and an editorial workflow could turn it into coordinated infrastructure for electronic culture in Cologne.
Groups remain independent. Art of Urban Life coordinates content, permissions and distribution across them.
This report describes a planned system, not existing software or a confirmed organisational structure.
01 / Starting point
Art of Urban Life grew out of a community network for electronic events, secret raves, open-air events and club culture in Cologne. Information is currently distributed through various WhatsApp groups and their administrators. The groups are loosely organised and managed differently. Reach is estimated to be in the five figures; overlapping membership currently prevents a reliable count of unique recipients.
The challenge is not to reinvent WhatsApp. It is to make submissions, approvals and publication traceable without taking control away from the established community.
02 / Target architecture
Organisers → Submission → Editorial team → MySQL → Admins → WhatsApp groups
03 / Data model
The MVP distinguishes communities (optional), groups, admins, group_admin_roles, events, submissions, distribution_targets and distribution_log. A group can have several administrators; an administrator can manage several groups. This assignment is modelled as a separate relation.
Initially, only data needed to operate the system is stored. Member lists, phone numbers, invitation links and internal group identifiers do not belong in a public report.
04 / Permissions and publication
05 / Automation – with limits
There is no general official interface for fully automated management of existing WhatsApp groups. A Chromium/Playwright agent for WhatsApp Web would be an experimental integration with risks from interface changes, terms of use and account restrictions. The MVP therefore starts with a manual approval and distribution workflow. Later automation will be assessed separately and must not circumvent platform restrictions.
06 / Privacy and security
No secrets in the public architecture: this report uses only abstract roles and example data. Credentials, phone numbers, WhatsApp invitation links, session cookies, personal administrator assignments and internal IDs remain outside public documentation. Where published identifiers are unavoidable, stable pseudonyms with a secret key are preferable to simple hashes that can be reverse-engineered from small input sets.
Future operation requires access rights, change logs, a deletion policy, legal bases and proper handling of commercial advertising.
07 / Implementation with GitHub and Codex
Development follows a traceable workflow: requirements are documented as a GitHub issue (task), then implemented by a coding agent such as Codex, committed and pushed to the repository. Deployment follows review and testing. A commit or push alone does not mean the website is live.
Concept → GitHub issue → Codex → Commit & push → Review / tests → Deployment
This is the planned development process for the infrastructure, not a claim that WhatsApp automation is already running in production.
08 / Roadmap
- Phase 0: voluntarily record groups and administrators, confirm responsibilities.
- Phase 1: MySQL data model, event intake, editorial approval, manual distribution and audit log.
- Phase 2: discuss roles, advertising policies, name and trademark checks, and possible sponsorship.
- Phase 3: agent prototype only after technical and legal assessment.
09 / Open organisational question
An independent initiative, a separate association or sponsorship by an existing association are possible options. None has been decided. The competent association body would have to decide on any involvement by Arts & Culture Germany e.V. A trademark application also requires checking existing rights and clarifying ownership.
Conclusion
More structure. No less subculture.
The goal is a reliable editorial layer for a decentralised scene, rather than a centrally controlled chat network.
Public architecture proposal · No internal credentials or group lists included.