Skip to main content
A Playbook is a reusable recipe for getting something done — written once, then run whenever you need it. It’s how a way of working stops living in someone’s head and becomes something your business can repeat reliably. If Memory is what you know, a Playbook is how you do a specific thing — and unlike a plain document, a Playbook can actually run.

​
From one-off to repeatable

The natural path in aidax:
1

You do it once

A project gets something done — say, a weekly performance report.
2

It becomes knowledge

The steps and decisions are distilled into your workspace Memory.
3

It crystallizes into a Playbook

When the job repeats, you capture it as a Playbook — a step-by-step workflow your agents can follow.

​
Run it your way

A Playbook can be triggered:

On demand

Run it manually whenever you need it.

On a schedule

Every Monday morning, month-end — set it and forget it.

By an event

Kicked off automatically from another tool via a webhook.
This is where Playbooks become more than documentation. A scheduled Playbook is a piece of your business that runs itself — the work happens even when no one starts it.

​
Your procedures, reusable and owned

Playbooks are part of your Memory — the procedural layer — so they’re stored as portable files you own, just like the rest of what your business knows. Build a library of them and your operations get more capable without getting more complicated.

​
Next

Memory

Where Playbooks live and how they’re born.

Agents

Who runs your Playbooks.