Public: anyone can read this; nobody can change it.
/goal /ultracode-workflows [SPINE-4] re-establish a known-good baseline — germinate a fresh long-lived reference/staging platform from post-SPINE-2/3 main #27
Closed without the crew
SPINE-4 delivered: long-lived reference/staging platform staging.local germinated on the vxrail from the current committed seed (post-0.7.6 + full tooling era) and LEFT RUNNING as the standing baseline. Full acceptance gate 12/12 + GATE PASS (context k3d-staging: whiteboard 10/10 Kustomizations + 12 ClusterPolicies, single restart-idempotent webhook on the 0.7.6 verify path, redirect matrix, hostNetwork mirror + crictl pull, agents 0.7.6/mcp 0.26.0, tier-1 mitosis fork with true parent lineage). Standing roles: (a) soak/long-run stability target — the one axis ephemeral CI daughters cannot cover; (b) the PolicyReport bake window plat/gitops#14's Enforce checklist needs; (c) demo/reference. Ops: checkout + logs at vxrail:~/staging-mitosis, fork key backup in ~/.mitosis-keys. Closing.
Track/Wave:
SPINE-4· Wave M5 · Size M Repos:mitosis,mcp,agents,gitops,_app-templateDepends on: SPINE-2, SPINE-3, DOM-1a, SEC-1, HYB-1Why
Nothing runs the current stack today (gc.local torn down; prod on old versions). This re-validates hardened main end-to-end and becomes the reference/staging platform Horizon 2 validates against. Immediate pre-condition to the client VPS deploy.
Scope
Germinate a fresh long-lived platform from hardened main; exercise the full secrets flow (prod + dev PLAT_DEV scoping), the credential boundary, public TLS, and a real agent-built app with DB+bucket end-to-end; KEEP IT RUNNING as staging.
Acceptance
Passes CI-1 AND a human-reviewed report confirms secret scoping, the non-admin boundary (#16 red-team), and browser-trusted TLS on a client-shaped app; the platform is kept alive as staging.
Notes
→ MVP milestone: after this, germinate main onto the client's VPS. That is the SOW deliverable.
--- Part of the First Client Deploy → Governance roadmap. The owning agent may recurse into its own subagent team (ultracode workflow) if the task warrants. Honor the seam-serialization: land on a shared seam by rebase, and don't start a seam position until the prior one has merged.