[Nothing Recomputable]
Tiered Affiliates Dashboard
One route, two readings by role — and no hidden number can be rebuilt from what's left on screen.
Three requests — hide sensitive data from affiliates, give the AOV team a front-end × back-end view, create access levels — were about to become three dashboards.
Saw they were one problem and built one dashboard with cuts by role.
Affiliates needed their own numbers without being able to infer what's reserved for masters and owners.
01 · Member cut
Revenue, net, net % and refund + chargeback rate. No order counts (revenue ÷ orders = AOV) and no affiliate filter.
02 · Master / owner
Everything, plus channel chips (front end, recovery, monetization, broadcast, brand bidding), a back-end/front-end AOV column, a detail ⇄ macro toggle and best/worst warnings.
03 · The recomputability rule
If a number can be recomputed from what's left — on screen or in the CSV — it wasn't hidden.
04 · One truth
Formulas shared with the AOV dashboard and checked number by number, so the two can't drift.
what you're seeing
The KPI cards a member or a master sees. You choose what to hide from members; the leak detector checks whether a hidden number can be rebuilt from what's left — on screen or in the exported CSV.try this
- 1.As Member, hide only AOV: the detector shows it leaks through revenue ÷ orders.
- 2.Hide order count too — now the cut is consistent.
- 3.Turn on CSV export: the file carries the hidden columns until “CSV follows the screen cut” is on.
real vs simplified
The rule and the leak paths are the real ones behind the affiliates dashboard. The program and its numbers are fictional.! brokeHiding the filters in the UI wasn't enough: affiliate values passed in the URL still filtered the data, and the per-affiliate query still fired.
→ changedMember requests drop those parameters, and the breakdown query isn't sent at all.