Skip to content

Playbook Entity

The playbook is the strategy entity in Cortiq.

A playbook typically defines:

  • market conditions the setup requires
  • entry conditions and filters
  • invalidation logic
  • stop and target guidance
  • trade-management expectations
  • priority relative to other linked playbooks

This is the strategy hint.

Use it to tell Cortiq whether the playbook is fundamentally a trend-following, mean-reversion, breakout, range, or similar style setup.

This is the main analysis timeframe.

It tells the AI where the broader market structure for the setup should be judged.

This is the trigger timeframe.

It tells the AI where the actual execution signal should appear after the setup becomes valid.

This section explains what the market must look like before the setup is considered real.

Use it for structure, alignment, volatility character, trend state, or regime conditions.

This section explains what must happen before the AI is allowed to act.

Use it for confirmation, timing, candle behavior, or specific trigger logic.

This section explains how the trade should be boxed.

Use it for stop placement, take-profit logic, reward-to-risk thresholds, or sizing boundaries.

This section explains what should happen after entry.

Use it for trailing, partials, break-even logic, or what should happen as the trade progresses.

This section explains when the setup should be abandoned.

Use it to tell the AI exactly what makes the playbook no longer trustworthy.

These fields help the user express where the playbook belongs.

They are useful when a setup works better on certain markets or during certain trading windows.

  • Keep setup conditions broader than entry conditions.
  • Keep entry conditions more precise than setup conditions.
  • Keep risk and management rules separate.
  • Always define invalidation if the setup can lose its logic.
  • Use preferred symbols and sessions as fit guidance, not as a substitute for the actual setup logic.

Playbooks keep the AI inside a structured trading framework.

That means Cortiq is not just asking an AI model to improvise trades from raw chart data.

Good playbooks are:

  • narrow enough to be clear
  • specific enough to be testable in journals and reviews
  • explicit about when not to trade
  • explicit about what to do after entry

A playbook should not be:

  • a catch-all idea list
  • a macro-news summary
  • a one-off active thesis for one current setup

Those belong in other entities such as trade ideas or sentiment reports.

Playbooks work most effectively with: