ReNunney/docs/MIGRATION.md

Migration

Goal

Move the current cost-of-substitution implementation into renunney in staged, low-risk steps.

Current State

Operational code still lives in:

• ../../collaborations/to_ptbc/evc/cost_of_substitution

renunney currently acts as:

• a clean git repository,
• a run-control wrapper,
• a stable place for deployment and orchestration commands,
• the eventual destination for migrated code.

Recommended Migration Order

1. Orchestration control plane has been migrated locally:
   • src/renunney/orchestration.py
   • scripts/run_orchestration.py
2. Paper-scale Figure 1 submission configs have been copied locally into config/.
3. Track 1 runner and API boundary have been migrated locally:
   • scripts/run_track1.py
   • src/renunney/track1_api.py
4. Track 1 analysis boundary has been migrated locally:
   • src/renunney/track1_analysis.py
5. Track 1 threshold/search boundary has been migrated locally:
   • src/renunney/track1_threshold.py
6. Keep the Track 1 simulation backend in the legacy path until real multi-host runs are stable.
7. Migrate the Track 1 simulation core after the runner path is stable:
   • python/track1_reference.py
   • python/track1_threshold.py
   • python/track1_analysis.py
8. Migrate report, dataset, fit, and orchestration-adjacent Track 1 modules after the kernel boundary is stable:
   • python/track1_report.py
   • python/track1_dataset.py
   • python/track1_fit.py
   • python/track1_extinction.py
9. Migrate docs and example configs last, after path references are updated.

Constraint

Do not break the ability to run current Figure 1 jobs while migrating code.