Reading the native organ court.
RELEASE CENTER · VERIFY → PREFLIGHT → DRY-RUN → DEPLOY → WITNESS
Deploy from one honest gate.
Local verification can run now. Cloudflare dry-run and deployment remain unavailable until the exact operator, environment, credentials, bindings and witness conditions shown below are satisfied.
OPERATOR AUTHORITY
Authenticate once for this browser session
Use network-os-local-data/OPERATOR_BOOTSTRAP_TOKEN.txt. The token stays in session storage and is sent only to this local HQ origin.
Reading the separate kernel bridge.
Reading worker, migration and config state.
No deployment is inferred from configuration files.
01
Verify restored HQ
Runs the allowlisted restoration integration suite. It does not deploy.
02
Inspect Cloudflare preflight
Reads worker source, migrations, Wrangler configs and current gate flags.
03
Dry-run
Compiles the Worker without publishing. Requires operator auth and BENT_AGENT_ALLOW_CF_DRY_RUN=1.
04
Deploy
Requires authenticated Cloudflare credentials, HQ_ONLINE, backend switch, deploy flag, then live route/write-read/rollback witnesses.
DEPLOYMENT REQUIREMENTS
The button tells you exactly what is missing.
DAISY_LINK_HQ_BACKEND_SWITCH=1BENT_AGENT_ALLOW_CF_DEPLOY=1- Cloudflare authentication available to Wrangler
- D1/KV/R2 IDs and migrations where the selected lanes require them
- Route smoke, data write/read and rollback witnesses after publishing
Action receipt
No release action has run.
This center can verify, preflight, dry-run and invoke the real gated deployment command. A returned URL alone is not a commercial-release witness.