Account Guardian

One written trading policy. Paper orders placed through Precrime are refused when they break an enforced rule. Imported brokerage history is audited against the same policy; it cannot be blocked after the fact.

Current status

Latest recorded session · 2026-10-09

Session P&LLimit −$1,500: +$628
Week P&LNo weekly limit: +$4,039
Trades this sessionLimit 5: 3

Losing streakPause at 2: 0
Equity (realized): $96,913
Flags in history88 on enforced rules: 263

Enforcement

What each rule can actually do

RulePaper / simulationLive brokerage

Max risk per tradePapersimulation enforcedLivemonitoring only
Max daily lossPapersimulation enforcedLivemonitoring only
Max weekly lossPapernot availableLivenot available
Max open exposurePapermonitoring onlyLivemonitoring only
Max simultaneous positionsPapermonitoring onlyLivemonitoring only
Trading hoursPapersimulation enforcedLivemonitoring only
Max trades per sessionPapermonitoring onlyLivemonitoring only
Min planned risk/rewardPapermonitoring onlyLivemonitoring only
Stop-loss requiredPapersimulation enforcedLivemonitoring only
Consecutive-loss pausePapersimulation enforcedLivemonitoring only
Cooldown after a lossPapermonitoring onlyLivemonitoring only

No brokerage integration is connected, so nothing here can stop an order sent directly to your broker. Live rules are monitoring only: they are checked against imported history. A broker adapter must use the broker's own server-side risk controls before any rule is shown as broker supported.

Violation history

263 flags

Max open exposure54×−$6,326
Min planned risk/reward49×−$8,135
Cooldown after a loss37×−$1,829
Max risk per trade36×−$3,887
Consecutive-loss pause19×−$1,791
Held through planned stop18×−$18,162
Stop-loss required15×−$1,364
Trading hours13×−$881
Stop widened after entry10×−$7,339
Max trades per session7×−$162
Max daily loss5×+$1,928

Right column: combined net P&L of the trades carrying each flag (a trade counts once per flag type).

Recent flags

Max risk per tradeenforced rule
Thu, Oct 8, 10:59 · Risk $1,055 vs limit $947 (1% of $94,728).
Max open exposuremonitored
Thu, Oct 8, 10:59 · Open notional would be $299,204 vs limit $150,000.
Min planned risk/rewardmonitored
Wed, Oct 7, 15:33 · Planned R:R 1.20 vs minimum 1.5.
Trading hoursenforced rule
Wed, Oct 7, 15:33 · Entry at 15:33 vs window 09:40–15:30 (America/New_York).
Max trades per sessionmonitored
Wed, Oct 7, 15:33 · This would be trade 7 of the session (limit 5).
Cooldown after a lossmonitored
Wed, Oct 7, 15:33 · 4.0 min since last losing exit (cooldown 15 min).
Min planned risk/rewardmonitored
Wed, Oct 7, 15:25 · Planned R:R 1.20 vs minimum 1.5.
Max trades per sessionmonitored
Wed, Oct 7, 15:25 · This would be trade 6 of the session (limit 5).
Max risk per tradeenforced rule
Wed, Oct 7, 12:07 · Risk $1,048 vs limit $943 (1% of $94,291).
Consecutive-loss pauseenforced rule
Wed, Oct 7, 12:07 · 2 consecutive losing trades this session (pause at 2).
Cooldown after a lossmonitored
Wed, Oct 7, 12:07 · 8.0 min since last losing exit (cooldown 15 min).
Max open exposuremonitored
Wed, Oct 7, 12:07 · Open notional would be $299,111 vs limit $150,000.
Max risk per tradeenforced rule
Wed, Oct 7, 11:39 · Risk $1,425 vs limit $947 (1% of $94,655).
Min planned risk/rewardmonitored
Wed, Oct 7, 11:39 · Planned R:R 1.00 vs minimum 1.5.
Cooldown after a lossmonitored
Wed, Oct 7, 11:39 · 5.0 min since last losing exit (cooldown 15 min).
Max open exposuremonitored
Wed, Oct 7, 11:39 · Open notional would be $238,118 vs limit $150,000.
Cooldown after a lossmonitored
Fri, Oct 2, 12:41 · 1.0 min since last losing exit (cooldown 15 min).
Max risk per tradeenforced rule
Thu, Oct 1, 12:41 · Risk $1,436 vs limit $910 (1% of $91,006).
Min planned risk/rewardmonitored
Thu, Oct 1, 12:41 · Planned R:R 1.00 vs minimum 1.5.
Max daily lossenforced rule
Thu, Oct 1, 12:41 · Session realized P&L $-1,793 vs limit −$1,500.
Consecutive-loss pauseenforced rule
Thu, Oct 1, 12:41 · 3 consecutive losing trades this session (pause at 2).
Cooldown after a lossmonitored
Thu, Oct 1, 12:41 · 5.0 min since last losing exit (cooldown 15 min).
Max open exposuremonitored
Thu, Oct 1, 12:41 · Open notional would be $239,396 vs limit $150,000.
Max daily lossenforced rule
Thu, Oct 1, 12:31 · Session realized P&L $-1,645 vs limit −$1,500.
Consecutive-loss pauseenforced rule
Thu, Oct 1, 12:31 · 2 consecutive losing trades this session (pause at 2).
Max risk per tradeenforced rule
Thu, Oct 1, 11:48 · Risk $1,436 vs limit $926 (1% of $92,610).
Min planned risk/rewardmonitored
Thu, Oct 1, 11:48 · Planned R:R 1.00 vs minimum 1.5.
Cooldown after a lossmonitored
Thu, Oct 1, 11:48 · 6.0 min since last losing exit (cooldown 15 min).
Max open exposuremonitored
Thu, Oct 1, 11:48 · Open notional would be $238,989 vs limit $150,000.
Held through planned stopmonitored
Thu, Oct 1, 11:42 · Exited at 123.36, beyond the planned stop 123.82. Extra loss vs. the stop: $221 before slippage.
Max risk per tradeenforced rule
Wed, Sep 30, 13:16 · Risk $1,445 vs limit $914 (1% of $91,374).
Min planned risk/rewardmonitored
Wed, Sep 30, 13:16 · Planned R:R 1.00 vs minimum 1.5.
Cooldown after a lossmonitored
Wed, Sep 30, 13:16 · 2.0 min since last losing exit (cooldown 15 min).
Max open exposuremonitored
Wed, Sep 30, 13:16 · Open notional would be $239,580 vs limit $150,000.
Max risk per tradeenforced rule
Wed, Sep 30, 12:20 · Risk $1,043 vs limit $895 (1% of $89,515).
Max open exposuremonitored
Wed, Sep 30, 12:20 · Open notional would be $298,162 vs limit $150,000.
Min planned risk/rewardmonitored
Tue, Sep 29, 15:33 · Planned R:R 1.20 vs minimum 1.5.
Trading hoursenforced rule
Tue, Sep 29, 15:33 · Entry at 15:33 vs window 09:40–15:30 (America/New_York).
Min planned risk/rewardmonitored
Tue, Sep 29, 15:28 · Planned R:R 1.20 vs minimum 1.5.
Held through planned stopmonitored
Fri, Sep 25, 14:10 · Exited at 223.91, beyond the planned stop 224.34. Extra loss vs. the stop: $572 before slippage.

Audit trail

Signed-in accounts only

Policy changes, imports and deletions are logged with timestamps for signed-in accounts. Demo changes are not stored on the server.