RiskDrive — App

Review of the week

This XAUUSD trade broke 1 of its declared rules — the stop was widened mid-trade. The realized outcome is shown separately and does not change this.

XAUUSD · Tue Jun 9 · move 4 of 4 — open the review →

RULE BREACH

規則偏離

Rule conformance

9/17

checkable declared rules followed · outcome excluded

Net P&L

-$650

realized outcome — shown for context, not graded

Rule breaches

8

of the reviewed decisions had a recorded breach

Evidence-insufficient

0decisions

too thin to check a rule — recorded, not guessed

Outcome vs decision — every trade lands in a quadrant

Recorded breaches by rule

Counts each recorded rule breach. It does not claim a market-optimal alternative or attribute a dollar cost.

Conformance trend · 8 weeks

Top behavior pattern

Stop-moving under pressure

Recorded 7 times in 90 days, within 30 min of price approaching the stop. Rulebook §2 (no stop-move) flagged each time. Outcome impact is not attributed.

Instrument	Date	Annotation	Conformance	P&L	Verdict

← →

—

Conformance

—

Historical replay checks

HISTORICAL RULE IMPACT—

EVIDENCE LIMIT—

Connect broker^soon

⌧ Drop a closed-trade statement here A CSV or HTML export from MT4 / MT5 / cTrader — exact numbers, any broker, no login. Choose a file

Crop out your account number & balance first — we only need the trade. Nothing connects to your broker; nothing is stored without your say.

The rule this trade was meant to follow · required

The one thing no import carries — it sets what the review measures against. No rule → the review stays process-only.

Email for the review reply · required

+ add trade details — optional, your file carries the numbers

long short

Historical review only — no signals, no order execution, no account control. A founder reviews the closed-trade packet and replies by email.

1

Capturereads instrument, prices, and exact timestamps from your file or photo.

2

Check evidencerebuilds the price path and loads your rulebook to test conformance.

3

Submit for founder reviewa founder reviews the closed-trade packet and replies by email — no automated score.

Every review quotes historical evidence fields: submitted stop distance, target progress, rule exposure, sample size, confidence, and limitations. These are review labels, not forecasts or trade instructions. This page shows the evidence checklist used before a review packet can be treated as founder-reviewed.

Evidence checklist - submitted record coverage vs reviewed outcome

SAMPLE 4,310 decisionsWINDOW rolling 12 mo BRIER 0.171ECE 2.9%

Why incumbents can't show you this

A journal summarizes outcomes. RiskDrive makes a narrower review claim: what the submitted historical record can and cannot support. The packet is useful only when sample size, confidence, and limitations stay attached to the note.

Endpoint

# discovery
packet.load("closed_trade_review")

# local packet preview / manual review only / JSON
resp = await tool.call(
  trade = closed_trades[-1],
  mode  = "manual_review_only"
)
resp.conformance # "9 of 17 followed"
resp.boundary   # "historical_review_only"
resp.limitations # ["historical review only"]

Packet checks a reviewer can verify

Pilot review packet

Evaluate review quality on founder-approved closed-trade data only.

PILOT

Deterministic JSON schema

Versioned, no prose-only responses. Schema at /v1/schema.

v1.2

Published evidence fields

Sample size, confidence, limitations, and boundary fields stay visible.

required

Review status

Manual review, no autonomous execution.

manual

Recent receipts

time	reviewer	trade	review note	status	boundary
16:42:09	founder-review	EURUSD short	SYSTEM_COST	sample	no execution
16:40:51	founder-review	XAUUSD long	RULE_DRIFT	sample	no execution

§1

Max risk per trade: 1.5% of equity

Position size implying more is a Mistake; over 3% is a Blunder.

90d violations 3

§2

Stops are never widened

Moving a stop away from price after entry, for any stated reason.

90d violations 7

§3

Stop placed within 60 seconds of fill

Unprotected exposure beyond 60s is a Blunder regardless of outcome.

90d violations 2

§4

Add-to-loss rule

Adding to a losing position is marked as a historical rule breach in this sample.

90d violations 2

§5

No entries inside the no-chase zone

Chasing a move extended beyond 1.5× ATR(20) from the last base.

90d violations 1

Rules are yours and versioned — reviews always cite the rulebook version in force when the trade was taken, so changing rules never rewrites history.

This week

Reviews

Review a closed trade

Calibration

Review JSON