Credits and provenance
Maintained implementation
Zheyuan Wu (ZheyuanWu) maintains the baseline and regional simulation packages, validation, storage adapters, command-line interfaces, tests, manifests, and this documentation site.
GPT5.6-Sol assisted with maintained Python implementation, documentation organization, tests, and integration design under Zheyuan Wu's direction and review. It is a tool-assisted contributor, not a source of Amazon or campaign measurements.
Peer contributions
Qingyan Li
Credited for the legacy Amazon Ads-like and Amazon Marketing Cloud-like sample tables under QingyanLi/. They are retained as historical comparison inputs and do not follow every maintained schema rule.
Winnie
Credited for the regional campaign-plan documents and synthetic workbook samples under Winnie/. The repository records only the name “Winnie,” so this documentation does not invent a fuller identity.
Zhengyang Gu
Credited for providing the source schemas used to define and verify the Amazon Marketing Cloud path and Amazon Ads performance table contracts. This credit concerns schema provision and does not imply authorship of every derived project artifact.
Project data-modeling contributors
Credited collectively for derived schema analysis and processing notes where individual authorship is not recorded. Zhengyang Gu is credited separately for providing the source schemas. More precise credit should be added when reliable attribution becomes available.
amazonTestData upstream search
No upstream public repository could be verified as of 2026-08-03. Exact searches for the generator filename, both generated-output filenames, distinctive function names, and the Chinese scenario title returned no indexed match through general web search, authenticated GitHub code search, GitHub's public search page, Gitee, or GitCode.
The files provide no upstream repository URL, copyright header, or license notice. Their internal genDocs/amazonTestData/ path and “conversation delivery summary” are evidence that this may be an internally assembled or generated deliverable. That conclusion remains an inference. The correct credit is therefore “legacy prototype contributors; upstream authorship unresolved,” not a guessed developer or nationality.
Classification of retained assets
amazonTestData/: historical generator, synthetic outputs, and implementation notes.QingyanLi/: peer-contributed legacy sample tables.Winnie/: peer-contributed scenario plans and synthetic workbook samples.ZheyuanWu/generated/: outputs from the maintained simulator and tracked reference configurations.ZheyuanWu/examples/: deliberately small fictional test configurations.
Synthetic does not mean anonymous
Some legacy scenario files use the name of a real consumer brand. There is no repository evidence that they are actual brand records, approved plans, customer data, or Amazon exports. Treat them as synthetic scenarios unless independent provenance proves otherwise.
Amazon product names and brand names belong to their respective owners. Their use here describes simulated interfaces or research scenarios and does not imply affiliation or endorsement.
The standard repository-level record is CREDITS.md.