Deployment Roadmap

Deployment Roadmap

Artifact dossier

Deployment Roadmap

v1.0.0

Copy permalinkPermalink copied

Artifact details

Permalink/clients/gerimedica/a/gerimedica-deployment-roadmap

Current snapshot/clients/gerimedica/a/gerimedica-deployment-roadmap/v/1.0.0

Artifact keygerimedica-deployment-roadmap

Version1.0.0

Published2026-03-24

Version history1 snapshot

• 1.0.02026-03-24

Rollout order for the Gerimedica C2F control plane, project runtime, migration, and launch sequence.

This section explains what gets built and deployed first, what follows after that, and which later enterprise controls depend on the initial project-runtime model.

Main Rollout Story

• Open the narrated deployment sequence

Provider Appendices

The roadmap is provider-agnostic at the sequence level. These appendix views show how the same runtime contract maps onto concrete provider primitives.

• Open the Scaleway project runtime view
• Open the Nebius project runtime view
• Open the spend-control view

Sequence Summary

1. Stand up the shared management cluster and project-runtime registry.
2. Provision one provider project and one dedicated cluster for each C2F project.
3. Bootstrap the minimal project runtime: API, relational stores, vector search, secrets, and ingress.
4. Lift the current authoritative workbench artifacts into the new runtime.
5. Rebuild derived search and index state inside that project cluster.
6. Launch the workbench through the portal gateway.
7. Add spend control, suspend/destroy, audit visibility, and other enterprise controls on top of the same runtime contract.