The step that now blocks acceptance at the top (AEA / JF / Management Science Data Editors
re-run your code and check every number). Full manifest + validation checklist:shared-resources/empirical-methods/replication-package.md.
resources/official-source-map.md(code at submission vs. acceptance? Data Editor? AsCollected page? restricted-data rule?
hosting?). Match it exactly.
(clean → construct → estimate → robustness → tables), pinned environment, README/roadmap,
data (or pseudo/synthetic data for restricted access + access instructions), the
script→exhibit output map, and the disclosure statement.
number reproduced (body + appendix); seeded/deterministic; restricted-data plan; output
map complete; venue policy satisfied.
regenerate the affected outputs.
【Venue policy】(code timing, Data Editor, restricted-data rule, hosting)
【Manifest】master · steps · env · README · data · output-map · disclosure — status each
【Validation】end-to-end ✓/✗ · all numbers reproduced ✓/✗ · seeded ✓/✗ · restricted-data plan ✓/✗
【Blocking gaps】what would fail a Data-Editor check, ranked
【Ready?】GO / NOT-YET — deciding items
the script doesn't reproduce; committing confidential data; leaving assembly to post-accept crunch.