Playbook Engine

The Playbook Engine is the strategist of the RiskState stack. It answers:

Is there a setup I trade?

It is a registry of pre-defined, locked setups (playbooks). A playbook fires only when three things agree at once:

1. its own conditions match the live data,
2. the Structure Engine aligns (the navigator votes ALIGN, not CONFLICT), and
3. the RiskState gate permits.

That triple-confirmation, governed is what neither a raw signal feed nor a trading bot provides.

Open the live Playbook Engine →

The viewer is free and read-only. It shows the strategy registry and what is firing now — and deliberately shows no fund positions, NAV, or money. It is the strategist layer, not a fund dashboard.

What it shows

• Strategy registry — every playbook with its thesis, side (long/short), asset, class, priority, horizon, cooldown, and its sizing and exit rules (as rules, never dollar amounts).
• Firing now — for the selected asset, which setups currently fire, each annotated with the Structure Engine's vote (ALIGN / NEUTRAL / CONFLICT) and the risk gate verdict (ALLOW / RESIZE).
• Conviction — the proposed size as a fraction of NAV (relative conviction only — never a dollar figure).

The three engines, governed

Each engine answers a different question; the product is the confluence:

A playbook proposes a candidate intent; the navigator confirms the terrain; the governor sizes and permits it. Only when all three agree does a governed intent exist.

Why a registry, not signals

Playbooks are pre-defined and locked — their conditions are fixed in advance, so each fire is measurable against a stable definition. This is what lets the stack accumulate an auditable track record (every governed decision is hashed with its forward return) rather than a stream of one-off calls.

Related

• Structure Engine — the navigator the playbooks require for confluence.
• Methodology — how the risk gate sizes and permits a candidate intent.
• Audit Log — how governed decisions are recorded and verified.