[[Knowledge]] about *how* to do something — sequences of actions, workflows, methods, and processes. Also called **know-how**. ^definition Examples: - "How to deploy to production" - "The incident response process" - "Steps to onboard a new client" ^examples ## In [[Knowledge base design]] Procedural knowledge is inherently sequential and harder to atomize. It fits best as runbooks, checklists, or step-by-step documents. Forcing procedural knowledge into [[Node|graph nodes]] (one node per step) loses the sequential context that makes the procedure understandable — an agent reading step 3 in isolation won't know why it follows step 2. ^kb-implications