docs: runbook for the first companyOS kernel deployment (SuperCleanOS) #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/superclean-runbook"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Three phases. Phase 0 is the only one safe to run today.
Phase 0 lands an
include_objectfilter insuperclean-sys2/backend/alembic/env.py. Without it, autogenerate against a production-derived database proposes a DROP for all nine kernel tables. Changes no production state and is worth doing regardless.Phase 1 creates the nine tables in SuperClean's production database. Gated on human approval.
Phase 2 has
superclean-apiimport the library and read the shared database directly rather than calling the kernel over HTTP.Collision check run against the live schema on 2026-07-27:
superclean_prod_dbholds 30 tables plusalembic_version, none intersecting the kernel's nine oralembic_version_kernel.