Design AnnualStatsResult and MilestoneDefinition data models
epic-annual-impact-summary-core-services-task-003 — Define the Dart data classes for AnnualStatsResult (total_hours, unique_contacts_helped, activity_type_distribution as Map<String,double>, streak_days, period_start, period_end), MilestoneDefinition (id, threshold, metric_key, significance_rank, description_template), and MilestoneResult (definition, is_newly_unlocked, formatted_description). These models are the shared contracts between the aggregation service, detection service, and BLoC.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 1 - 540 tasks
Can start after Tier 0 completes
Implementation Notes
Place all three classes in lib/features/annual_summary/domain/models/annual_stats_result.dart (or separate files per class if the project convention is one class per file). Use Map.unmodifiable() when assigning activityTypeDistribution so the getter always returns a read-only view. For MilestoneResult, compute formattedDescription in the constructor (or a factory) by calling descriptionTemplate.replaceAll('{value}', value.toStringAsFixed(1)) — this keeps the presentation logic in one place. Consider defining a MetricKey class (or enum) with constants matching the AnnualStatsResult field names (e.g.
MetricKey.totalHours = 'totalHours') so MilestoneDefinition.metricKey is type-safe. This small addition eliminates an entire class of runtime bugs when the detection service evaluates thresholds via reflection or switch statements.
Testing Requirements
Unit tests only (flutter_test). Four test groups: (1) AnnualStatsResult — constructor with valid data; empty() factory; assert fires when distribution does not sum to ~100.0; equality and hashCode; (2) MilestoneDefinition — basic construction and equality; (3) MilestoneResult — formattedDescription correctly substitutes {value} placeholder with threshold formatted to one decimal place; (4) Immutability — verify activityTypeDistribution cannot be modified after construction (access the map and attempt mutation, expect UnsupportedError). Target 100% branch coverage for these model files.
Activity records may contain duplicate entries (as evidenced by the duplicate-detection feature dependency) or proxy-registered activities that should be attributed differently. Including duplicates or mis-attributed records would produce inflated stats, undermining trust in the summary.
Mitigation & Contingency
Mitigation: Implement the aggregation query to join against the deduplication-reviewed-flag on activity records and filter out unresolved duplicates. Coordinate with the duplicate-detection feature team to confirm the authoritative flag field before implementing the RPC. Include a data-quality warning in the summary when unresolved duplicates are detected.
Contingency: If deduplication state is unreliable at release time, add a prominent disclaimer in the summary UI noting that figures reflect all registered activities and may include duplicates pending review. Track a follow-up task to re-aggregate after deduplication runs.
Each organisation wants to define their own milestone thresholds (e.g., NHF's counting model differs from HLF's certification model). Implementing configurable thresholds may expand scope significantly if the configuration UI is expected in this epic.
Mitigation & Contingency
Mitigation: Scope this epic strictly to the evaluation engine and a hardcoded default threshold set. Define the MilestoneDefinition interface with an organisation_id discriminator so per-org configs can be loaded from the database in a later sprint. Build the admin configuration UI as a separate follow-on task outside this epic.
Contingency: If stakeholders require per-org milestone configuration before launch, deliver a JSON-based configuration file per org as an interim solution, loaded from Supabase storage, until a full admin UI is built.
Android 13+ restricts access to media collections and requires READ_MEDIA_IMAGES permission for gallery saves, while older Android versions use WRITE_EXTERNAL_STORAGE. Handling both permission models correctly across the device matrix is error-prone.
Mitigation & Contingency
Mitigation: Use the permission_handler Flutter package with version-aware permission requests abstracted behind the summary-share-service interface. Write platform-specific unit tests for both Android API levels in the test harness. Test on a minimum of three Android versions (API 29, 32, 34) in CI.
Contingency: If gallery save is broken on specific Android versions at launch, disable the 'Save to gallery' option on affected API levels and surface only clipboard and system share sheet, which require no media permissions.