Status note (2026-09-25): Dated workstream record. Issue, PR and readiness states in this folder are snapshots, not live Project status. Verify current tickets, repository sources and tests before planning work.

MVP: Operational & Financial Analytics

TL;DR: workstream record for making creator, campaign, and staff figures explainable (balances, CPM spend, RPM expense, payout history). Orchestration record with snapshots — verify current tickets, sources, and tests before planning work.

Foundation audit: 2026-09-06, Asia/Manila. Owner: the next smart orchestrator. Implementation parent: backend #63.

Objective and scope

Make creator, campaign, staff, group, and sponsor figures explainable and reconcilable against persisted observations, funding, earnings, and payout allocations. Deliver correct accrued/pending/held/reserved/paid balances, campaign CPM spend and RPM expense, remaining funding, payout history, and required operational filters and time series.

This folder is the durable orchestration record. This session produced documentation only. No analytics product code, feature PR, issue closure, database mutation, or deployment was performed. The implementation workstreams remain ready or blocked, never complete merely because an issue says so.

Existing canonical domain docs remain authoritative for their domains; this folder records current-code corrections and the contracts analytics needs from them. It supersedes the older suggestion to deliver analytics in one late integration session in the sibling analytics handoff.

Verified baseline

Repository	Inspected main worktree / fetched branch	Commit
Backend	dev = origin/dev	226381bdef25f92a77d01f406e993c4c50f9350b
Frontend	dev = origin/dev	907963f
Metric scraper	main = origin/main; no local or remote dev exists	7fedb34
Canonical documentation	Workspace docs/, not a configured Git repository	No commit created

Existing backend docs/campaign-sponsor-reports.md modification and scraper untracked src/observability/ were preserved. Other worktrees were not used as the implementation baseline. No applicable filesystem AGENTS.md was found in the workspace/main repositories or ancestor chain; the session-supplied Conventional Commits instructions apply if a later session commits.

Current status and success criteria

Rates, continuous tracking lifecycle, canonical audit infrastructure, sponsor reports, and RBAC building blocks have landed. Financial journals, verified funding, payout allocations/Whop execution, durable fraud holds, group rate integration, and complete review history have not. Existing analytics are partially functional and financially inconsistent. See readiness for code versus deployment distinctions.

Completion requires all of the following:

• Every #51/#52 acceptance criterion and the integrated #28 group slice has a reviewed implementation and evidence, including dependency gates.
• Equal scope, currency, basis, cutoff, and coverage produce equal totals across creator, staff, group union, and sponsor projections.
• Funding, CPM spend, RPM expense, liabilities, reservations, confirmed payments, and corrections reconcile without rate recomputation or hidden double counting.
• Time series retain observation provenance, corrections, missing coverage, and explicit date semantics.
• Bounded queries, rollout compatibility, existing authorization, and sponsor privacy survive the changes.
• The verification plan passes on representative disposable fixtures, followed by the recorded manual and environment-specific release checks.

Navigation and maintenance

Start with handoff, then execution plan. Use issue tree, system map, financial contract, decisions, evidence, and the individual workstreams.

Before delegating, assign a workstream ID, repository, files, base commit, dependencies, and test command. After each PR, update its status/evidence, the issue acceptance mapping, readiness, and handoff in the same session. Revalidate only changed upstream contracts and branch/issue deltas; do not repeat this entire investigation. Keep business decisions separate from implementation proposals. Do not copy secrets, bearer report URLs, provider payloads, or personal records into this folder.