// local browser tool
Runbook Composer controls
Runs in this tab. Nothing you type is uploaded.Runbook Composer turns a risky task into a clearer local checklist: prerequisites, dry-run checks, execution steps, rollback notes, and verification.
What it does
- Structures a task into an operational checklist.
- Separates prerequisites, dry-run checks, execution, rollback, and verification.
- Uses the shell context to choose the dry-run guidance and records the selected risk level in the artifact.
- Keeps the task text local to the browser.
Use cases
- Prepare an API-token rotation.
- Draft a small deployment checklist.
- Turn an infrastructure change into ordered steps.
- Capture rollback and verification notes before making a change.
Local privacy boundary
The task text is processed in the browser. It is not uploaded to graysond.xyz, sent to an AI provider, stored in a database, or included in analytics.
The AI clause is the deliberate one. The task text becomes the heading and nothing else — the template never reads it, branches on it, or needs to understand it — so there is genuinely nothing to send anywhere. A model could write specific-looking steps instead, but it would be writing them for an environment it cannot see, and a plausible wrong command in a rollback section is worse than a blank line that makes you write your own.
Risk framing
The shell selector changes the dry-run guidance for PowerShell, Bash, or an unspecified shell. The selected risk level is recorded at the top of the artifact for the person reviewing it; it does not change the checklist content.
Limits
Runbook Composer drafts structure. It does not approve production changes, validate commands, replace peer review, or know the private state of your environment.
Related
Use CIDR Inspector for network ranges, Structure ZIP Builder for reusable scaffolds, Practical Business Systems for workflow context, or Technical Operations for operational writing patterns.