PayAttentionPrice Alert Studio
Local only

HISTORICAL PRICE ANALYSIS

Overview

Load historical observations and transparent rules to find verifiable signals.

Start analysis

CURRENT WORKSPACE

Your data at a glance

Load files or try the bundled sample.

Instruments0Unique price series
Observations0Historical closes
Rules0Validated conditions
Alerts—Latest completed analysis
01Load your dataSelect a CSV and rules JSON pair 02Configure rulesCreate level and moving-average rules 03Review signalsFilter, inspect and export results

01 / INPUTS

Historical data

Choose files or load the sample. Everything is parsed locally in this browser.

CSV

Prices

Required columns: date, instrument, close

Download sample prices CSV
{ }

Alert rules

Official and supported legacy JSON schemas

Download sample rules JSON

Select both files to preview and validate them.

Download sample prices

PREVIEW

Review parsed inputs

Waiting for valid files
Validated price rows and normalized rules will appear here.
Advanced input diagnostics Admin workspace · local only

Parsed CSV preview

Changes are applied only after selecting “Validate and apply JSON”.

Browser limits: 5 MB per file · 100,000 price rows · max decimal scale 10,000.

OPTIONAL

Add one observation

Append an observation to the loaded data without editing CSV manually.

02 / CONFIGURATION

Alert rules

Configure rule conditions with a guided form; advanced users can edit the JSON above.

No rules loaded

Load a rules JSON file or create a rule to configure your analysis.

LEVEL

Cross a price level

Above: previous close at-or-below; current close above.

Below: previous close at-or-above; current close below.

First observation cannot cross. Omitting direction retains Java's either-direction behavior.

MA_CROSS

Moving-average crossover

Requires full short and long windows. A crossover compares successive full-window averages.

Observations are sorted per instrument; calendar gaps do not interrupt the sequence.

Official fields are short/long; legacy shortWindow/longWindow aliases work too.

RULE EDITOR

Create alert rule
Compatibility notes and engine limits Admin workspace

Types and directions are case-insensitive. JSON property names are case-sensitive. Conflicting aliases, unsupported properties, duplicate IDs, and incomplete rules are rejected. Level thresholds can be any valid BigDecimal value; CSV closes must be positive. Browser decimal scale is capped at 10,000.

Admin mode is a local interface preference, not authentication or a security boundary.

03 / RESULTS

Analysis results

Run an analysis to reveal computed historical signals.

Detected alerts—
Instruments covered—
Rules evaluated—
Observation date range—
InstrumentAlert typeMessage

Results appear here

Load valid inputs and run analysis to see computed events.

No result setAnalysis is retained when filters change.

TRANSPARENCY

Historical signals, not forecasts.

Price Alert Studio is a separate client-side JavaScript implementation of the Java CLI. It uses the same rule definitions and matching alert semantics, but the Java JAR does not run in the browser.

Disclaimer: Historical rule alerts are not price predictions, investment advice, or recommendations.

Files are read, parsed, and evaluated locally. There is no upload API, market-data service, database, analytics, or remote storage.

Website documentation and limitations

SAME INPUTS → SAME ENGINE

CSV + JSON→Local parse→Rule engine→Alerts

Browser engine tests and a shared sample fixture are provided. See the feature-parity checklist for verified behavior and known boundaries.