SNIPERTRADER
Education · Precision · Edge
Education · SniperTrader

For education only. Not financial advice. Past patterns do not guarantee future results. Protect capital first.

Meridian OFI Stacked Imbalance Mastery

From the CVD proxy to native footprint order flow. Version 2.2 reads real bid and ask rows, then stacks the diagonal imbalances into lattice type 10.

This course follows the Pine v6 script titled Meridian Engine v2.2 OFI. Course one is Meridian Engine v2 Mastery. Course two is Meridian OFI Engine Mastery, where cumulative volume delta, absorption, and imbalance are taught in full. This page recaps types 8 and 9 in a few lines, then stays on the stack.

v2.2 · Type 10 Diagonal footprint +1 grade nudge FP or px on the row

Seven modules. One new event.

01 · BRIDGE

From v2.1 to v2.2

Types 8 and 9 stay. The missing piece is a run of diagonal imbalances, still pointed at one side.

02 · ROWS

Footprint in plain English

Price rows, bid volume, ask volume, ticks per row, and why the comparison steps down or up one row.

03 · RUNS

How a stack is found

Walk the rows. Keep the longest same-side run. Default length is 3. A tie keeps the buy stack.

04 · FALLBACK

Native, or the CVD proxy

Prefer native footprint is on by default. If the footprint is missing, consecutive strong delta bars stand in.

05 · LATTICE

Type 10, grade, magnets

The bitmask now holds types 1 through 10. A stack can add one grade step. The zone can become a magnet.

06 · READ

Marks, row, alerts, tune

Green and red squares, one zone box, the OFI dashboard cell, and the six new inputs.

07 · PLAY

Three ways to use a stack

Continuation at a zone, a later magnet retest, and a stack beside absorption. Every rule is in the script.

Module 01 · The bridge

From v2.1 to v2.2

Stacked imbalance sits on the order-flow layer you already have. It does not replace it.

1.1 What types 8 and 9 already do

Order flow means who is pushing, read from volume. In v2.1 that read is a proxy called cumulative volume delta (CVD). Each bar splits its volume by the close versus the prior close. Up volume minus down volume is the bar delta. CVD is the running sum. The full reset modes, the 3-bar slope, and the level tests live in Meridian OFI Engine Mastery.

Two event types from that course still run in v2.2, on every bar, underneath the stack.

TYPE 8

Absorption. Strong delta fights the candle, and the candle wins, at a zone, a VWAP band, or the top magnet. A tiny circle marks it. Bullish absorption is a green circle under the bar.

TYPE 9

Imbalance. Strong delta agrees with the CVD slope, and with a break of structure, a VWAP reclaim, a zone, or a change of character. A tiny diamond marks it.

TYPE 10

Stacked imbalance. New in v2.2. Several neighboring price rows each show a one-sided diagonal imbalance. A tiny square marks it. That is the rest of this course.

Strong delta still means the bar delta is larger than OFI strong-delta × avg (default 1.5) times the 20-bar average of absolute delta. Types 8 and 9 use that test. The native stack does not. The proxy fallback does.

The engine under both layers is unchanged. The lattice, the magnets, the regime, the three gates, and the path are taught in Meridian Engine v2 Mastery. A lattice is a short memory of event types near price. Each type counts once. The count becomes a grade.

FIG 01 · V2.2 LAYER STACK V2 · TYPES 1–7 · STRUCTURE AND VWAP V2.1 · CVD PROXY TYPE 8 ABSORB · TYPE 9 IMBALANCE V2.2 · NATIVE FOOTPRINT TYPE 10 STACK · OR CVD MULTI-BAR PROXY DENSITY · EACH TYPE ONCE GRADE · THEN +1 IF STACK GATE 2 · STACK DOES NOT ARM GATE 3 · GRADE MUST CLEAR TYPES 8 AND 9 STILL REQUIRE A LEVEL TYPE 10 IS PUSHED WHEN THE RUN QUALIFIES BUY SQUARE #16A34A SELL SQUARE #DC2626 SAME GATES · SAME PATH · ONE NEW EVENT TYPE
FIG 01 · TYPE 10 SITS ON TYPES 8 AND 9 · THE GRADE CAN MOVE · GATE 2 STAYS A SWEEP, A RECLAIM, OR A CHOCH

1.2 The missing piece, and where a stack is allowed to count

A single diagonal imbalance is one loud price row. A stack is several of those rows in a row, all on the same side. That run is the high-value piece v2.1 could not see, because v2.1 never read a footprint. v2.2 asks TradingView for one, with request.footprint.

The design stays direction-aware. A buy stack pushes lattice direction 1. A sell stack pushes direction −1. Only one side is kept on a bar. The long grade and the short grade are still scored apart.

Types 8 and 9 still fire only at a level the engine already tracks: a fair value gap or order block, a VWAP sigma band, or the strongest magnet, inside OFI level proximity (×ATR) (default 0.4). Type 10 is different. The script pushes it whenever the run is long enough. It does not run that level test first.

The stack still has to sit near price to affect the grade. Density keeps an event only when its price is inside Lattice price proximity (×ATR) (default 1.5) of the close, and the event is inside the lattice lookback. The stored price of a stack is the midpoint of its zone. On the bar it prints, that midpoint is inside the bar, so the stack usually counts immediately. On later bars it counts only while price is still near that midpoint.

An entry still needs Gate 1, an arm, a zone, the filters, the grade, and a confirmed bar. The square is evidence. Gate 2 arms only on a sweep, a VWAP reclaim, or a CHoCH.
Module 02 · The rows

Footprint basics in plain English

A footprint is the inside of one bar, split into price rows, with buy volume and sell volume on each row.

2.1 Rows, bid, ask, and ticks per row

A normal candle hides the volume inside the high and the low. A footprint opens that range into rows. Each row is a thin slice of price.

  • Sell volume on a row is trade that hit the bid. Someone sold into a resting buy.
  • Buy volume on a row is trade that lifted the ask. Someone bought into a resting sell.
  • Ticks per row is how thick that slice is. A tick is the symbol’s smallest price step. The input is Footprint ticks/row. Default is 100. Minimum is 1.

Thinner rows mean more rows inside one bar. Thicker rows mean fewer rows, and a stack is harder to build. The script’s own note says to aim for about 15 to 40 rows on a typical bar. Module 6 shows how to tune that.

The call is always request.footprint(fpTicks, 70, fpImbPct). Pine needs that request on every bar, so the script calls it even when you turn native footprints off. The middle number, 70, is fixed. It is the value-area percent TradingView uses inside the footprint object. You do not have an input for it. You tune the ticks and the imbalance percent.

FIG 02 · ONE BAR, OPENED INTO ROWS HIGH LOW CANDLE ROW 6 · 105–106 · SELL 40 · BUY 15 ROW 5 · 104–105 · SELL 8 · BUY 70 · BUY IMB ROW 4 · 103–104 · SELL 12 · BUY 80 · BUY IMB ROW 3 · 102–103 · SELL 10 · BUY 90 · BUY IMB ROW 2 · 101–102 · SELL 20 · BUY 40 · QUIET ROW 1 · 100–101 · SELL 100 · BUY 10 · QUIET EACH ROW IS FOOTPRINT TICKS/ROW THICK · DEFAULT 100 TICKS SELL = HIT THE BID · BUY = LIFTED THE ASK THE SCRIPT READS THE FLAGS · IT DOES NOT RECOMPUTE THE VOLUMES
FIG 02 · A FOOTPRINT BAR IS PRICE ROWS · EACH ROW HAS SELL VOLUME AND BUY VOLUME · TICKS PER ROW SETS THE SLICE

2.2 Why the comparison is diagonal, and what 300% means

The best bid and the best ask sit one tick apart. A market buy lifts the ask. A market sell hits the bid. Comparing buy and sell on the same row mixes both sides of that spread. The useful comparison steps to the neighbor.

TradingView’s rule, which this script uses through the footprint flags, is written in the header comment:

  • Buy imbalance on a row: buy volume at that row is at least the threshold percent times the sell volume of the row below.
  • Sell imbalance on a row: sell volume at that row is at least the threshold percent times the buy volume of the row above.

The input is Imbalance threshold %. Default is 300. Minimum is 100. The step is 50. 300% means 3 times. Buy 90 against sell 20 on the row below is a buy imbalance, because 90 is at least 3 × 20. Buy 40 against sell 100 on the row below is quiet, because 40 is far under 300.

The script does not do that multiply itself. It reads has_buy_imbalance and has_sell_imbalance on each volume_row. The percent you set is passed into request.footprint, and TradingView sets the flags.

Native footprint data needs a TradingView Premium or Ultimate plan. The input label says Prefer native footprint (Premium+). On other plans, or on a symbol with no footprint, the request comes back empty and Module 4’s proxy takes over.
FIG 03 · THE DIAGONAL RULE · 300% IS 3 TO 1 ROW ABOVE · BUY VOL THIS ROW’S BUY ROW BELOW · SELL VOL NEIGHBOR’S SELL BUY ≥ 300% × SELL BELOW ROW ABOVE · BUY VOL NEIGHBOR’S BUY THIS ROW · SELL VOL SELL IMBALANCE LIVES HERE SELL ≥ 300% × BUY ABOVE SAME-ROW BID VERSUS ASK IS NOT THE TEST THRESHOLD INPUT DEFAULT 300 · STEP 50 · FLOOR 100
FIG 03 · BUY VOLUME VERSUS THE SELL OF THE ROW BELOW · SELL VOLUME VERSUS THE BUY OF THE ROW ABOVE
Module 03 · The walk

Stack detection

The script walks every row, keeps consecutive one-sided flags, and remembers the longest run on each side.

3.1 Consecutive runs, and the minimum length

When Prefer native footprint (Premium+) is on, and the footprint is not empty, the script sets a flag that this bar used real footprint data. It then walks rows() from the first row to the last.

Each row is one of three things:

  1. Buy only. The buy flag is on and the sell flag is off. The buy run grows by one. The sell count goes back to zero.
  2. Sell only. The sell flag is on and the buy flag is off. The sell run grows by one. The buy count goes back to zero.
  3. Anything else. Both flags, or neither flag. Both counts go to zero, and the running price span is cleared.

A row that is both sides is a break. It does not count for either run. The script keeps the longest buy run and the longest sell run it saw on that walk. If two buy runs have the same length, the first one is kept, because the script replaces a best run only when the new run is strictly longer.

The price span of a run is the lowest down_price and the highest up_price of the rows inside it. A direct flip from buy rows to sell rows, with no quiet row between them, starts a new count. The span is not cleared on that flip, so the new side’s box can still include the earlier rows until a quiet row or a both-sides row wipes it.

Min stacked imbalance rows defaults to 3. The smallest allowed value is 2. The largest is 12. A run shorter than that minimum is ignored.

FIG 04 · A RUN OF THREE BUY ROWS · THRESHOLD 300 ROW 6 · BUY 15 VS 3×8 = 24 · QUIET · BREAKS THE RUN ROW 5 · 104–105 · BUY 70 ≥ 3×12 · BUY RUN = 3 ROW 4 · 103–104 · BUY 80 ≥ 3×10 · BUY RUN = 2 ROW 3 · 102–103 · BUY 90 ≥ 3×20 · BUY RUN = 1 ROW 2 · BUY 40 VS 3×100 = 300 · QUIET ROW 1 · 100–101 · SELL 100 · BUY 10 · QUIET QUALIFIES · BUY STACK LENGTH 3 · MIN IS 3 ZONE 102 TO 105 LATTICE PRICE = MID 103.5 SELL SIDE ON THIS BAR NO SELL-ONLY RUN BEST SELL LENGTH = 0 ONE STACK PER BAR
FIG 04 · ROWS 3, 4, AND 5 ARE BUY-ONLY AT A 3:1 TEST · LENGTH 3 MEETS THE DEFAULT MINIMUM · ZONE IS 102 TO 105

3.2 Which side wins, including a tie

After the walk, the script picks one stack for the bar. The test is in this order:

  • If the best buy run is at least the minimum, and it is at least as long as the best sell run, the bar is a buy stack.
  • Otherwise, if the best sell run is at least the minimum, the bar is a sell stack.
  • Otherwise there is no stack.

A tie goes to the buy side. The comparison is bestBuyRun >= bestSellRun. Buy length 3 and sell length 3, with a minimum of 3, prints the buy stack. Sell length 4 and buy length 3 prints the sell stack, because the buy run is no longer at least as long. Buy length 2 and sell length 3, with a minimum of 3, prints the sell stack, because the buy run never cleared the minimum.

Buy wins the tie

Best buy 3, best sell 3, minimum 3. Direction is +1. Count is 3. The zone uses the buy run’s top and bottom.

Longer sell wins

Best buy 3, best sell 4, minimum 3. Direction is −1. Count is 4. The shorter buy run is dropped for this bar.

FIG 05 · THE RUN WALK NEXT ROW BUY ONLY BUY +1 · SELL COUNT 0 SELL ONLY SELL +1 · BUY COUNT 0 BOTH OR NEITHER CLEAR COUNTS AND SPAN KEEP THE LONGEST RUN ON EACH SIDE BUY ≥ MIN AND BUY ≥ SELL BUY STACK · TIES INCLUDED ELSE SELL ≥ MIN SELL STACK EQUAL LENGTH INSIDE ONE SIDE KEEPS THE EARLIER RUN IF NEITHER SIDE CLEARS THE MINIMUM · NO STACK THIS BAR
FIG 05 · WALK EACH ROW · A QUIET ROW BREAKS THE RUN · THE BUY SIDE WINS WHEN THE TWO BEST RUNS TIE
Module 04 · When the rows are missing

The graceful fallback

The feature still runs when the footprint is empty, or when you turn native data off. The stand-in is coarser.

4.1 useTrueFP, and what “na” does

useTrueFP is the input Prefer native footprint (Premium+). Default is on. na means “no value.” If TradingView cannot build a footprint, request.footprint returns na.

The script treats the bar as native only when both of these are true:

  • Prefer native footprint is on.
  • The footprint object is not na.

That bar is then marked fpNative. The dashboard will end the OFI text with ·FP. FP means footprint.

If the toggle is off, the footprint is still requested, and then ignored. fpNative stays false. The proxy runs. The dashboard ends with ·px. px means the price-bar proxy.

A real footprint that simply has no long enough run does not fall through to the proxy. Native data, even a quiet footprint, blocks the proxy for that bar. The proxy runs when the object is na, or when the toggle is off.
FIG 06 · NATIVE OR PROXY REQUEST.FOOTPRINT EVERY BAR TOGGLE ON AND OBJECT NOT NA? YES · NATIVE WALK THE ROWS DASHBOARD TAG ·FP NO · PROXY STRONG DELTA BARS DASHBOARD TAG ·px YES PATH QUIET ROWS STILL COUNT AS NATIVE NO QUALIFYING RUN · PROXY STAYS OFF NO PATH PLAN, SYMBOL, OR TOGGLE OFF TAG IS THE DATA SOURCE · NOT THE WORD NATIVE
FIG 06 · ·FP MEANS THIS BAR RECEIVED A FOOTPRINT OBJECT · ·px MEANS THE PROXY RAN · A QUIET FOOTPRINT DOES NOT SWITCH TO THE PROXY

4.2 The CVD multi-bar proxy, and why it is coarser

The proxy does not look inside the bar. It looks backward across bars. It starts at the current bar. A strong up delta adds one to the buy count and clears the sell count. A strong down delta does the opposite. The first bar that is neither strong up nor strong down stops the walk.

The current bar has to be part of the run. Three strong bars in the past, with a quiet bar now, do not print a stack. The loop breaks on bar zero.

The window is short. The loop runs from 0 through min(min stacked rows + 2, 8). That is at most nine bars, indexes 0 through 8. If you set Min stacked imbalance rows to 10, 11, or 12, the proxy can never qualify. A native footprint still can, up to the input maximum of 12.

When the proxy qualifies, the zone is not a set of footprint rows. The top is the highest high of those bars. The bottom is the lowest low. The count is the number of strong bars. There is no diagonal test. The same strong-delta multiple used by absorption, default 1.5, is the test.

Native stack

Neighboring price rows. Diagonal 3:1 flags. Zone is the row prices of the winning run. Dashboard tag ·FP.

Proxy stack

Neighboring bars with strong same-side delta. Zone is the high-low of that streak. Dashboard tag ·px. Coarser on purpose.

Example. Minimum is 3. This bar and the two before it are each stronger than 1.5 times their own average absolute delta, all to the upside. The bar before those three is quiet, so the walk stops. Buy count is 3. The script prints a buy stack and tags the row ·px.
Module 05 · Where the stack goes

Lattice and magnets

Type 10 joins the bitmask. A small grade nudge can follow. The zone can be stored as a liquidity pool.

5.1 Type 10, the +1 nudge, and Gate 3

Event codes in this script are fixed. 1 sweep, 2 CHoCH, 3 BOS, 4 VWAP reclaim, 5 band touch, 6 session tag, 7 fair value gap, 8 absorption, 9 imbalance, 10 stacked imbalance. A stack pushes type 10 at the midpoint of its zone, direction +1 or −1.

Density uses a bitmask. A bitmask is a row of on/off switches, one per event type. The loop checks bits 0 through 9, which are types 1 through 10. Repeating the same type does not raise the count. Two stacks in the lookback still count as one type 10.

The grade is built in this order. Learn the order. The nudge is last.

  1. Count the distinct types near this close. The lookback is Lattice lookback bars (default 12), shortened on Scalp and lengthened on Position. The price window is 1.5 × ATR by default.
  2. Session boost. London, the NY killzone, or the Silver Bullet multiplies that count by 1.25. These windows amplify. They are not a required gate.
  3. Round to a whole grade.
  4. Magnet bump. A direction-matched magnet of strength at least 1.0, within 1.2 × ATR, adds 1 if the grade is already at least 3. The cap here is 5.
  5. Transition haircut. In TRANSITION, if the grade is under 4 and the raw density is under 3.5, the grade is capped at 2.
  6. Stack nudge. If this side has a stack and the grade is already at least 2, add 1. The result is capped at 5.
Watch
2

Grade 2. A stack nudge can lift this to PRIME.

Prime
3

Default minimum to enter. Stacked alerts use this line.

Elite
4

Grade 4. Imbalance alerts start here. A nudge can reach SINGULAR.

Singular
5

The cap. Extra types and extra nudges stop here.

A stack by itself is one type. Rounded grade 1 is shown as a dash, and 1 is below 2, so the nudge does not fire. The stack needs company already inside the window before the +1 is allowed. Two types make WATCH. The nudge then makes PRIME.

Gate 3 reads the grade after the nudge. Min lattice grade to enter defaults to PRIME, which is rank 3. Gate 2 does not read the stack. A buy arm is still a sweep of the lows, a bullish VWAP reclaim, or a bullish CHoCH. The arm expires after a preset number of bars. The entry label still requires barstate.isconfirmed, so the bar has closed.

The nudge can undo a one-step transition haircut. A TRANSITION grade capped at 2, with a stack on that side, becomes 3. It can also stack on the magnet bump: three types can be PRIME, a strong magnet can make ELITE, and the stack nudge can make SINGULAR. The cap is still 5.
FIG 07 · BITMASK 1–10 · THEN THE NUDGE 1SWEEP 2CHOCH 3BOS 4VWAP 5BAND 6SESS 7FVG 8ABS 9IMB 10STACK EACH TYPE COUNTS ONCE · THE ARRAY HOLDS AT MOST 30 EVENTS BASE GRADE 2 WATCH · TWO TYPES STACK AND ≥2 GRADE 3 PRIME · AFTER +1 CAP 5 SINGULAR GATE 2 IS NOT IN THIS PICTURE GATE 3 COMPARES THE NUDGED GRADE TO MIN LATTICE GRADE A LONE STACK IS GRADE 1 · THE NUDGE STAYS OFF WATCH CYAN · PRIME EMERALD · ELITE VIOLET · SINGULAR AMBER
FIG 07 · TYPE 10 IS ONE BIT · THE +1 NUDGE RUNS ONLY WHEN THAT SIDE’S GRADE IS ALREADY AT LEAST WATCH · THE CAP IS SINGULAR

5.2 Registering the stack in the Liquidity Memory Map

Register stack as liquidity magnet defaults to on. A magnet is a stored liquidity pool. It has a price, a direction, an intensity, and a strength that decays.

  • Buy stack. The pool is placed at the stack bottom. Direction is +1, so it can support a long grade later.
  • Sell stack. The pool is placed at the stack top. Direction is −1, so it can support a short grade later.
  • Intensity is stack length × 1.5 × volume ratio. Volume ratio is this bar’s volume divided by the 20-bar average volume. If that average is zero, the ratio is 1.

A stack of 3 on a bar with twice the average volume starts at intensity 3 × 1.5 × 2 = 9. That is a strong start next to many sweep pools. The blueprint’s phrase “length times volume ratio” leaves out the 1.5. The script multiplies by 1.5.

Every cap the map already enforces still applies to these pools:

  • Max liquidity pools defaults to 20, and the input itself cannot go above 30 or below 5. A new pool past the cap deletes the oldest pool and its ray.
  • Magnet decay / bar defaults to 0.92. Each bar multiplies strength by that number. Under 0.15 the pool turns off and the ray is deleted.
  • A revisit adds strength only when price tags the level (within 0.35 × ATR, or the bar crosses it), volume is above 1.2 × average, and the candle closes in the pool’s direction. The add is half the original intensity.
  • The grade’s magnet bump needs strength at least 1.0, a matching direction, and a grade already at least 3, inside 1.2 × ATR.
  • TP3 can use the nearest opposing pool only when that pool’s strength is at least 0.8.
  • The lattice event list itself stops at 30 events. Older events fall off the back.
  • The chart box is a separate, tighter limit. Only the latest stack box is kept. The previous box is deleted. The box extends 12 bars to the right. The magnet ray is the memory that can outlive the box.
FIG 08 · STACK ZONE BECOMES A MAGNET BOX TOP 105 BOTTOM 102 · POOL LIVES HERE DIR +1 RAY LATER TAG INTENSITY = 3 × 1.5 × VOL RATIO DECAY 0.92 / BAR · DROP UNDER 0.15 · CAP 20 POOLS SELL STACK REGISTERS THE TOP · DIRECTION −1
FIG 08 · A BUY STACK STORES THE BOTTOM · A SELL STACK STORES THE TOP · THE BOX IS TEMPORARY · THE POOL DECAYS
Module 06 · On the chart

Chart, dashboard, alerts, and tuning

The visuals stay small. The row tells you the side, the length, and whether the bar used a footprint.

6.1 Squares, boxes, the OFI row, and the alerts

Abs ↑ circle Imb ↑ diamond Stack ↑ square #16A34A Stack ↓ square #DC2626

Buy squares print under the bar. Sell squares print above the bar. Both are tiny. Both use the input Show OFI absorption marks (default on). Turning that input off hides the circles, the diamonds, and the squares together. There is no separate switch for the squares.

Show stacked imbalance zones defaults to on. A qualifying stack draws one box from the zone top to the zone bottom, starting at this bar and ending 12 bars later. Buy boxes use green #22C55E. Sell boxes use red #EF4444. The fill is very transparent. The border is slightly stronger. The next stack deletes the previous box. You will not see a trail of old boxes.

The dashboard is the table at the top right, when Show dashboard is on. The last row is labeled OFI. If this bar has a stack, the cell leads with the stack. A buy stack of 3 on native data reads Stk↑3·FP, then a space, then the CVD number in volume format. A sell stack of 4 on the proxy reads Stk↓4·px, then the CVD number. The examples in the blueprint match that pattern.

When there is no stack, the same cell falls through: absorption, then imbalance, then the CVD slope (CVD↑, CVD↓, or a dash). The source tag is still attached. A quiet bar with a live footprint can read CVD↑·FP. The tag describes the data source of the bar, and the stack text describes the event.

Stacked alerts are alertcondition entries. You create them in TradingView’s alert dialog. The names and messages are:

Alert nameWhen it can fireMessage
OFI Stacked Imbalance Long Buy stack, and the long grade is at least 3 (PRIME). The nudge counts. Meridian OFI: stacked buy imbalance
OFI Stacked Imbalance Short Sell stack, and the short grade is at least 3. Meridian OFI: stacked sell imbalance
OFI Absorption Long / Short Absorption, and that side’s grade is at least 3. Meridian OFI: bullish / bearish absorption at level
OFI Imbalance Long / Short Imbalance, and that side’s grade is at least 4 (ELITE). Meridian OFI: strong bullish / bearish imbalance
Enable alert() calls gates the script’s runtime alert() lines, such as the entry text and the path text. The stacked alerts are alert conditions. That toggle does not turn them on or off.
FIG 09 · DASHBOARD OFI ROW NATIVE BAR OFI Stk↑3·FP 12.4K BUY · LENGTH 3 · FOOTPRINT CVD VALUE FOLLOWS THE TAG SQUARE UNDER THE BAR PROXY BAR OFI Stk↓4·px 8.1K SELL · LENGTH 4 · PRICE BARS NO SEPARATE NATIVE / PROXY ROW SQUARE ABOVE THE BAR STACK TEXT WINS THE CELL · ABS AND IMB SHOW ONLY WHEN THERE IS NO STACK
FIG 09 · THE OFI CELL READS STK↑3·FP OR STK↓4·px · THEN THE CVD NUMBER · ONE ROW, NOT A STACK OF NEW ROWS

6.2 The new inputs, and how to tune the rows

These six inputs sit in the Event Lattice group. Labels and defaults are the script’s.

InputDefaultWhat it does
Prefer native footprint (Premium+) true Use the footprint when the object is not empty. Off forces the proxy and the ·px tag.
Footprint ticks/row 100 How many minimum price steps sit in one row. Minimum 1. Tune per symbol.
Imbalance threshold % 300 The diagonal ratio. 300 means 3 to 1. Minimum 100. Step 50.
Min stacked imbalance rows 3 How long a run must be. Minimum 2. Maximum 12. The proxy cannot reach 10, 11, or 12.
Show stacked imbalance zones true Draw the zone box. Only the latest box is kept.
Register stack as liquidity magnet true Push the buy bottom or the sell top into the Liquidity Memory Map.

A few older inputs change the stack even though they are not new. Show OFI absorption marks shows or hides the squares. OFI strong-delta × avg (default 1.5) is the proxy’s strength test. Lattice lookback bars and Lattice price proximity (×ATR) decide how long type 10 stays in the grade. Max liquidity pools and Magnet decay / bar bound the magnet.

The script’s closing note says footprint calls are limited to one per script, and ticks per row should be tuned so a bar holds about 15 to 40 rows. It gives ES as about 4 to 20 ticks per row, and says crypto should be larger. The owner’s tuning note, which is guidance and not a second coded limit, is tighter: try 4 to 20 on ES or NQ, and 50 to 200 on crypto or on large-range bars. If stacks print too often, raise Imbalance threshold % to 400 or 500. The input will accept those values. The step is 50.

Start from the default of 100 only as a placeholder. If a typical bar has a handful of rows, lower the ticks per row. If the bar is a smear of tiny rows, raise it, until you land near 15 to 40 rows. Then, if the squares are still common, raise the percent before you raise the minimum length.
FIG 10 · TICKS PER ROW · AIM FOR 15–40 ROWS TOO THICK · FEW ROWS 4 ROWS · A STACK OF 3 IS MOST OF THE BAR IN RANGE · ABOUT 15–40 ES/NQ TRY 4–20 · CRYPTO TRY 50–200 SAME PRICE RANGE · SMALLER TICKS/ROW · MORE ROWS TOO MANY STACKS · RAISE THRESHOLD TO 400–500%
FIG 10 · TICKS PER ROW SETS HOW MANY SLICES FIT IN THE BAR · THE SCRIPT ASKS FOR ABOUT 15 TO 40 · 400–500% IS THE OWNER’S FIX WHEN STACKS ARE TOO COMMON
Module 07 · How to read it

Playbooks

Three readings. Each one uses a rule the script already enforces. None of them is a win rate.

7.1 A stack at a zone, as initiative

Initiative here means aggressive one-sided trade, which is what a stack measures. The script calls the nudge a high-conviction add when the stack lines up with the grade you already have.

A long continuation, read off the script, needs all of this on a closed bar:

  • Gate 1. The regime allows a long. TREND wants the ribbon or the cloud on the long side. RANGE wants discount or the lower extreme. TRANSITION is looser on bias and stricter on grade.
  • Gate 2. The long is armed by a sweep of the lows, a bullish VWAP reclaim, or a bullish CHoCH, and the arm has not expired.
  • A zone. Price is tapping an unmitigated bullish fair value gap, or an order block if those are shown.
  • The stack. A buy stack on this bar pushes type 10 and, if the long grade is already at least WATCH, adds 1, capped at 5.
  • Gate 3. The nudged long grade clears Min lattice grade to enter. Default is PRIME. No-chase, the RTH window on Scalp and Intraday, and band confluence if you required it, still apply.
  • One side. If the short grade is higher, the long stays quiet. If the grades tie, both stay quiet.
The square under a bullish zone is not the entry. If the arm is missing, or the grade is still a dash, the script will not print BUY. Do not click because the square is green.

7.2 The stack zone as a later retest

The box fades from the chart when the next stack replaces it. The pool can remain. With Register stack as liquidity magnet on, a buy stack leaves a long-side pool at the bottom of the zone. A later bar can use that pool in three ways the script already has.

  1. A grade bump on a revisit. If the magnet is still at least 1.0, price is within 1.2 × ATR, the direction matches, and the grade is already PRIME or better, the density function adds 1 before the stack nudge. A fresh stack on the retest bar can add one more, still capped at 5.
  2. A level for absorption. Types 8 and 9 can use the top magnet when it is within OFI level proximity, default 0.4 × ATR. A stack pool becomes that top magnet only if it is the strongest active pool. Absorption still needs its own tests: opposing strong delta, a rejection candle, and the CVD condition.
  3. A target. A sell-stack pool above a long, with strength at least 0.8, can be chosen as TP3. A buy-stack pool below a short can do the same. The path still confirms on TP1 and breaks on a close through the stop.

The pool only gets stronger on a revisit when volume expands and the candle closes in the pool’s direction. A tag with no volume, or a close the wrong way, does not add strength. Decay still runs, at 0.92 per bar by default, until the pool falls under 0.15.

FIG 11 · CONTINUATION NOW · MAGNET LATER AT THE ZONE · THIS BAR BULL FVG · GATE 3 ZONE STK↑ · TYPE 10 · +1 STILL NEEDS ARM + GRADE CONFIRMED BAR · ONE SIDE SQUARE DOES NOT ARM LATER · POOL STILL ACTIVE BUY STACK BOTTOM TAG + VOLUME + CLOSE UP CAN BUMP A PRIME GRADE BOX MAY ALREADY BE GONE
FIG 11 · A STACK AT A TAPPED ZONE CAN LIFT THE GRADE · THE STORED PRICE CAN MATTER AGAIN ON A LATER TAG

7.3 Beside absorption and imbalance

Types 8, 9, and 10 can all be true on the same bar. They are separate pushes. The bitmask will count each type once inside the lookback. A circle plus a square is two types, not two copies of one type.

Type 8 · circle

Opposing strong delta, a rejection candle, and a level. It is a defense. It still needs the level test that type 10 skips.

Type 9 · diamond

Same-side strong delta, a CVD slope that agrees, and structure or a zone. It is one bar of push, not a stack of rows.

Type 10 · square

A run of diagonal rows, or a run of strong bars in the proxy. It can add the extra grade step. The dashboard prefers its text.

If a buy stack and bullish absorption both print, the OFI cell shows the stack, not Abs↑. Look at the chart for the circle. The grade still received both types, if both prices sit inside the lattice window.

A useful pairing is a stack in the direction of the trade, and absorption at the level you are leaning on. The script allows that pairing. It does not score it as a special setup. You still need the arm, the zone, and the minimum grade. There is no win rate in this script for “stack plus absorption.” The known limits at the bottom of the file say to use a companion backtest if you want those numbers, and that no walk-forward test is built in here.

Path integrity does not grow a new rule for squares. TP1 first is PATH CONFIRM. A close through the stop first is PATH BREAK. The square can help create the path, through the grade. It does not move the stop.
After v2.2 · Not in this script

What’s next on the roadmap

The owner’s blueprint lists these as unfinished. They are not in Meridian Engine v2.2 OFI. Do not look for them on the chart.

Next Four items still on paper

Unfinished-auction magnets

The idea is to mark an extreme row that still has volume on both sides, and to project that price until it is filled. The v2.2 script has no unfinished-auction test and does not push that kind of pool.

Effort versus result

The idea is a z-score of delta against the price result, to filter weak absorption, on both true delta and the CVD proxy. The script’s absorption test is still the strong-delta multiple, the candle, and the level. There is no z-score.

Delta divergence

The idea is a new price extreme with opposing bar delta or CVD, used as an early path break or a grade penalty. The script does not compare price extremes to delta. Path break is still a close through the stop.

Extra dashboard rows

The blueprint describes separate rows for FP Stack, unfinished auctions, delta effort, and a Native / Proxy label. v2.2 keeps one OFI row. The stack and the ·FP or ·px tag live inside that cell, next to the CVD number.

Shipped in this script: the native diagonal footprint, the run walk, type 10, the +1 nudge, optional magnet registration, the multi-bar CVD proxy, the squares, the single zone box, the OFI row, and the two stacked alert conditions.

Seven takeaways. Then practice.

  • v2.2 adds stacked imbalance as lattice type 10. Types 8 and 9 still run. The full CVD lesson is in the OFI Mastery course.
  • A buy imbalance compares buy volume to the sell volume of the row below. A sell imbalance compares sell volume to the buy volume of the row above. 300% means 3 to 1.
  • The script keeps the longest one-sided run. Default minimum is 3. A tie keeps the buy stack. A both-sides row or a quiet row breaks the run.
  • Prefer native footprint defaults to on. Empty footprint data, or the toggle off, uses consecutive strong delta bars and tags the row ·px. A quiet but real footprint stays ·FP and does not use the proxy.
  • Type 10 counts once. The +1 nudge needs a grade of at least WATCH and stops at SINGULAR. Gate 3 reads that grade. Gate 2 does not arm from a square.
  • A buy stack can store its bottom as a magnet. A sell stack can store its top. Intensity is length × 1.5 × volume ratio. Pools cap at 20 by default, decay at 0.92, and drop under 0.15.
  • Squares are #16A34A and #DC2626, tied to Show OFI absorption marks. The OFI cell can read Stk↑3·FP or Stk↓4·px. Stacked alerts need PRIME. Unfinished auctions, effort z-scores, delta divergence, and extra dashboard rows are still roadmap.

Replay one closed bar. Name the data source, the winning side, the run length, and whether the grade was allowed to take the nudge. If you cannot, leave the square on the chart.

Stacked imbalance page → OFI Mastery course → v2 Mastery course →

FOR EDUCATION ONLY · NOT FINANCIAL ADVICE · MANAGE RISK ON EVERY TRADE