The Patterns tab is point-in-time: it shows you the state of all 28 detectors today. The Insights feed is the time axis on top of that — every time the Engine recomputes your patterns, it diffs against the previous snapshot and persists the changes:
- new — a detector started firing this run that wasn't firing before (a fresh red flag).
- resolved — a detector stopped firing (you cleared a discipline issue).
The feed lives at Tools → Analytics → Insights feed. Each row carries the date the change was detected, the detector kind (Revenge trading, Friday drift, …), and a link that drops you back into the matching card on the Patterns tab so you can see today's full context.
The snapshotter runs automatically on every Patterns recompute — you don't have to do anything. Resolved entries are intentional: the positive-reinforcement signal that you cleared a behaviour issue is one of the few things in trading that's worth celebrating. The Engine gives them equal weight with new findings.
The feed is a self-coaching loop. Two readings make it useful:
1. Cadence of new entries. Three red flags in a single week is a stress signal — the Engine spotted three different behaviour breakdowns at once. Don't try to fix all three at once; pick the one with the highest impact (typically Revenge trading or Overtrading) and work on it for a week, then re-read the feed. 2. Time-to-resolve. When a red flag appeared three weeks ago and is still in the feed, your interventions aren't biting. When something appears one week and clears the next, you found the lever. Either reading helps you calibrate how much friction your discipline rules actually create.
Why we exclude info-only cards. The R-Multiple distribution and hold-time quality detectors show structure, not warnings. They're informational. Putting them in the feed would dilute the actionable signal — the feed is a behavioural-warning log, not a stats archive. The Patterns tab is where you read the structural reports.
Sunday review pairing. Open the Insights feed right before the weekly digest email — five minutes of scrolling tells you what the Engine flagged this week without you having to re-read every detector card. Anything appearing for the second or third time gets a sentence in your journal: "Friday drift again — what's different about Fridays?"
Trader-coach handoff. If you ever work with a coach, the feed is the cleanest possible artifact to share — one CSV-export, one timeline, no narrative coloring. The coach sees what you've been wrestling with, when you cleared what, and what's still recurring. No screen-share needed.
When the feed is empty. That's fine. Either you haven't hit the 20-trade threshold yet that the Onyx Engine needs, or no detector is firing — in which case there's nothing to coach yourself on, and you keep journaling until something shows up. Silence here is the same signal as silence on the Patterns tab: no behavioural pattern strong enough to act on.