Description
Problem
Account activity can be retrieved, but there is no structured reporting layer for categorizing transactions or preparing account-level compliance data. Consumers must independently transform raw activity into audit-friendly records.
Solution
Introduce a reporting pipeline that normalizes account activity, categorizes transaction behavior, and produces framework-specific report structures. The design should allow additional compliance rules to be introduced without changing the underlying activity retrieval APIs.
Acceptance Criteria
Note for Contributors
Treat this as a reporting abstraction rather than a legal compliance engine. Keep framework rules configurable and avoid embedding assumptions about jurisdiction-specific regulatory requirements.
Description
Problem
Account activity can be retrieved, but there is no structured reporting layer for categorizing transactions or preparing account-level compliance data. Consumers must independently transform raw activity into audit-friendly records.
Solution
Introduce a reporting pipeline that normalizes account activity, categorizes transaction behavior, and produces framework-specific report structures. The design should allow additional compliance rules to be introduced without changing the underlying activity retrieval APIs.
Acceptance Criteria
generateComplianceReport(account, framework)is introducedsrc/account/index.tsandsrc/index.tsNote for Contributors
Treat this as a reporting abstraction rather than a legal compliance engine. Keep framework rules configurable and avoid embedding assumptions about jurisdiction-specific regulatory requirements.