---
type: atlas-artifact
artifact_type: runbook
project: "{{project}}"
status: draft
owner: "{{owner}}"
created: {{date}}
updated: {{date}}
source: "{{source}}"
reviewer: "{{reviewer|TBD}}"
tags: [atlas, artifact, runbook]
safety_tier: "read-only | low-risk-write | medium-risk-ops | high-risk-destructive"
---
# Runbook: {{title}}

Parent project: [[{{project}}]]
Source: {{source}}
Last tested: {{last_tested|YYYY-MM-DD or never}}

## Purpose

When and why to use this runbook.

## Preconditions and credentials required

- Required access/tools, without secrets.
- Confirm environment: ...

## Safety tier / approval requirement

- Tier: read-only | low-risk write | medium-risk ops | high-risk/destructive.
- Approval needed before: ...

## Agent blast-radius checklist

Complete this before running an agent workflow, specialist task, cron job, webhook, or gateway-triggered action that can change state.

- [ ] Filesystem scope: exact allowed paths/repos/vaults are named; out-of-scope paths are explicitly off-limits.
- [ ] Network egress: allowed external services, APIs, domains, channels, or repositories are named; uploads/exfiltration are blocked unless explicitly approved.
- [ ] Credential exposure: required credentials are referenced by source/location only; secret values must not be printed, copied into notes, committed, or sent to third parties.
- [ ] Destructive command approval mode: risky commands require `approvals.mode: manual` or `smart`; `--yolo` / approval-off is limited to an intentional sandbox and never assumed for gateway/profile automation.
- [ ] Rollback/checkpoint status: filesystem checkpoint, git branch/worktree, backup, snapshot, or explicit recovery plan exists before mutation.
- [ ] Human approval gate: Tier 2/3 actions name the exact target, expected effect, rollback/stop condition, and approver before execution.

## Step-by-step procedure

1. Do the first action.
   ```bash
   exact command
   ```
   Expected: ...
2. Do the next action.

## Verification

- [ ] Check: ...
- [ ] Command: `...` -> expected ...

## Rollback/recovery

- If X fails, do Y.

## Escalation path

- Contact/person/profile/channel: ...

## Next action

- Owner: ...
- Action: ...

## Runbook-specific review checklist

- [ ] Commands are exact and safe for the stated environment.
- [ ] Agent blast-radius checklist is filled out for any state-changing agent workflow.
- [ ] Credentials are referenced but not exposed.
- [ ] Verification and rollback/recovery are actionable.
- [ ] Last tested date is present.

## Universal reviewer checklist

Before accepting this artifact, verify:

- [ ] Clear owner, status, date, source, and next action.
- [ ] Saved in the correct durable destination and named using the convention.
- [ ] Links back to the relevant project note and source task/issue/PR/session/incident.
- [ ] Claims are backed by evidence links, command output, or labeled assumptions.
- [ ] Risks, rollback, recovery, or revisit triggers are documented where relevant.
- [ ] No secrets, tokens, raw PII, private keys, or unredacted credentials are included.
- [ ] A new specialist can understand the artifact without rereading the whole chat.
