Technically eligible one day, but the blockers are structural: hosted WCF or SOAP contracts that cannot run two versions at once, or heavy legacy coupling. Sequence the modernisation work first. Legacy web front end: session state and framework age make mixed-version fleets risky until state is externalised.

• Consumes WCF contract packages: never take a breaking client bump mid-feature, and treat obsolete warnings as migration debt
• Feature flags come from phenix-feature-service (WCF-only): flag reads themselves are a legacy dependency to watch

1. Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
2. Raise automated test coverage first: ZDD trades the end-of-sprint manual gate for continuous automated confidence, so the tests are the entry ticket.
3. Make every change dual-version safe: backwards-compatible APIs (new major version for breaking wire changes), expand and contract for any schema change, and consumers tolerant of unknown fields.
4. Audit serialized data: anything in Redis, queues or shared caches must deserialize cleanly across adjacent versions.
5. Externalise any remaining session state so users can move between nodes mid-session without disruption.
6. Wrap behaviour changes in feature flags so code deploys dark and release becomes a business decision, not a deployment event.
7. Route deployments through the Workflow Engine's automated drain, deploy, health-check, return cycle (the path proven by the first automated production run in mid-2026).
8. Verify with area-scoped regression rather than the whole-platform cycle, and watch error rates after rollout with automated rollback on alert.

No SQL Server dependency is recorded for this repo. Nothing to migrate.

Appropriate, but the .NET Framework runtime has to go first; container work rides along with the replatform rather than preceding it.

• .NET Framework only runs on Windows; practical (Linux) containers need modern .NET

1. Replatform to modern .NET first (see the recommended actions). Containerising then becomes routine.
2. Add a Dockerfile and make the app read all configuration from environment variables and the secrets manager, never from machine-local files.
3. Log to stdout and expose a health check endpoint so ECS can supervise it.
4. Adopt the shared ci.yml pipeline template with the container parameters (awsRegion, containerAfterBuild, ecsTerraformRepo), which is exactly how the estate's existing AWS services deploy.
5. Define the service in the Terraform repo, deploy to a non-production environment, then shift traffic and disarm the deployment-group release pipeline.