Skip to content

Prompt Record

This page preserves a compact record of what the user asked Codex to do. It is a continuity aid, not a substitute for requirements, code review, meeting notes, or source evidence.

Prompt summaries should describe goals and constraints without copying secrets, credentials, personal data, or unnecessary verbatim conversation.

Recording rule

At the end of every repository task:

  1. add a dated entry;
  2. summarize the requested outcome and important constraints;
  3. list material decisions or assumptions;
  4. record whether the task was completed, partially completed, or blocked;
  5. name the main files or areas affected;
  6. state in the final response whether the prompt was recorded.

2026-07-30 — Repository attribution, manifest authors, and training-file contract

Recording status: Recorded

Requested outcome: Add the GitHub repository link to the documentation site and generated manifests; identify ZheyuanWu and GPT5.6-Sol as authors; explain every generated file, its training or evaluation role, and its relationship to MTA数据处理方案_简明版.md; then commit the maintained changes.

Important constraints: Keep synthetic outcomes distinct from Amazon observations, never expose simulation ground truth as a training feature, distinguish path outcomes from Amazon Ads diagnostic conversions, preserve read-only context files, verify generated datasets and documentation, and leave pushing to the repository owner.

Material decisions:

  • Active dataset manifests use manifest_version: 2 with repository_url and ordered authors fields.
  • The documentation navigation, GitHub icon, home page, and footer expose repository and author information.
  • Generation Flow treats the path and performance tables as model inputs, simulation ground truth as evaluation-only, validation as a quality gate, the manifest as provenance, and SQLite as alternative storage.
  • The specification mapping separates finalized result-table compliance from upstream Amazon Marketing Stream ingestion features that are not implemented.

Completion status: Completed. Seven baseline tests and five regional tests passed; all four active datasets were regenerated with manifest version 2; and the VitePress production build passed.

Main affected areas: VitePress configuration and home page, dataset-creation/generation-flow.md, shared manifest generation and tests, active generated dataset manifests, README.md, and this prompt record.

2026-07-30 — Regional Gini equation rendering repair

Recording status: Recorded

Requested outcome: Repair the regional documentation where the multi-line Gini noise equation and its following inline bound appeared as raw or missing LaTeX.

Important constraints: Keep descriptive parameter names, avoid Greek parameter symbols, preserve the documented behavior formula, and verify the VitePress output.

Material decision: Introduced inequality adjustment as an intermediate mathematical quantity so \max no longer spans an alignment line break.

Completion status: Completed. The VitePress build succeeded; the rendered regional page contains three MathJax containers, no raw aligned block, and the intermediate quantity appears in both the display equation and inline bound.

Main affected area: ZheyuanWu/docs/dataset-creation/regional.md.

2026-07-30 — Baseline and regional separation with modular documentation

Recording status: Recorded

Requested outcome: Replace long confidence text in headings with short colored badges; divide Dataset Creation into linked pages; preserve a peer-compatible baseline without new economic parameters; move regional variations into simulations/regional/; render equations with LaTeX and descriptive notation; document the overall generation flow, each baseline parameter group, regional parameters and outputs, and detailed future recommendations.

Important constraints: Keep all dataset-creation pages except NOTATIONS.md under docs/dataset-creation/; avoid parameter tables; link parameter uses back to their first definitions; use no Greek parameter names; copy code examples from maintained source; keep context directories read-only; and retain reproducible Comma-Separated Values and SQLite output.

Material decisions:

  • Baseline generator version 1.0.0 now owns only peer-compatible campaign parameters and neutral marketplace behavior.
  • Regional generator version 0.1.0 owns internet reach, target-audience density, economic willingness, Gini context, provenance, and confidence.
  • The shared simulator accepts an explicit behavior provider, so schemas, validation, and storage are not duplicated.
  • Status text is rendered by compact right-aligned color badges without changing heading anchors.
  • VitePress MathJax support is enabled, and NOTATIONS.md defines every mathematical convention used.
  • SQLite output is rebuilt atomically so repeated runs in the same directory retain deterministic file hashes.

Completion status: Completed. Seven baseline tests and five regional tests passed. Baseline and all three regional scenarios reported zero validation errors. Repeated baseline manifests and regional Comma-Separated Values outputs were byte-identical. Windows and Linux documentation launchers both completed the VitePress production build.

Main affected areas: ZheyuanWu/simulations/baseline/, ZheyuanWu/simulations/regional/, ZheyuanWu/generated/, ZheyuanWu/docs/dataset-creation/, ZheyuanWu/docs/NOTATIONS.md, VitePress theme and navigation, README.md, AGENTS.md, and ZheyuanWu/pyproject.toml.

2026-07-30 — Dataset creation baseline and regional economic scenarios

Recording status: Recorded

User goal: Add a Dataset Creation section beginning with baseline.md; explain how the synthetic dataset is generated, how it differs from original code, and what every global and feature parameter means using contextual examples and supporting evidence. Move the maintained generator and configuration into ZheyuanWu/simulations/baseline/. Add more realistic hidden economic influences and generate separate Europe, Japan, and North America datasets using real economic inputs and selected read-only Winnie scenario assumptions. Rank confidence for every estimation. Add this prompt record and a permanent project rule requiring future task prompts to be recorded.

Important constraints:

  • Keep code and technical identifiers in English.
  • Do not present synthetic or modeled behavior as Amazon data.
  • Preserve context directories as read-only.
  • Cite papers, official sources, or clearly labeled common reasoning.
  • Keep low-confidence mappings visible for data-modeling team review.

Material decisions:

  • The existing deterministic generator became baseline version 0.2.0.
  • Economic inputs adjust audience volume, conversion odds, or daily variation; they do not become model features.
  • The Gini coefficient changes variation rather than mean demand.
  • World Bank indicators provide source-dated population, exchange rate, internet reach, household-consumption growth, and income-inequality inputs.
  • Population-to-campaign traffic, target-audience density, and Winnie conversion targets remain low-confidence assumptions.
  • A later hidden-segment simulator should be a new version instead of silently replacing the baseline.

Task steps recorded:

  1. inspected maintained code, configuration, documentation, and regional workbooks;
  2. researched official economic indicators and statistical or advertising definitions;
  3. relocated the implementation and exposed hard-coded behavior constants;
  4. added economically informed behavior transformations and regional configurations;
  5. generated and validated regional datasets;
  6. documented formulas, examples, evidence, confidence, and limitations;
  7. updated navigation, project instructions, and verification commands.

Completion status: Completed. Nine Python tests passed; all four scenario outputs reported zero validation errors; repeated runs produced byte-identical Comma-Separated Values files; the baseline SQLite row counts matched the Comma-Separated Values row counts in the automated storage test; and the VitePress production build succeeded without broken links.

Main affected areas: ZheyuanWu/simulations/baseline/, ZheyuanWu/generated/, ZheyuanWu/docs/dataset-creation/, ZheyuanWu/docs/DEFINITIONS.md, ZheyuanWu/docs/PROMPTS.md, README.md, and AGENTS.md.

Earlier task summaries

The following entries reconstruct earlier goals from the current conversation. They were not recorded at their original completion time.

2026-07-29 — Definitions and documentation site

Create DEFINITIONS.md for high-school readers; move repository analysis under ZheyuanWu/docs/; separate model proposals into CONJECTURE.md; make the documentation directory a VitePress site; add status labels, navigation, cross-platform launchers, definition links, and collapsible source sections.

Recording status: Reconstructed later

2026-07-29 — Documentation launcher repair

Repair the VitePress development command; make both launchers derive their own path; default to development mode; support npm and pnpm; detect a missing or outdated Node.js environment; and provide actionable clean-system diagnostics.

Recording status: Reconstructed later

Keep facts, inferences, and recommendations distinct.