Cookbook

Complete, working wrun indicators you can copy, run, and adapt, in six groups: what to draw on price, how to read order flow, prediction-market odds read against the markets they move with, HUD cards that read a market at a glance, views beyond the time axis (profiles, volatility curves and surfaces, fund flows, the order book, cross-market maps, calendars, the yield curve), and strategies that trade. Forty of them are also the templates the chart's New indicator starter list offers, one card each, under the same group names; the other six are shorter recipes that build up the loop one idea at a time, each with the indicator in full and the reasoning behind it.

Every recipe page is a full indicator, not a snippet. Pick its card in the editor's starter list, or paste it into a blank indicator tab under the language marker, press Run, and it works. Then read "How it works" for the moving parts, "Where it runs" and "When data is missing" for the markets it serves and what it says on the ones it does not, and "Customize it" for the variations worth trying. Each recipe ends with the concept pages behind it, so you can go deeper wherever something catches your eye.

Inside a group the shorter recipes come first, easy to advanced, then the picker's templates in the picker's order. The first one is the cleanest introduction to the loop: load a series, compute a number, draw it.

1. On price: marks, zones and tints drawn on the chart's own bars.
2. Order flow: buyers and sellers, open interest and liquidations, bar by bar.
3. Prediction markets: a Polymarket market's odds against the market they move with.
4. HUDs: one reading of the whole market, kept beside the candles.
5. Beyond the time axis: profiles, curves, chains and fund flows on a second axis.
6. Strategies: packages that trade, replayed by the Strategy Tester.

On price

Marks, zones and tints drawn on the candles themselves, from the chart's own bars.

Order flow

Who traded, who is positioned and who was forced out, from sided trades, open interest and liquidations.

Prediction markets

A Polymarket market's odds set against the market they move with.

HUDs

One card pinned to the price pane, each in its own look, that answers one question first and reads the numbers behind it underneath, kept current on the live bar.

Beyond the time axis

Views whose second axis is price, tenor or the calendar.

Strategies

Packages that trade: orders placed in the file, replayed by the Strategy Tester under the chart.

How to use a recipe

• The ring is the loop: the Editor, Templates, the recipe's card, Run, a setting changed, a value read at the Console prompt, and back to the editor.
• Publish leaves the ring: the indicator goes to other charts, to readers and to alerts.
• The three verbs in the middle are what every recipe does: load a series, compute a number, draw it.

1. Open the editor: the chart toolbar's Editor button, or the Build icon in the Indicators dialog.
2. For a recipe that is also a template, press the Templates icon ("Browse starter templates") in the editor's Explorer and pick the recipe's card under its group. The pick fills an untouched draft, or opens in a tab of its own, with the //@lang=wrun-ts line on top. For any other recipe, press New indicator in the Explorer, pick Blank indicator (a tab holding the //@lang=wrun-ts line alone), and paste the recipe's indicator block under that line.
3. Press Run on a liquid symbol. Run compiles the file in your browser and draws it on the chart. The order-flow recipes want a market where the venue reports buy and sell volume; each page's "Where it runs" names the markets it serves.
4. Open the overlay's settings. Every setting is a row there, labelled by its description and drawn as the control its kind names (a number field bounded by its min and max for param(...) and param.int, a toggle for param.bool, a menu for param.choice), so lookbacks and thresholds change without touching code, and a change reruns the indicator over the loaded bars. Colors are declared on the outputs, boxes, and segments: edit the hex strings and Run again.
5. Read a value at the editor's Console prompt, which reads the last run without a new build (below).
6. Publish it from the editor to add it to other charts, share it, or put an alert on it (Publishing, Alerts). A published indicator runs in each reader's browser, or on OpenMarket's servers when its code is Protected.

What the Console prompt answers after a Run, with the Volume spike detector's z as the output:

outputs       every output with its value on the newest bar
params        the settings the last run used
rows          the bars the run covered, the first and last bar time, the warm-up bars
z             the output's value on the newest bar
z[-3]         the same output three bars back
last 20 z     its last 20 bars; a data-only output reads the same way

Most recipes read the chart's own market and interval (Execution model). The ones that pin say so on their page. The chart serves a pin on a secondary ohlcv input: an interval coarser than the chart's and a whole multiple of it (Multi-timeframe), or another market at the chart's interval (Odds vs price). A market pin on any other source is refused by name, which is why Aggregated CVD reads the chart's own venue. Stocks, forex and gold pin the same way (Multi-source). On CME markets the editor's Run is paused, and a community indicator cannot read CME data; OpenMarket's official wrun indicators can.

What the recipes share

A few shapes come back in every recipe:

• State lives in module-level variables. A value that must survive from bar to bar is a module-level let; a window of past values you index into is a StaticArray<f64> ring buffer, which History packages as a class (Stats, history and lists).
• Decisions are numbers. A condition the chart should act on is a data-only none output written as 1 or 0; the declarations turn it into a look through shape_where, color_by, or a box's when gate.
• Calendar math comes from the bar's open time. bar.time() is each bar's open in epoch seconds; dividing by 86400 gives the UTC day, and a boundary in that index is where sessions reset.
• An output can carry an alert. Once the indicator is published and on a chart, the chart's alert dialog offers every drawn output with conditions such as Crosses above and Greater than, and a data-only gate becomes a ready-made signal through alert(name, { when }) in the file (Alerts).