Updates the implementation plan to match the cluster-split decision
landed in platform/orca-platform PR #6 (commit 6be727d4):
§1.1 Repo strategy
- Adds three cluster repos to the inventory:
platform/breakpilot-edge (Identity + Infra, vm-edge)
platform/breakpilot-control (Control, vm-control)
platform/breakpilot-app (App, vm-app-prod + vm-app-stage)
- Reframes platform/orca-platform as the staging area where the
cluster manifests live design-only until the legal entity unlocks
SysEleven / Hetzner business contracts at M1.2.
§1.8 Environments
- Rewrites the three-clusters-by-env model into three-clusters-by-plane.
- Stage and prod live in the same breakpilot-app cluster on different
VMs (vm-app-stage and vm-app-prod); identity and control are NOT
duplicated for stage.
M0.1 / M0.3 / M1.1 / M1.2 / M1.3
- M0.1 note: the three cluster repos are NOT created at M0.1; they
split out of orca-platform at M1.2.
- M0.3 / M1.3 repo pointers re-targeted to breakpilot-edge.
- M1.1 updated to describe the cluster-split layout that landed in
PR #6: clusters/breakpilot-{edge,control,app}/services/ + per-cluster
node whitelist in scripts/validate.sh.
- M1.2 rewritten as "Provision VMs + split cluster repos": 4 VMs across
3 clusters, KC repurposed from CERTifAI, legal-entity gate added,
sized up to L.
M2.1 / M2.2 / M3.1 / M3.2
- Fix vm-identity / vm-secrets typos to vm-edge.
- M2.1 calls out the KC repurpose explicitly + the JVM-pin escape
hatch (split KC to its own VM if heap fight shows up).
- M3.2 re-pointed to breakpilot-control.
M8.x / M9.x / M18.x
- ERPNext + Frappe HD repo pointers re-targeted to breakpilot-control.
- M18.1 ACME work re-pointed to breakpilot-edge.
- "data plane" → "app plane" everywhere; data-plane phrasing kept
only where it refers to per-tenant data isolation as a concept.
PR-10 narrative updated: VM provisioning is a cluster split, gated on
legal entity.
No milestone IDs change; effort estimates change only for M1.2 (M→L)
to reflect the added repo-split + KC realm migration work.
Sharang Parnerkar