Read Rings authorization limits and Ledger receipts Open RevEngine, Rings campaigns. A proposal captures scope and a workload-matched canary baseline. A separate Owner or Admin review authorizes the exact stored manifest. Read the page carefully: campaign execution is not connected and no patch deployment is available through Rings. STOP cancels queued Rings installs, a command already picked up may finish, and STOP does not uninstall updates. The page requires current telemetry, recent canary heartbeats, build and workload tags, pending patches on all targets, and a continuous twenty-four-hour baseline. The offline training inventory cannot satisfy these prerequisites. We leave the proposal form unchanged and do not claim a campaign was accepted. Open Ledger to inspect the receipt list and chain status. Hash-linked receipts cover selected RevEngine workflows; full action coverage and backup-restore acceptance remain incomplete. A recorded authorization is not a dispatched job, and a chain status is not a successful endpoint patch installation.