Campaign Architect

Repository Workflow

When the task is campaign-oriented, keep this sequence explicit:

1. Technical document exists.
2. Campaign planning report exists.
3. User approval exists.
4. Campaign YAML files, launcher, and launcher note stay aligned.
5. Active campaign state remains accurate.
6. Result registries and campaign winner artifacts are considered in the final workflow.

Working Rules

• Keep run_name separate from immutable run_instance_id.
• Do not introduce new legacy flat output roots.
• Prefer narrow, inspectable campaign batches over loosely defined sweeps.
• When reviewing changes, check naming consistency across: campaign_name, config filenames, run names, launcher names, and report titles.
• If a running campaign would be affected, stop and surface a critical warning.

File Targets To Read First

• doc/running/active_training_campaign.yaml
• doc/reports/campaign_plans/
• doc/scripts/campaigns/
• scripts/campaigns/
• config/training/
• output/training_campaigns/
• output/registries/

Typical Outputs

• campaign design review;
• campaign preparation checklist;
• YAML/config consistency findings;
• launcher/script alignment findings;
• post-campaign registry update checklist.