Protuno Workspace

Run A Playbook And Read The Report

A playbook is a fixed sequence written down before it runs. How to switch one on, run it, and read what came back.

Protuno Editorial Team·3 min read

A playbook is one job written out step by step before it runs. Not a model deciding at runtime what looks reasonable: a fixed sequence you can read first, that does the same thing every Tuesday.

The seventeen playbooks, and where to find them

All seventeen live under Super Agents, in one list, with the category, the number of steps and whether it can write shown on every card.

The Every Playbook grid on the Super Agents screen, showing playbook cards with their category, step count and whether they can write
Scroll past the six agent cards and Every Playbook lists all seventeen, each with its category, its step count and whether it can write.

The six named agents above the list are the layer that will eventually group these playbooks and explain what they found. That layer has not shipped. The playbooks themselves have.

Eleven of the seventeen carry a BETA tag on their card. They run, and they are the ones still being shaped. Six do not: WP Security Audit, SSL And Domain Expiry Monitor, Cron Health Checker, SMTP Deliverability Check, Broken Image Finder and Spam Comment Deleter.

What a playbook page shows you

A playbook page shows every step in order, and each step opens to reveal the instructions it runs and what it hands to the next step. A playbook that needs a restore point has a backup step of its own, and it shows up as a step.

A playbook detail page showing its steps in order and the sites it is switched on for
Steps on the left, sites on the right. Every playbook needs the plugin, so any site that is not connected is switched off here, with the reason on the row.

Two things are worth knowing. Each site gets its own copy of the steps, so editing one site’s playbook does not touch another’s. And switching a site off keeps that copy rather than destroying it, so switching back on returns what was there.

Switching on is not running, with two exceptions

For fifteen of the seventeen, the toggle attaches the playbook to a site and Run does it now. Those are separate on purpose, because attaching a playbook is a decision you make once and running it is a thing you do.

The two free weekly playbooks behave differently. Switching one on arms the weekly routine and starts the first run immediately, and the screen says so as you press it. See Routines for why.

Reading the run report

Every run lands in Run history. A finished run carries one of three verdicts: Passed, Needs attention, or Failed. Cancelled is a fourth terminal state, for a run that was stopped rather than judged. While a run is still going you will also see Running, Finishing report, Waiting for a slot and Waiting on you.

A playbook started on four sites is four runs, each with its own report.

A Protuno run report showing a critical action plan, the steps that ran, and a technical detail section
A run that could not do its job, saying so. The report refuses to produce a grade rather than inventing one.

Each report has a simple and a technical view, and exports to PDF for sending on.

The example above is worth dwelling on. Every step ran, but the site never returned WordPress data, so the run reports zero findings and explicitly declines to assign a posture grade. An unreadable site is not graded as healthy. That is the behaviour to expect throughout: uncertain is never reported as fine.

Where to go next

Comments