MARKET PULSE

How it works

A system you can see into, from the first rule to the last rupee of paper P&L.

Four views of the same machine: how prices become paper trades, how a strategy grows up, the states a deployment moves through, and how any number can be traced back to the price behind it.

Under the hood

From a live price to a line in your record

Prices come in, your rules decide, shared safety rules check, and the trade is filled on paper and written to an append-only ledger. No order ever leaves for a broker.

  1. 01

    Live price

    Exchange quotes, each kept with where and when it was taken.

  2. 02

    Your rules

    Entry, exit and risk blocks, checked as prices arrive.

  3. 03

    Safety rules

    Price bands, position caps, kill switch, square-off. Same for every strategy.

  4. 04on paper

    Paper fill

    Priced from the quote it names. No quote, no fill: the signal is logged as skipped.

  5. 05

    Ledger

    Signal, order, fill, trade and day result. Rows are added, never edited.

  6. 06

    Your record

    Your dashboard, and the marketplace if you publish.

Broker and exchange

off

There is no path from a strategy to a real order. Paper mode is enforced by the database itself, not only by the screen.

The paper runner on this server is being set up. This is how it works once it starts.

Strategy lifecycle

From an idea to a record others can check

Build the rules, let the checker catch mistakes, test on past prices, then run on paper. Anything you learn on the way sends you back to the builder.

  1. 01

    Build

    Pick an instrument, write entry and exit blocks, set stops and targets.

  2. 02

    Check

    Every field is validated before the strategy is saved.

  3. 03planned

    Backtest

    Run the saved rules over past NSE prices, costs included.

  4. 04

    Paper

    Deploy with paper capital and watch the record build day by day.

  5. 05

    Publish

    Share it with the full record attached, losing days included.

Check, Backtest or Paper can send you back to Build.

A deployment's life

Four states, and the record survives every one

A deployment waits, runs, and ends either because it was stopped or because the runner could not continue. Deploying again starts a new record; the old one is never rewritten.

Queued

Saved with a frozen copy of the rules, waiting for the session to open.

on paper

Running

Every signal, order and fill is written as it happens.

Stopped

You stopped it from your dashboard. Its record stays as it was.

Failed

The runner hit something it cannot trade through. The reason is logged.

Deploy again creates a new deployment with its own ledger. Nothing from the earlier run is edited or deleted.

Numbers you can trace

Every figure walks back to a price

A day's result is the sum of its trades, a trade is made of fills, and each fill names the quote it was priced from. If a link is missing, the figure is not shown.

  1. Quote

    Where and when the price was taken.sourcequote_atprice

  2. Fill

    Never earlier than its quote, never edited.priceqtychargesfilled_at

  3. Trade

    Entry to exit, with why it closed.entryexitreasonnet = gross − charges

  4. Day result

    One row per deployment per day.tradeswinslossesnetequity

LoginRead the docs