Playbooks

Playbooks capture how an agent should behave. They are behavioral guidance at two scopes: user-specific evidence and agent-wide rules.

User Playbooks

User playbooks are extracted from one user's interactions. They capture a correction, constraint, or successful procedure tied to its source evidence—for example, “When this user asks for a recommendation, respect the stated budget before optimizing other attributes.”

They are useful for personalization and as evidence for broader improvement, but they should not be mistaken for universal policy.

Agent Playbooks

Agent playbooks consolidate recurring user-playbook patterns into guidance for an agent version. They remove user-specific detail and express an actionable trigger and response.

Agent playbooks use a human approval gate:

User interactions
    ↓ extraction
User playbooks
    ↓ clustering and synthesis
Pending agent playbook
    ↓ human review
Approved or rejected

Only approved agent playbooks should be treated as validated agent-wide guidance.

Retrieval Behavior

Unified search can return profiles, user playbooks, and agent playbooks together. When a returned agent playbook already represents a source user playbook, Reflexio suppresses that duplicate user playbook from the result.

Use:

• User playbooks for user-specific steering and source-level debugging.
• Approved agent playbooks for reusable behavior across users.
• Pending agent playbooks for review, not production prompting.

Configuration and Optimization

Reflexio includes a default playbook extractor and aggregator. Tune extraction prompts or aggregation thresholds only after observing real traffic. Optional playbook optimization can refine content against replayable source windows while preserving the normal approval rules.

For integration patterns, see Collecting and Using Playbooks. For optimization details, see Playbook Optimization. For exact methods and schemas, see the Playbook API Reference.