Futures · Futures analysis foundations · lesson 9 of 9 · 7 min read · David Alexander

Building a futures read

the futures read

The routed underlying view, dressed in the layer's checks: the view and its difference from consensus from the underlying's track; crowding from OI trend and the COT's right category; the curve and basis clean or explaining themselves; the merged calendar's date; the invalidation on the board's honest chart. The router's division of labour, ending in numbers the plan can size.

Fifth read-assembly lesson, with the module's one structural difference: the view is imported. The assembly is what the layer adds around it.

The assembly

The view, routed: the underlying track's read, built by that track's methods - the balance sheet, the layers, the crowd-reading - arriving with its own difference-from-consensus and audit date. Without it, there is nothing to assemble.
The crowding checks: OI trend and the family's COT category against their histories - is the view already funded, already everyone's? Lessons 3 and 6.
The machinery checks: curve change consistent with the view or asking questions; basis clean, leaning on schedule, or impaired - lessons 4 and 5.
The date and the collision scan: the merged calendar's grading date, and any contract-stream collisions between here and there - lesson 7.
The shape: entry, stop and invalidation on the board's honest charts - lesson 8 - converted through the multiplier into module 4's arithmetic, per the worked example.

What the layer can veto, and what it cannot

The honest division: the layer's checks can downgrade a read - crowded positioning, an impaired basis, a collision-heavy path to the date all subtract conviction or size - but they cannot upgrade one, because the layer measures machinery and crowds, not the underlying's truth. A clean basis and quiet positioning around a wrong view is a wrong view, well-plumbed. The underlying track giveth; the layer taketh away - and a read that survives both is the occasional, differentiated object every analysis module on this platform has ended by describing.

The track's analysis, closed

Route the view, check the layer, merge the calendars, shape the trade - and hand the numbers to the plan. The occasionality clause survives its fifth telling unchanged: most weeks the honest output is 'the consensus looks right, the machinery is clean, nothing to do' - and on an asset class where doing nothing is free of even a financing meter, that output costs less here than anywhere. Module 6 turns the recurring reads into rules the machine can test.

Worked example

figures in USD

A futures read converted to a trade, in index points: entry 8,040, stop 8,000, target 8,120. Point ratios carry no currency, so a USD account runs the same arithmetic through its own contract's multiplier.

The routed view: the underlying's track says tighter than consensus, the next release should show it, OI says the trade is not yet crowded, the basis is clean. Entry 8,040, stop 8,000 - session-range based, per module 4 - target 8,120.
40 points of risk per point against 80 points: ratio 2.0, break-even 33.33% - and the multiplier turns each into account money per module 4's arithmetic.
The read named its underlying logic, its futures-layer checks, its date and its invalidation. The layer added context; the underlying carried the view - the router's division of labour, ending as always in a shape the plan can size.

Check your understanding

Question 1 of 2

Why can the futures layer veto a read but never upgrade one?