DATA ENGINEERING / SYNTHETIC EXPERIMENT
17 synthetic events · deterministic policies · original educational example, 2026.10.13
| Row | ID | Timestamp (UTC) | Group | Amount | Audit state |
|---|
01 / NOTES & EVIDENCE
Zero is an observed value; a missing amount is unknown. Strict UTC validation rejects impossible calendar dates. Equal IDs with different business fields require a stated conflict policy. Amounts are aggregated as integer cents.
Original Spark & preparation notes →A new browser experiment using synthetic events and PapaParse. The core has automated checks for zeros, calendar boundaries, conflict policies, reconciliation and idempotence. It does not run Spark or benchmark distributed processing.
Read the automated checks →Prepared from local data engineering study topics. No textbook pages, examination questions, private records or production data are included. The sample uses a 2000–2099 UTC date contract and two-decimal amounts within ±1,000,000.
Reproduction & limitations →