Launch

At a glance

• Production setup path uses control-plane provisioning and CI-driven deploys.
• Do not use legacy events/*.json CLI flows.

Do this

1. Configure GitHub Environment vars/secrets for development and production using:

• .github/environments/development.env.example
• .github/environments/production.env.example.

2. Push to main (or run manual dispatch) for:

• .github/workflows/control-plane-deploy.yml
• .github/workflows/docs-deploy.yml

3. Verify smoke checks pass in both workflows.
4. Create/provision events from control-plane and verify event deploy jobs in GitHub Actions.

Deployed targets

• Development:
• control plane https://dev.tripplan.ing/platform
• docs https://dev.tripplan.ing
• Production:
• control plane https://tripplan.ing/platform
• docs https://tripplan.ing

Decision points

• Need exact command surface: use Commands.
• Migrating legacy Atkins event: use Legacy Migration Reference.