Appearance
Historical snapshot archived 2026-09-25. This records an earlier review or plan, not current implementation or live ticket state. For current work, follow root AGENTS.md, the relevant BloxClips skill, and owning repository source/tests. Preserve approved decisions as evidence; verify their present authority before acting.
MVP Dependency Map
Critical path
text
Whop invoice records -> idempotent invoice reconciliation -> funded campaign
-> finance permission -> campaign launch -> creator access
Accepted-only scheduler -> ScrapeJob worker/reconciliation -> metric observations
-> CPM/RPM policy snapshot -> budget debit + creator earning
-> fraud/finality state -> payout reservation
-> Whop transfer operation -> provider reconciliation -> paid stateCross-cutting controls:
text
RBAC -> campaign finance, review, group rates, payouts, analytics, staff management
Audit -> funding, lifecycle, moderation, rate changes, fraud decisions, payoutsParallel work
- RBAC schema/guards, Whop invoice adapter, Whop transfer adapter, review query work, and tracking eligibility can begin independently.
- Clipper Group RPM configuration can proceed while owners decide conflict precedence; applying the rate to accrual waits for that decision.
- Metric breadth and analytics query work can proceed after the observation schema is agreed, but financial analytics must wait for authoritative journals.
- Support Chat needs runtime verification only and is not on the financial critical path.
Ordering constraints
- A campaign cannot launch until funding is locally verified and the caller has the finance permission.
- Earnings cannot be authoritative until CPM/RPM, accepted-view delta, precision, and correction rules are fixed.
- A payout cannot reserve money until earnings are payable and fraud/finality gates have passed.
- A provider timeout cannot be retried as a new transfer until reconciliation proves that no transfer moved.
- Analytics must project from authoritative facts; it must not define accounting behavior itself.