starcoach-hackathon/zarinpal-analytics-backend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: define peer benchmark suppression

Browse Source
This commit is contained in:
Amirhossein Khalili
2026-08-20 13:26:51 +03:30
parent 6e0cc0b3fd
commit f91e529298
3 changed files with 32 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/DATA-FOUNDATION-SPEC.md
View File

@@ -156,7 +156,8 @@ Resolved: interpret timezone-naive source timestamps as `Asia/Tehran`, normalize
Resolved: retain `payer_card_key` unchanged as a restricted, merchant-scoped opaque source token for internal repeat-payer analytics. Do not HMAC it, expose it, log it, export it, or send it to AI providers. Its upstream semantics remain unverified. See ADR 0005.
Resolved: peer benchmarks exclude the active merchant and require at least 10 other merchants plus 1,000 combined peer sessions in the approved cohort/window. Otherwise the benchmark is suppressed as insufficient data; the merchant's own analytics remain available. See ADR 0006.
Remaining approval gates:
1. Minimum cohort size and suppression policy for peer benchmarks.
2. Physical partitioning/materialization strategy, which must follow measured query needs rather than the logical ERD alone.
1. Physical partitioning/materialization strategy, which must follow measured query needs rather than the logical ERD alone.