WEBVTT

00:00:00.250 --> 00:00:06.051
Open RevEngine, Rings campaigns. A proposal captures scope and a workload-matched canary

00:00:06.051 --> 00:00:11.918
baseline. A separate Owner or Admin review authorizes the exact stored manifest. Read the

00:00:11.918 --> 00:00:17.719
page carefully: campaign execution is not connected and no patch deployment is available

00:00:17.719 --> 00:00:23.652
through Rings. STOP cancels queued Rings installs, a command already picked up may finish,

00:00:23.652 --> 00:00:26.025
and STOP does not uninstall updates.

00:00:27.192 --> 00:00:32.957
The page requires current telemetry, recent canary heartbeats, build and workload tags,

00:00:32.957 --> 00:00:38.721
pending patches on all targets, and a continuous twenty-four-hour baseline. The offline

00:00:38.721 --> 00:00:44.088
training inventory cannot satisfy these prerequisites. We leave the proposal form

00:00:44.088 --> 00:00:47.467
unchanged and do not claim a campaign was accepted.

00:00:48.644 --> 00:00:54.263
Open Ledger to inspect the receipt list and chain status. Hash-linked receipts cover

00:00:54.263 --> 00:01:00.082
selected RevEngine workflows; full action coverage and backup-restore acceptance remain

00:01:00.082 --> 00:01:06.036
incomplete. A recorded authorization is not a dispatched job, and a chain status is not a

00:01:06.036 --> 00:01:08.644
successful endpoint patch installation.
