Overview
At a glance for this environment.
Server
Backups
Activity
Admin actions across the Command Center — most recent first.
Companies
Only devs (Command Center) and each company's admin appear here. A company's other employees are managed inside its own Employee tab (the roster) — they don't show up in the Command Center.
Releases
Dev is the live working site — every change auto-appears on dev.kerfestimatebuilder.com. Production is promoted from Claude under fixed rules; it is not released from here.
Dev · dev.kerfestimatebuilder.com
version —
health: unknown
Live — auto-updates on every save
Edits are backed up to git and published to dev automatically (~45s). No button needed.
Production · kerfestimatebuilder.com
version —
Promoted from Claude, one structure-only release at a time. The version increases by one with each promote.
Promote rules (enforced): a promote ships structure only — app code + additive schema migrations. It never adds, removes, or rewrites client data, and no demo or test data crosses to production. Migrations are forward-only and additive — no
drop / truncate / delete — and every database is left intact. The version increases by one with each promote.
Deploy log
Audit trail
Every admin action in this environment — who did what, and when.
Write path
Which projects save marks as rows (Phase D) instead of rewriting the whole document. Faster once several people are on one job — and slower on a quiet one, so enrol the busy jobs.
Enrolling changes how every user on that project saves. While an enrolled project has a mark write still settling, an older browser tab is briefly refused when it tries to save marks — it catches up within seconds. Un-enrolling is always safe and takes effect on the next save, with no reload.
KERF Collective — Command Center · The studio [behind] the studio.