Skip to content

A16 — Group and member analytics views ​

Status: blocked. Updated: 2026-09-06. Assigned agent: unassigned. Implementation PR: none.

Issues and acceptance covered ​

#28, #52. The acceptance boundary is the implementation scope and completion checks below; see the issue acceptance matrix for parent coverage. Shared definitions: financial contract; proof anchors: evidence index.

Dependencies and blockers ​

A09 and A11 formatter. Group CRUD/rates remain #26/#27; #76 required for full real fixture walkthrough. D-04 needed only for a requested additive variant.

Repository and expected files ​

Frontend: features/admin/clipper-groups, surfaces/content-rewards/screens/admin/clipper-groups; existing campaign/archive group selectors and detail roster.

Existing behavior and verified gap ​

Group list/detail can show campaign-owned membership history but no selected-period counts/views/earnings or financial coverage (E22).

Proposed implementation boundary ​

Add period/platform controls where contract supports, group summary and paginated member breakdown, archived reporting, clear historical membership/cohort scope and union/unattributed reconciliation. Preserve group ownership and rate management workflow.

Expected API / data contract ​

Consume A09 exact amounts/counts/time basis/coverage; no current-roster client join or summing overlapping group tiles into campaign total.

Required tests ​

Leave/rejoin/overlap/archive/unknown member; member pagination versus full group summary; mismatched campaign; no groups; denied/error/loading; cohort disclosure and union equality. Focused API tests, lint/build, manual fixture.

Suggested agent tier ​

Lower-cost UI agent; smart owner validates temporal membership and non-additive comparison.

Expected PR boundary and reason ​

One group analytics UI PR stacked on A09/A11. Completes #28 presentation acceptance with backend evidence; do not close #28 until full reconciliation/manual checks pass. Unlocks A17. Keep compatibility additive, avoid unrelated cleanup, and list exact stacked commits and later units unlocked in the PR. If observed scope grows beyond this boundary, update the plan before splitting or adding work.

RBAC requirements / TODOs ​

Preserve Clipper Group admin access. TODO(RBAC): Require approved campaign-group analytics/member compensation visibility; group membership management access is not a new unrestricted financial grant.

Completion and reconciliation checks ​

Each full member breakdown reconciles to group total; overlapping group totals carry explicit cohort scope and campaign union. Archived data readable without making group globally reusable.

Record actual tests, source schema/contract versions, PR/merge SHA, manual evidence and residual coverage before changing status to review/complete. Any unexpected migration must first satisfy the migration gates; never bundle upstream financial writer work into this analytics unit.