Consider OpenMeet groups as shared community layer instead of building our own

[zhiganov]

Discovery

OpenMeet already has a full group management system with:

• Group CRUD (create, join, leave, manage)
• "Groups you organize" / "Groups you're part of" on their dashboard
• ATProto DID-based membership (group-did-follow)
• API endpoints (src/group/group.controller.ts)

This is essentially what community-admin V1 is designed to build — community registration, membership, organizer roles.

Impact on roadmap

Before building community-admin's own community/membership system (V1), we should evaluate:

1. Can OpenMeet groups serve as the community layer? If users create groups on OpenMeet, can Avails/scenius-digest/my-community read those groups via API?
2. What's missing? OpenMeet groups likely don't have Telegram channel mappings, event source configs (Luma/guild.host), or link collection topics. Those are Citizen Infra-specific concerns.
3. Hybrid approach? OpenMeet handles identity + membership + events. Community-admin adds the Citizen Infra-specific config (Telegram, link digests, event sources) on top of OpenMeet groups.

Possible architecture

OpenMeet Groups (ATProto-native)
  = identity, membership, events, RSVPs
  
community-admin (Citizen Infra layer)
  = Telegram config (group_id, topics, output_channel)
  = Link digest config (which topics to monitor)
  = Event source config (Luma, guild.host)
  = references OpenMeet group by DID/slug

This would mean community-admin is a thin config layer on top of OpenMeet groups, not a standalone community system.

Action items

• Explore OpenMeet group API endpoints (blocked by ATProto scope issue — OpenMeet publish blocked by ATProto OAuth scope upgrade — no re-consent prompt avails#49)
• Discuss with Tom (OpenMeet) about API access for third-party apps
• Evaluate if V1 scope can be reduced by using OpenMeet for identity/membership

Related

• Explore OpenMeet groups API as community source for polls avails#50 — OpenMeet groups as community source for polls
• Expose GET /api/config endpoint for scenius-digest and Avails #9 — config API (may become a thin wrapper around OpenMeet groups)
• Telegram bot onboarding for self-service community registration #10 — Telegram bot onboarding (still needed regardless)