docs: define source timestamp normalization

This commit is contained in:
2026-08-20 13:15:11 +03:30
parent 491c673153
commit 2753162a75
3 changed files with 32 additions and 6 deletions

View File

@@ -12,7 +12,7 @@ For every Go-related task, always invoke and follow the `golang-how-to` skill, t
- Every merchant-scoped query derives merchant identity from the authenticated server-side session; never trust a client-supplied merchant identifier as authorization.
- Cross-merchant results are minimum-cohort, anonymized aggregates only.
- Use integer minor currency units or an explicitly documented fixed-precision representation; never floating point for money.
- Preserve source timestamps and document their timezone assumptions. Normalize operational timestamps consistently.
- Interpret timezone-naive challenge timestamps as `Asia/Tehran`, preserve their source provenance, and normalize canonical database/API timestamps to UTC `timestamptz`/ISO 8601. Any change to this assumption requires a new import version and ADR.
- Raw imports are immutable inputs; corrections are new import versions, not silent mutation.
- `adjusted_fee` is obfuscated and may be used only for relative analysis.