How rafin-110/ssp_village-action-group works
The repository is a Flutter frontend for a village/development-management application, but its README provides no product description and the sampled source contains no Dart implementation. The tree indicates user-facing workflows for authentication, issue reporting and progress, meetings, villages, submissions, and administration, with local storage, Supabase, and synchronization layers. The graph therefore maps these evident domains and likely runtime boundaries; links between Dart subsystems are omitted where the available evidence does not establish their callers.
Main entry points: logic Issue state · sync_manager.dart Sync manager · main.dart Flutter entry · screens Issue workflows
Components 22
App shell
- Flutter entry
lib/main.dart - App configuration
lib/app.dart - App routing
lib/core/router/app_router.dart - Sign-in screens
lib/features/auth/screens/login_screen.dart
Issue management
- Issue workflows
lib/features/issues/screens - Issue state
lib/features/issues/presentation/logic - Progress rules
lib/features/issues/domain/services/progress_rules_service.dart - Issue domain
lib/features/issues/domain/entities - Issue persistence
lib/features/issues/data/data_sources/issue_local_data_source.dart - Issue API
lib/features/issues/data/remote/issue_remote_data_source.dart
Community workflows
- Meeting workflows
lib/features/meetings/screens - Village workflows
lib/features/villages/screens - Submission flows
lib/features/submissions/screens - Dashboard
lib/features/dashboard/screens/dashboard_screen.dart
Administration
- Admin console
lib/features/admin/screens - Admin data state
lib/features/admin/presentation/logic
Data and services
- Sync manager
lib/core/sync/sync_manager.dart - Local database
lib/core/database/local_db.dart - Supabase auth
lib/core/auth/supabase_auth_service.dart - Supabase clients
lib/core/network
Other components
- User
- Supabase
Connections 19
- User → Flutter entry: opens app
- Flutter entry → App configuration: starts
- User → Sign-in screens: signs in
- User → Issue workflows: reports or updates
- User → Meeting workflows: manages meetings
- User → Village workflows: views villages
- User → Submission flows: submits work
- User → Admin console: administers
- Issue workflows → Issue state: uses issue state
- Issue state → Issue domain: handles domain data
- Issue state → Issue persistence: persists issues
- Issue state → Progress rules: checks progress
- Issue state → Issue API: accesses remote issues
- Issue persistence → Local database: stores locally
- Sync manager → Local database: synchronizes local data
- Sync manager → Supabase clients: uses API client
- Supabase clients → Supabase: accesses backend
- Supabase auth → Supabase: authenticates
- Admin console → Admin data state: uses admin state