Skip to content

Sessions

This is the entity reference for sessions. By the end you’ll know what a session contains, what it references, and how to think about it as a reusable operating template.

The session is the main operating unit in the Cortiq trading cycle — the practical bridge between strategy design and live operation. Every other entity in the trading cycle is something a session points at.

A session bundles:

  • One MT5 account.
  • One primary AI provider and integration mode.
  • One symbol — the single instrument the session trades.
  • One data package.
  • One or more playbooks (with priority).
  • Optional trade ideas.
  • Optional support layers — preparation package, instrument profile, sentiment report.
  • A time window, active days, and execution settings.

Without sessions, you’d reassemble the whole workflow manually each time. The session is what makes the trading cycle repeatable — start it, pause it, review it, improve it, duplicate it into a new template.

For runtime behavior and the session lifecycle, see Sessions. For the architectural role, see Session architecture.

Treat the session as a trading-desk template. Once it’s stable, duplicate before changing — keep the original running as a control while you experiment on the duplicate. Cohort comparison turns the two runs into evidence.

ReferenceRequired?Read more
MT5 accountyesMetaTrader 5 integration
AI provider + modeyesAI providers
Data packageyesData packages
Playbooksyes (one or more)Playbooks
Trade ideasoptionalTrade ideas
Preparation packageoptionalPreparation packages
Instrument profileoptionalInstrument profiles
Sentiment reportoptionalSentiment reports
  1. Session architecture — the four scopes a session controls.
  2. Sessions — the runtime view and session lifecycle.
  3. Trading cycle: overview — the cycle the session drives.