Skip to main content
The playbook is a markdown file that tells the agent what to try and why. It is the primary lever for domain expertise: when you know something about your hardware or workload that the agent doesn’t, you add a heuristic to the playbook. The default playbook lives at src/aevyra_forge/playbook.md and is bundled into the package so it works after pip install.

Structure

A playbook is a markdown file with ## section headings. Sections Forge always includes in the agent prompt: Hardware-specific sections are included only for the matching vendor:

YAML front-matter

version is used by Reflex (the prompt optimizer) to track playbook revisions.

Custom playbook

Pass --playbook path/to/playbook.md to override the built-in:

Validate a playbook

Programmatic access

format_for_agent filters to only the sections relevant for the current hardware and layer, keeping the agent prompt focused.

Reflex integration

In v0.2+, Reflex will read the experiment history and propose playbook edits — turning empirical findings (e.g. “prefix caching always helped on this hardware”) into permanent heuristics. For now, edits are manual.