Control Tower
Clients, devices, packages and build activity.
Staff sign-in
Paste your individual Control Tower staff token. It stays in browser memory only until you lock or close this page.
Control Tower/data/owner.token, copy the single line, paste it below, then close the file. A friendly client key is deliberately rejected here.The Worker owner key, friendly client keys, and package signing keys never enter this page.
Measurement and rollout notes
External pilot rollout is ON HOLD pending client qualification. Input reduction is a historical physical estimate and may include failed requests. It is not proof of lower bills, extra subscription allowance, or equivalent task quality. Dollar savings are unmeasured.
Clients & devices
| Actions |
|---|
Content-free diagnostics. No prompts, source files, or provider secrets.
Technical diagnostics
Build new client packages
Builds the matching native package, verifies decryption, registers it, and issues one device-bound client key per friendly. Existing IDs are never overwritten.
Package availability is checked on this computer before building. The expiry clock starts now; enrollment and live agent qualification are separate steps.
Build history
| Cohort / build ID | Status | Created | Clients | Packages / details |
|---|
Package delivery
Send each friendly only their own encrypted archive and client guide. Send the archive password and that friendly's client key through separate secure channels. Never distribute this console, this repository, staff tokens, operator receipts, databases, source code, or signing material.
| Delivery files |
|---|
Live qualification
Independent task checks, not savings certification. Lab-bound identities must not be handed to another workstation.
Show qualification history
Activity
| Time | Action | Target | Outcome |
|---|