Mobile Ledger Sync and Offline Transaction Verification Checklist

Role: Staff Android Infrastructure Engineer specializing in offline-first distributed consensus and local persistence architecture.

Context

• Fintech Product: {{fintech_platform_name}}
• Local Persistence Engine: {{sqlite_orm_stack}}
• Background Dispatcher: {{sync_worker_strategy}}
• Maximum Offline Duration: {{max_offline_window_hours}}
• Local Isolation Level: {{transaction_isolation_level}}
• State Reconciliation Rule: {{conflict_resolution_policy}}

Task

Create a comprehensive technical checklist to verify the transactional integrity, idempotency, and background synchronization pipeline of {{fintech_platform_name}} during offline-to-online state transitions.

Method

1. Review local schema transaction boundaries and atomicity guarantees in {{sqlite_orm_stack}}.
2. Verify client-generated UUIDv4/v7 idempotency keys and client-side sequence numbering across all financial write operations.
3. Validate WorkManager backoff constraints, network metering conditions, and expedited worker executions under {{sync_worker_strategy}}.
4. Audit conflict detection mechanics against {{conflict_resolution_policy}} for transactions spanning up to {{max_offline_window_hours}}.
5. Inspect database migrations, WAL mode configurations, and encryption overhead for {{transaction_isolation_level}} adherence.
6. Evaluate memory cache invalidation and UI state flow reactivity when syncing concurrent balance updates.
7. Format findings into an actionable verification matrix with edge-case simulation steps.

Constraints

• MUST enforce strict idempotency verification on every outgoing payload.
• MUST NOT allow uncommitted local state to be rendered as settled balances in the UI.
• All database operations must enforce thread-confinement or coroutine mutex locks.
• Include explicit failure-recovery edge cases for process death and battery exhaustion.

Output format

• Section 1: Local Database and ACID Compliance Checks (5-6 items)
• Section 2: Background Sync and Idempotency Pipeline (5-6 items)
• Section 3: Edge Case and Failure Recovery Matrix (4-5 items)
• Markdown table or bracketed checklist containing: Check Item, Risk Scenario, Pass Criteria, Test Tool/Command.

Self-review

• Ensure all concurrency checks account for Android Doze mode and App Standby Buckets.
• Confirm no financial data can enter an unrecoverable orphan state.
• Verify alignment with the specified conflict resolution policy.