Skip to content

Presentation layer for futures analytics

Sightline

Your engine publishes probabilities, value areas, ranked opportunities. Sightline turns them into a board, a brief and trade plans, and never recomputes a number.

Open the boardOne click. No signup, no email.

The demonstration shows the Sightline application reading a published snapshot: a futures board of six contracts with value areas and probabilities, today’s brief with engine ranked opportunities, and published trade plans. Part way through, the engine contract switches from v1.0 to v2.0 and the field map rewrites itself while every figure on the board stays the same.

A version bump in your engine should cost one mapping file and an afternoon. Not a quarter of dashboard rework, and not a room full of people arguing about which number is the real one.

Ingest path

Your engine stays the source of truth.

The payload arrives in whatever shape it already has. One adapter maps it to one internal model.

1Enginepublishes

On the wire

{
  "schemaVersion": "2.0",
  "board": [
    { "ticker": "ES",
      "price": { "last": 6842.25 },
      "probability": { "up": 0.62 } }
  ]
}
2Adapternormalizes

Field mapping

symbol←ticker
last←price.last
probabilityUp←probability.up
already a fraction
3Sightlinepresents

Rendered

ESZ66,842.25
E-mini S&P 500
Published probability62% up close
Engine stateAcceptance above value

Counted from the fixtures, on the server

60
fields the adapter resolves into the internal model
2
payload shapes it resolves them from
0
fields missing on either contract
6
contracts on the board, all published

The contract

Watch the payload change shape.

Names, nesting and units all move between v1.0 and v2.0. The model beside them does not.

Payload shape against internal model
v1.0
Engine contract in flight
4
Payload fields on the wire
0
Changes below the adapter
Engine payload
  • symstring
  • lastnumber
  • va_highnumber
  • prob_up_pctpercent
  • probability.horizonDaysnot in v1.0
Internal model
  • symbolstring
  • lastnumber
  • valueArea.highnumber
  • probabilityUpfraction
  • Four fields, both times. The adapter settles the units, so nothing downstream has to ask which contract produced the snapshot.

Four surfaces, one published snapshot.

RTH · 2026-09-04 · Balanced — two-way auction

Overnight inventory finished balanced and the open auction held above the prior value area high, which the engine reads as acceptance rather than a probe. Energy carries the strongest directional score on the board; rates are the only market where the engine flipped short since the previous publish.

#1 CL Trend continuation above breakout shelf71% · Intraday
#2 ES Acceptance above prior value area high62% · Intraday
#3 GC Value migration toward record high58% · Multi-session
#4 6E Range rotation between value extremes53% · Intraday

The boundary

The platform never has a second opinion.

Every number on every screen traces to a field in the payload.

What the platform is not allowed to do

  • Recompute a probability

    If the engine says 62%, the board says 62%. There is no blend, no smoothing and no house adjustment.

  • Invent a level

    Value areas and points of control are read from the payload. The platform has no opinion about where price should matter.

  • Render a partial snapshot

    A payload missing required fields is reported with the field names and the paths they were expected at, rather than displayed with holes in it.

Who opens it

Prop desks
One board the whole room reads the same way.
Newsletter analysts
Publish once, let subscribers open the plan.
Systematic shops
A window onto the model without exporting it.

The questions that come up first.

What does Sightline compute?
Nothing. Probabilities, market states, value areas, rankings and plans are all published by the engine and displayed verbatim. A platform that quietly recomputes its source has two answers to every question.
What happens when our engine changes its payload?
You add a mapping file. The internal model does not move, so nothing below the adapter changes. The demo ships with two contracts so you can watch that happen rather than take it on faith.
Do we have to change the engine to use this?
No. The payload arrives in whatever shape it already has, including flat keys with percentages as whole numbers. Unit conversion is a mapping detail, not an application concern.
Is the data in this demo real?
No. Every contract, level, probability and plan is generated, and the interface says so wherever it shows one.
What happens if a payload arrives incomplete?
It is reported, not displayed. The adapter names every missing field and the path it was expected at, which is more use than a stack trace.
Is any of this investment advice?
No. Sightline is a presentation layer for a third party engine's output. Nothing displayed is a recommendation, and the interface repeats that on every surface showing a plan.

Open the board and switch the contract.

Six contracts, ranked opportunities and published plans, normalized from an engine payload.

Open the board

Sightline is a demonstration. Every contract, level and plan in it is generated, and nothing shown is investment advice.