The PDT rule: what it is, why it matters, and how Apex1819 handles it

The Pattern Day Trader rule is one of the most important — and most frequently misunderstood — regulations governing retail trading accounts in the United States. It is a FINRA regulation that directly restricts your ability to trade if violated. Apex1819's compliance engine is explicitly designed to prevent PDT violations from ever occurring — not to warn you after the fact, but to veto the trade before it happens.

The core of the PDT rule is simple: accounts under $25,000 are limited to 3 day trades in any rolling 5-business-day window. The system tracks this counter in real time and will veto any trade that would constitute a 4th same-day round-trip, regardless of how high-conviction the signal is. The AI does not make exceptions for good signals. That's the point.

What the PDT rule is

FINRA Rule 4210 defines a day trade as buying and selling — or selling short and covering — the same security on the same trading day. This applies to equity trades in margin accounts. Cash accounts are technically exempt from the PDT rule itself but have T+2 settlement constraints that create different restrictions on capital reuse. Apex1819 accounts use margin by default at most brokers.

The consequence of a PDT violation is a 90-day trading restriction. During that period, the account can only execute closing transactions — meaning you can sell positions you already hold, but you cannot open new ones. No autonomous trading system can operate under that restriction. Avoiding PDT violations is not optional.

The $25,000 threshold

The PDT rule applies only to accounts with portfolio equity below $25,000. At or above $25,000, you can execute unlimited day trades in a margin account without PDT designation. This is one reason professional and institutional traders rarely encounter PDT as a constraint — they're simply above the threshold.

For retail accounts below $25,000 — which is the majority of Apex1819 users starting out — the 3 day trade limit per rolling 5-day window is a real operational constraint that shapes the trading strategy. The AI accounts for this by preferring swing trades (multi-day holds) over pure intraday plays when the PDT counter is elevated, and by prioritizing the highest-conviction signals when only one or two day trade slots remain in the window.

How GUARDIAN tracks the counter

The compliance engine reads the PDT counter from the trade history in real time, before evaluating any proposed trade. The rolling window is exactly 5 business days — Monday through Friday, excluding market holidays. A day trade executed on Tuesday counts against Wednesday, Thursday, Friday, Monday, and Tuesday of the following week, then drops out of the window.

This is a rolling window, not a calendar week reset. A common mistake: assuming that a new calendar week resets the counter. It does not. Three day trades on Thursday and Friday of one week leave you with zero day trades available through the following Thursday. The system calculates this correctly; the dashboard's PDT counter display reflects the actual remaining count at any moment.

What happens when you're at 2/3

At 2/3 day trades used in the rolling window, the compliance engine still approves intraday round-trips for qualifying signals. Nothing changes in signal generation or approval behavior — the full pipeline runs normally. The only difference is that the system is one approval closer to the veto threshold.

At 3/3, the compliance engine vetoes any new signal that would require a same-day exit. This includes signals with a 95 Alpha score. The AI cannot make exceptions here. A trade that scores 95/100 and would be a same-day round-trip gets vetoed with reason PDT_LIMIT_REACHED and logged to the counterfactual tracker — so its outcome is still tracked and feeds into the learning system's accuracy analysis.

Future: in-app veto links to this article

A planned enhancement links compliance veto reason strings — specifically those containing PDT, day trade, or pattern day — directly to this article inline from the signal feed. When a PDT veto appears, a "Learn why" link will open this article in a side panel without leaving the feed. This integration is built into the veto reason mapping system already in production; the UI surfacing is pending.

The intent is to eliminate the friction between seeing a veto reason and understanding what it means. Most users who hit a PDT veto for the first time are confused by it — not because the rule is hard to understand, but because nobody explained it to them clearly before the restriction happened. That is what this article is for.