editing per portfolio feature flag

This commit is contained in:
Khalim Conn-Kowlessar 2026-05-14 07:39:18 +00:00
parent 02df38e207
commit f8bd13cb63

View file

@ -74,7 +74,7 @@ Forced cut-over, driven by the 30 May deadline. There is no strangler period bec
- On 30 May the Old EPC API dies; `model_engine` ceases to function for any new modelling run.
- Some downtime is expected and accepted. Clients are aware.
- Modelling resumes when the new pipeline is ready end-to-end. There is no per-portfolio feature flag, no parallel pipelines, no traffic split — the new pipeline is the only pipeline.
- Modelling resumes when the new pipeline is ready end-to-end. Remains to be decided if we have a per-portfolio flag, purely for the front end to reference old tables where necessary. No parallel pipelines, no traffic split — the new pipeline is the only pipeline.
- **Calico** and **Hyde** are the first live clients onto the new pipeline in June.
- `model_engine`, `SearchEpc`, the legacy `Property`, and surrounding modules in `backend/` are deleted once the new pipeline is serving all traffic.
@ -82,7 +82,7 @@ Forced cut-over, driven by the 30 May deadline. There is no strangler period bec
- No strangler — there is nothing to strangle once the Old EPC API dies on 30 May.
- No parallel-shadow run — would double compute and require diff tooling we don't have, while the old engine is already known to return bad data so diffs would be noise.
- No per-portfolio feature flag — the cut-over is all-or-nothing.
- TBC per-portfolio feature flag. Without this, the cut-over is all-or-nothing. All old portfolios are broken.
---