E ELARVEN

From Model Skill to Execution Reality

Why a prediction metric, an executable decision and realized PnL are different objects-and why missing fill data breaks the chain.

A model score, an executable order and realized PnL are not interchangeable observations. ELARVEN's Strategy Decay work began by asking whether the existing research archives were complete enough to trace that chain.

The intended waterfall

The target schema was:

research decision → live decision → executable entry → actual fill → spread cost → bid/ask asymmetry → rejected or missed → exit / realized PnL → risk and account context

What the archive contained

A data-readiness scan found candidate evidence across both the ELARVEN execution-intelligence work and older DRAGON archives. The first readiness pass located 77 ELARVEN candidates and 1,918 DRAGON candidates across the searched schema categories.

What was actually structured

LayerEvidence status
Live decisionStructured schema match found
Executable entryPartial structured match
Actual fillNo usable structured match
Spread costStructured schema match found
Bid/ask asymmetryPartial structured match
Rejected / missedPartial structured match
Exit / realized PnLPartial structured match
Risk / account contextStructured schema match found

The resulting mapping verdict was PARTIAL_CORE_STRUCTURED_EVIDENCE__GAPS_REMAIN.

Why the missing fill matters

Without a reliable actual-fill layer, it is difficult to attribute decay precisely. A model can be correct at decision time and still lose value through entry delay, spread, partial execution or a changed exit path. If those states are merged, model error and execution error become indistinguishable.

Research consequence

The work therefore stopped short of claiming a complete execution waterfall. The useful result was the schema itself and a precise description of which instrumentation must exist before strategy decay can be measured without guessing.

Limitations

  • The scan identifies structured evidence availability, not causal execution decay by itself.
  • Candidate counts are search/mapping counts and should not be interpreted as trade counts.
  • A complete future implementation requires systematic live fill capture and consistent order identifiers across the chain.