Admin

Service settings and Emergency Mode. Reads on this page come from this WUI's local projection; every change is authorized at url://buildtest/ with a single-use W3Wallet presentation.

Control connection

Checking the url://buildtest/ control surface…

A coordinator that predates the control surface still serves every ordinary page; only the commands below become unavailable.

Wallet

Each command below requests a fresh single-use challenge from url://buildtest/, asks the W3Wallet browser extension to create a presentation over it, and forwards the two wire values with the command. Nothing about the credential is stored by this WUI or by your browser session.

Settings capability
buildtest.admin.settings.write
Emergency capability
buildtest.emergency.control
Audience
url://buildtest/
Extension
checking…
Last challenge
none requested yet

Service settings

This WUI has not observed a service-settings document yet. A coordinator publishing projection schema 1 never sends one; a schema-2 coordinator sends it with its next baseline.

The limit is a positive integer. Lowering it never cancels a running build and never releases a reservation: it prevents further capacity grants until the reconciled fleet plus outstanding reservations fits under the new value. Raising it wakes waiting builds immediately.

Emergency status

This WUI has not observed an emergency-state document yet.

An activation has no expiry and no timer. It ends only when an authorized operator deactivates it, and it survives a restart of both the coordinator and this WUI.

Plans

Plans are immutable. Editing one forks it, keeping the parent's body and lineage intact. A plan is retired, never deleted, and a retired plan stays readable and forkable.

Create or fork a plan

Ordered rules

Rules are evaluated in this order and the first match decides the request. The last rule must be an explicit catch-all — no operation names, caller ANY, no attributes — and no earlier rule may be one, because every rule after a catch-all would be unreachable.

Dry-run report

A dry run performs no action. Nothing is canceled and no droplet is destroyed by it.

Confirm activation

Run a dry run first; its report is what an activation is confirmed against.