Environments and pipeline
Three environments on branches, feat/*→dev→test→master, auto-backport test→dev, Release-triggered prod
Phase
Phase 1
Size
L
Waits on
1
Releases
6
Waits on
Releases
- E3 Map system
- F4 Startup-pull bootstrapper
- W4 Admin panel
- W6 Health monitor v2
- X1 Blue/green cutover
- safe iteration on everything
Stories
Not designed yet.
Stories and acceptance criteria are written one Feature at a time. Nothing is missing – this one has not had its pass.
Decisions of record
- Environments and deployment
Three environments, each tied to a branch: Production -> master, Test -> test, Dev -> dev (default branch).
- Environments and deployment
Test and Dev also need a build server, environment-independent, so building can happen away from testers or with testers involved.
- Environments and deployment
Flow: work in feat/* or fix/* -> PR to dev -> merge rebuilds Dev. PR to test rebuilds Test. Anything merged to test that is not in dev is auto-backported to dev so a hotfix does not cost parity.
- Environments and deployment
Merging to master deploys nothing. It marks production-ready. A GitHub Release against master triggers the Production deploy, and deploying to prod is possible at any time via the no-downtime cutover.
History
- 3 Sept Not started – Seeded from the delivery plan, 2026-09-03.