`/knowledge/playbooks/`¶

Operational how-to guides. The "how do I do X?" layer of the wiki.

What goes here¶

Step-by-step playbooks that a reader (Rick, an agent, a future team member) can follow to accomplish a specific operational task. Examples:

"How to rotate a credential in 1Password"
"How to onboard a new agent from Drafted to Active"
"How to launch a Mission from inbox capture to Monday.com Epic"
"How to debug a failing launchd job"
"How to set up a new Make.com scenario"
"How to run a council review on a decision"

Relationship to `/system/playbooks/`¶

There is a deliberate distinction:

/system/playbooks/ — governance-level operational playbooks. Approved, versioned, CEO-accountable. These enforce operating standards and have a version number, owner, and audit trail. Example: SOP-EXEC-strategy-request-intake-v1.0.md.
/knowledge/playbooks/ — reference how-to guides. Not governance. Practical step-by-step instructions that describe HOW something is done. Can be updated freely as tools change. Example: how-to-rotate-a-credential-in-1password.md.

Rule of thumb: if a failure to follow it is an SOP breach, it belongs in /system/playbooks/. If it's "here's the clickstream to accomplish X," it belongs here.

A /system/playbooks/ SOP can (and should) link to one or more /knowledge/playbooks/ how-to guides for its implementation details. The SOP codifies the rule; the playbook shows the clicks.

Frontmatter convention¶

---
title: "How to {action}"
type: playbook
category: {credential-mgmt | agent-onboarding | mission-lifecycle | debugging | integration-setup | other}
owner_agent: {agent_id or tbd}
related_sops: []  # paths to /system/playbooks/ or /system/sops/ that this implements
related_tools: []  # paths to /knowledge/tools/ this playbook touches
difficulty: {trivial | routine | intermediate | advanced}
estimated_time: "{5 min | 15 min | 1 hr | ...}"
last_verified: YYYY-MM-DD  # when someone last confirmed these steps still work
last_updated: YYYY-MM-DD
seeded_by: {agent_id}
tags: []
---

Page structure¶

# How to {action}

## When to use this
_What situation triggers this playbook. One paragraph._

## Prerequisites
_Access, credentials, tools, agent state, or prior knowledge required._

## Steps
_Numbered, click-by-click, reproducible. Include screenshots or terminal output where helpful._

## Verification
_How to confirm the step worked. Tests, queries, expected output._

## Troubleshooting
_Common failures and their fixes._

## Related
_Wikilinks to SOPs, tools, platforms, best practices, and other playbooks._

## Last verified
_Date + who verified. Playbooks rot — re-verify quarterly._

Dashboard¶

Live list at /dashboards/playbooks-catalog.md — grouped by category, sorted by last_verified date (oldest first, so stale playbooks surface for re-verification).

Rotting playbooks¶

Playbooks rot as tools change. Every quarter, chief.staff runs a re-verification sweep: any playbook with last_verified > 90 days old gets flagged. The playbook's owner_agent is responsible for either re-verifying the steps or marking it deprecated.

/knowledge/playbooks/¶