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.
Owner Clarifications
All four audit questions were resolved by the owner on 2026-09-03. These decisions are retained here as product context for the live tickets.
RESOLVED MVP DECISIONS
CLARIFY-001 — Private campaign access model
Why this matters
Every authenticated user can currently list every launched campaign. The private rollout needs an enforceable definition of “permitted creator.”
What we know
Authentication and social-account ownership exist. ClipperGroup is campaign-specific but is not consulted by campaign listing or submission creation.
Decision
Active membership in a campaign-specific Clipper Group grants access to that campaign. There are no global Clipper Groups. A private campaign is accessible only to creators in active groups belonging to it.
Blocks
CLARIFY-002 — RPM precedence and overlapping groups
Why this matters
The current application has campaign RPM and submission customRate; groups have no rate. A creator may currently belong to multiple groups, including potentially multiple groups for one campaign.
What we know
CPM must remain independent from creator RPM. Rate changes must not rewrite prior earnings.
Decision
Creators may belong to multiple groups under the same campaign. Resolve the applicable RPM as the highest numerical value across the campaign RPM, all active applicable group RPMs, and the individual creator override. No rate source receives priority merely because of its type.
Blocks
CLARIFY-003 — Fraud finality and post-payment correction policy
Why this matters
Existing badges are advisory and bulk approval ignores them. A safe hold duration and correction rule are needed before earnings become payable.
What we know
Current signals include view history, low engagement ratios, sudden spikes, unavailable videos, and manual item decisions.
Decision
Use conservative rule-based holds with manual release. Use seven days as the tentative finality period, but the implementing developer must seek owner confirmation before shipping. A confirmed post-payment correction becomes attributable recovery due.
Blocks
RESOLVED MVP DECISION
CLARIFY-004 — Minimum client analytics
Why this matters
“All analytics on every end” may include the older unauthenticated share-link dashboard, but expanding to it silently would change MVP scope.
What we know
Creator/admin/campaign dashboards exist; no client access model or share-token analytics route was found.
Original decision
Defer the client-facing dashboard from MVP. Create a separate non-MVP ticket for a revocable read-only campaign link that exposes aggregate campaign statistics only. It must not expose individual creator/clipper payouts.
Superseding implementation decision
On 2026-09-05, the owner promoted the revocable read-only sponsor/client analytics link into MVP scope. Backend c9e5448 merged the audited report-token and public report implementation, and frontend fcf4809 plus 907963f merged shareable sponsor reports and expiry disclosure. The link remains read-only and token-scoped; client write access, a general client account system, deeper BI, and unrestricted creator financial records remain out of scope.