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

docs: approve Ent and pgx data access

Browse Source
This commit is contained in:
Amirhossein Khalili
2026-08-20 13:12:51 +03:30
parent 2426c1ed33
commit 491c673153
3 changed files with 38 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -150,10 +150,11 @@ Resolved: use a capability-oriented modular monolith, with lightweight ports/ada
Resolved: use manual constructor injection with explicit wiring at thin `cmd/` composition roots. See ADR 0002.
Resolved: use Ent for application persistence/modeling and pgx/PostgreSQL `COPY` for streamed bulk-ingestion staging. Migrations are explicit and versioned; production startup never performs automatic schema changes. See ADR 0003.
Remaining approval gates:
1. PostgreSQL access stack: ORM choice plus a bulk-ingest path suitable for 2.2M+ rows.
2. Source timestamp timezone and daylight-saving assumptions.
3. Whether `payer_card_key` must be retained, irreversibly transformed, or omitted after derived analytics.
4. Minimum cohort size and suppression policy for peer benchmarks.
5. Physical partitioning/materialization strategy, which must follow measured query needs rather than the logical ERD alone.
1. Source timestamp timezone and daylight-saving assumptions.
2. Whether `payer_card_key` must be retained, irreversibly transformed, or omitted after derived analytics.
3. Minimum cohort size and suppression policy for peer benchmarks.
4. Physical partitioning/materialization strategy, which must follow measured query needs rather than the logical ERD alone.