Market-intelligence startup, co-founder

Chart-Pattern Engine, Validated by Backtest

Rebuilt a chart-pattern detector with strict, volatility-scaled gates, then ran 347,000 look-ahead-free evaluations over eight years to test whether the patterns predict price. They do not, so the product claims were narrowed to match.

Headline number
347,000 point-in-time evaluations
Role
Built
Category
Data Platforms
Updated

Architecture

  1. Daily bars271 symbols, 8 years
  2. Pattern engine16 detectors, 5 gates
  3. Daily pattern sweep
    Point-in-time backtest347,000 evaluations
  4. Setup ranking score0 to 98, labelled a ranking
    Validation reportno directional edge
  5. Chart, scanner, setup board
One pattern engine feeds every surface. A point-in-time backtest harness runs the same engine against history and produces the validation report that set the product claims.

Key takeaways

  • 16 detectors, each behind five gates: structure, prior trend, depth, volume, and recency
  • 271 symbols times 8 years of daily bars, evaluated point in time with no look-ahead
  • Bars firing a signal fell from 12.99% to 4.85%; labelled charts from 58% to 27%
  • No pattern showed a directional edge, so the product says so

The situation

The first pattern detector labelled more than half of all charts with something. Members found that noisy, and I did not trust it. Before shipping pattern-based features to paying customers I wanted two answers: can we detect patterns cleanly, and do they actually predict anything?

What I built

A single engine with 16 detectors sharing five gates: a volatility-scaled zigzag for structure, a prior-trend requirement, a depth check, volume confirmation, and a margin-plus-recency test. One engine serves the chart analyzer, the scanner's pattern filter, and the setup board, so labels cannot drift between surfaces.

Then the honest part. I wrote a point-in-time replay harness that walks 271 symbols across eight years of daily bars, evaluating each detector only on data available at that moment, and compares forward returns against a matched base rate. 347,000 evaluations. The result: every pattern landed within about three points of the base rate. No edge.

The outcome

The rewrite cut false signals sharply: bars firing fell from 12.99% to 4.85%, labelled charts from 58% to 27%, and about 73% of charts now correctly show no pattern. The product claims were narrowed to what the data supports. Patterns describe geometry; they do not forecast. The ranking score built on top is labelled as a ranking, never a probability.

Why it matters

Most fintech content asserts. This platform measured, and published the measurement. Data discipline over marketing is the whole brand, and it started with being willing to find out the feature did not do what people wanted it to.

Stack

TypeScriptNode.jsDaily OHLCV barsBacktest harnessPostgreSQL

Need this built inside your organization?

One person, architecture to deployment. Tell me what is stuck and I will tell you where I would start.