> ## Documentation Index
> Fetch the complete documentation index at: https://docs.octavehq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Legacy Playbooks (deprecated)

> Legacy Playbooks have been superseded by Motions, Motion Playbooks, and Motion ICPs. This page is kept for reference only.

<Warning>
  **Legacy Playbooks are deprecated.** New workspaces and agents should use [Motions](/concepts/motions) instead.

  The legacy Playbook entity has been replaced by a structured hierarchy: **[Motion](/concepts/motions) → [Motion Playbook](/concepts/motions#motion-playbooks) → [Motion ICP](/concepts/motions#motion-icps)**. The new model separates the strategy (Motion), the narrative angle (Motion Playbook), and the persona×segment targeting (Motion ICP) into independently editable, learnable units. It is what every agent reads at runtime.
</Warning>

## What were legacy Playbooks?

A Playbook was a flat object that combined an [Offering](/concepts/offerings), [Personas](/concepts/personas), a [Segment](/concepts/segments), [Use Cases](/concepts/use-cases), [References](/concepts/references), [Proof Points](/concepts/proof-points), [Competitors](/concepts/competitors), [Alternatives](/concepts/alternatives), [Buying Triggers](/concepts/buying-triggers), and per-persona Value Props into a single executable sales strategy. Agents read from one or more Playbooks at runtime to generate personalized output.

## Why we replaced them

Legacy Playbooks worked for a single audience but didn't model the reality that the same offering needs multiple narrative angles (default, thematic, milestone, account-specific, competitive) — and that each angle reaches multiple persona×segment cells, each with its own narrative, learnings, and recommended evidence.

[Motions](/concepts/motions) make those layers explicit:

| Legacy concept                    | New equivalent                                                          |
| --------------------------------- | ----------------------------------------------------------------------- |
| Playbook (1 flat object)          | Motion + Motion Playbook(s) + Motion ICP(s)                             |
| Per-persona value props           | Motion ICP narrative + learnings                                        |
| Playbook → segment + personas     | Motion Playbook scope (AUTO or MANUAL)                                  |
| Playbook → competitors / triggers | Motion Playbook narrative type: `COMPETITIVE` / `MILESTONE` / `ACCOUNT` |
| Playbook collateral               | Motion Playbook anchor overrides                                        |

## Migration

Existing Playbooks remain accessible via the legacy `/api/v2/playbook/*` endpoints, but new development should target the Motion APIs. See [Motions](/concepts/motions) for the full data model and endpoints.

## Legacy API (for reference)

* `GET /api/v2/playbook/list`
* `GET /api/v2/playbook/get`
* `POST /api/v2/playbook/create`
* `POST /api/v2/playbook/update`
* `DELETE /api/v2/playbook/delete`