Power-Up Playbook

A curated knowledge index that scopes what a capability retrieves. Abbreviated PUP; rows are PUP-N.

A PUP is deliberately not a workflow and not a prompt — it carries no steps and no template body to execute. It carries a curated list of members (rows, pages, saved queries, whole Dotabases), and invoking it hard-filters retrieval to that member set. The point is precision: instead of searching everything the user owns, an agent searches exactly the slice a human decided was relevant.

A PUP can optionally widen its scope by graph expansion from its members, but that is off by default.

Usage examples

• "Curated knowledge indexes that scope what a capability retrieves." (the Playbooks Dotabase description)
• "Invoking @playbook hard-filters retrieval to the resolved member set; pin the composer chip if you want it to survive the turn."
• "A PUP cannot reference another PUP — no PUP-of-PUPs."

Source

SPEC-176 (DS_Power-Up-Playbooks) § 1.1–1.3; entity type pup / prefix PUP at packages/knowledge-graph/src/entity-types.ts; the live Dotabase slug playbooks.