Settings
A client build is the same code plus a small config layer. This is the config this deploy is running.
Set up your assistant, manage connections and review its rules.
Account details
Before anything sends on its own
The public testbed runs demo-mode (fixtures). A client build points at a deployed backend and pastes an operator JWT to drive the real endpoints. The JWT is held in sessionStorage only, never in the repo, never in localStorage.
A new tenant is provisioned on the CLI, never from a fixture-first browser page: POST /tenants returns one-time plaintext secrets (admin password, api key) that a static demo console must never render.
python -m cs_os.provisioning --slug <tenant> POST /tenants (operator ADMIN) -> principals.admin_password, api_key (one-time, this response only)
The provision_tenant endpoint stays in the console endpoint map (documented_only) so the contract test still covers it; no wizard renders one-time secrets.
Edit two files, drop in a logo, redeploy. Nothing in the component source changes.
assets/client.config.js name, tagline, dataBase, posture assets/client.css --client-accent --client-accent-ink --client-gradient
The structural design system (spacing, lines, status) stays shared. Autonomy level and the L3 whitelist are set in the merchant's cs/ config and gated by calibration, not here.