Skip to content
AQREVI
product / trader dna

Where you have an edge, and whether you can claim it.

Any slicing of statistics will show something. The edge map tests each cut statistically and shows only the ones that hold up.

The edge map: five claims out of sixty-one cuts

A hundred numbers and no finding.

Slice statistics long enough and some cut will show a profit. You can't tell a finding from chance by eye, and traders lose money trusting a pattern that isn't there.

five out of sixty-one

How it works here

The map keeps the cuts that survived the test.

Every dimension and every pair

Setup, market regime, session, instrument, weekday, holding time and their combinations. In the demo journal that's 61 cuts over 318 trades.

The honesty gate

A confidence interval, a correction for multiple comparisons and a check window by window. In the demo, 46 cuts reached a usable size and five passed the gate.

Decay on its own

A cut that held in early windows and gave out in the last one goes to the decay section. 'Worked and stopped' reads differently from 'doesn't work'.

Tested by number

How many trades a claim needs to be reliable, what the interval is now and what happens if your trades are reshuffled a thousand times.

  • A confidence interval on every figure
  • The required sample size named as a number
  • Resampling: how often the result stays positive
  • A correction for having checked many cuts
Trust: the interval and the sample it needs

The dossier: how you trade

A short interview about your style: how you enter and exit, the risk you hold, what you call a mistake. Facts are built from your answers, files and trades, and the AI judges a trade by them.

  • Every fact shows its source: interview, file, chat or trade
  • Saving writes a new version; the old one stays
  • A review gets the facts that bear on the question, not the whole dossier
  • No field is required
The dossier: the trader profile and sourced facts

Why the market moved: by frequency

On a day with an unusual move, the system looks for what else moved unusually and counts how often that coincidence happened over the year.

  • 'Coincided in 7% of cases, observed 42 times'
  • Under ten observations, no percentage
  • Calendar events stand apart, with no percentage
  • Your trades from that day alongside
What moved together and how often that happens

A link graph with no 'therefore' arrow

Setups, regimes, sessions, instruments and mistakes are nodes. Link thickness shows the number of trades, colour shows the result. A hypothesis can only be recorded together with the cut it refers to.

  • An edge says 'occur together'
  • A hypothesis without a cut is refused
  • A recorded hypothesis goes through the same gate
  • Thickness and colour come from the data
The graph: what occurs with what in your history

Where it differs

Typical analytics shows everything it computed and leaves you to decide what to trust. The edge map shows five cuts out of sixty-one, each with a status: established, emerging, hypothesis, not enough data. Twelve trades give no finding, and the screen says so.

Check it yourself

Create the demo journal with one button and open the edge map. The pattern is built into the trade prices, not the labels, and the engine finds it with the same code that runs on your trades.

The order

From an empty screen to the first review

Answer the interview

A couple of minutes about your style. You can skip it and come back later.

Build up history

While trades are few, the map says 'not enough data'. That's normal for the first weeks.

Open what's established

Each card opens into the list of trades it was built from.

What it does not do

What this module does not do

  • On a short history the map claims almost nothing. That's intended.
  • A link between dimensions isn't called a cause. A graph edge says 'occur together'.
  • There's no graph as of a past date: discovery dates for links aren't stored yet.

Questions

The things that stand in the way

Why are so few claims shown?

The rest failed the test. Showing them would make noise look like a finding.

Does this use a model?

No. The map, the trust figures and the graph come from code under tests. A model can retell the result in words, but *it produces no numbers*.

How many trades until the first finding?

It depends on the cut and the spread of results. The trust screen names the sample needed for each figure.

An edge you can claim

A cut on the map has survived the interval, the correction and the window check. Everything else is labelled for what it is.