Current limitations

These are outstanding capabilities or decisions, not instructions to reimplement shipped features.

AreaRemaining work or restriction
Futures dataThe oi_based and dsl roll policies have no implementation: engine/roll/oi.go and engine/roll/dsl.go were deleted in GLE-322 (their open-interest and FND/LND inputs never reached the adapter contract). ER5 (GLE-327) then deleted the volume policy, engine/roll, the registry loader and continuous.Build: marketfeed’s served schedule is the only election. Partial-roll scheduling remains deferred; spread orders are combo orders on dated contracts since GLE-409 (Combo orders), refused on continuous runs. Engine use of marketfeed’s :cont composite landed through GLE-214’s engine rounds: a run names fut:V:R or fut:V:R:cont:adj=<method> (ER3, GLE-325); a deferred composite (ofs=B1..B3) runs or is declared since GLE-410, with one rank of a root taking orders until GLE-484, and a declared :cont series joins since GLE-392.
Contract curvesctx.Curve(root) (GLE-410) is backtest-only, costs one listing request per trade date, and assumes the store does not change during the run. Two ranks of one root that both take orders (GLE-484) roll with legs of their own, never netted, and nothing caps their combined exposure; a held attempt pinned to a contract a rank rolls out of is refused at the roll since GLE-491 (2026-10-11), so the guard’s book and the fill’s attribution agree; live, IBKR’s self-trade prevention against their opposite legs on one contract is unverified; a calendar spread on dated contracts is a combo order (GLE-409). ofs=F is refused on a run, because it renders as the plain composite. See Contract curves.
Combo ordersCombo orders (GLE-409) run only on a lifetime-v2 backtest on the pb wire: a v1 run denies every combo, a live run refuses one (the IBKR venue has no combo ticket yet), a run with a continuous series denies one (a roll has no rule for a combo), and the CSV strategy wire has no place for legs. Each leg is a dated futures contract; an equity or a continuous series cannot be a leg. The margin model has no spread credit, so --margin-model enforce is stricter than an exchange. A cancel placed between a combo’s legs’ bars waits for that instant (GLE-486). A combo of a kept spread’s two legs is priced at the exchange’s spread, ES’s only (GLE-487); any other combo fills at its legs’ own opens and closes. See Combo orders.
Continuous liveSince GLE-1385 8b a live run on the emulated venue trades a continuous series under lifetime v1, following the composite it fetched at start and rolling at the venue with two DAY market legs (Continuous futures in live mode). Since GLE-1447 the roll is a market roll in every live mode: the legs are flagged as roll legs and the venue fills them at its own price for each contract at the cut (the emulator at its marks); a continuous member runs against the desk on any of its clocks, and on the SIM clock it sends the desk each contract’s served price at the cut as a bar. Since GLE-1385 8c a restart adopts the book on the series’ contracts, and after a missed cut makes one catch-up roll before its first bar, its legs filling at market. Since GLE-1448 the emulator books futures at their point values, and a live run ends with its backtest’s equity. Since GLE-1446 the roll runs under lifetime v2 and with a trade director, with a ledger, on a venue fed from history (A live continuous roll under order lifetime v2), and since GLE-1503 on a real-time feed too, where --roll-rebase restates the v2 book at each roll and the director values levels in the held frame (Re-adjusting at each roll). Since GLE-1502 the roll rebase is on by default, in backtests and live runs alike (Turning the roll rebase off). Since GLE-1516 a live strategy receives its own account before each bar, as in a backtest. Open: director rules that read a mark (no live marks, GLE-548); a roll at a real venue (PAPER, GLE-1379), whose strategy is the demo rollhold (A demo for a roll at a real venue); a real-time feed, which needs causal publication of the current front’s schedule (O5, GLE-1440); populating broker/manifest reconciliation inputs and recovering partial rolls.
SessionsContinuous daily/weekly runs consume the feed’s session composites, and continuous intraday grids the feed’s grid composites (GLE-443); a utc-day grid bar straddling a roll executes its remainder from the cut in the incoming contract (GLE-444). GLE-524 built the strategy side of sessions in the kit, with no engine change: calendar and session keys, trade-date session flags and session resampling over the exchange calendar (Calendar and session keys), and a session’s prior session, window and last bar (Prior sessions and weeks on base bars), whose series form is nseries’s PriorPeriodLast family, pinned and cross-checked against the kit bit for bit. The engine serves the calendar from 14 days before the earliest bar, so a key that needs the year’s first session (tdy) needs about a year of warm-up; an option for a longer window is not built. A missing last bar defers the close’s exit to the next session’s first bar, and the intraday demos keep GTC orders right by cancel and resubmission, which a live strategy would leave to a Controller. Inside one bar, two same-kind members of an OCO group tie at bar resolution and the first submitted fills; --path-heuristic midpoint or a declared path (--path-interval 1m) resolves them, and no engine tie rule is built; a continuous symbol walks the path of the contract it holds, a bar containing a roll from the cut, and only a session composite that serves no path refuses it (continuous_path_unavailable, GLE-1332; Which level a bar reached first). The lbr-* grid strategies’ DayBook reads the calendar’s trade dates and early closes (Sessions=calendar, GLE-553). Arbitrary intraday hours/day filtering and partially derived year coverage remain open.
Equity adjustmentsBacktest price adjustment is the feed’s since GLE-328: the engine translates orders and fills by the served cumulative_price_ratio and keeps its own schedule for live mode only. The served law’s parity spec is marketfeed’s TestEqbParity (equity_boundary_parity_test.go), the port of adjuster_boundary_spec_test.go that lands with GLE-228’s close-out. Open: a “mixed-qualifier lineage” hint when two renames collide under one anchor after the re-key; reinvested-dividend execution and alternative merger cost-basis models. Factor-feed reconciliation is superseded (GLE-228 Decision 8). The raw projection divides a settle by the bar’s ratio over a copied BarSession; live mode’s AdjustBar keys by trade date. An adjusted bar whose raw view is unset or not finite refuses the run (raw_view_unset, raw_view_not_finite, GLE-546); a bar whose eight prices are all 0 is accepted.
Live modeReal-time feed/clock support and the broader reconciliation/CA surface described above.
Databento ruleOnly marketfeed talks to Databento (the owner’s rule of 20 Nov 2026, GLE-1790). The marketfeed adapter has no direct route since GLE-1793: no server list is live data off, and a databento entry is refused (The live source). No direct path remains in this repository. The IBKR adapter’s HTTP corporate-actions backend (DatabentoURL, DatabentoKey, DATABENTO_API_KEY) is removed (GLE-1795), keeping the recorded fixture for tests: marketfeed’s adapter serves corporate actions from the archive, and the IBKR adapter’s stream is empty without the fixture (The three bundled adapters). Free metadata calls count too (GLE-1791): marketfeed’s mf-cost prices a pull, and algodata cost is removed (GLE-1796; Pricing a Databento pull). With both gateways down a live run has no live data until one returns (GLE-1791); a third gateway may be added later, and is not planned.
Order lifetimeLifetime v2 is the backtest default (GLE-470); a live run stays on the legacy profile unless it names --lifetime v2, and the live default moves only when the live work resumes (recovery and ownership-aware shutdown, native OCA groups and brackets at the IBKR venue). A strategy that declares no lifetime-v2 support runs on a backtest only under --lifetime v1 (Lifecycle turns). At a roll on a continuous series no order the roll re-submits fills at the cut price under either profile, since GLE-575 for a market order or a stop the cut price is through and since GLE-627 for every order: its first chance is the first real incoming bar, and an OCO group moves whole (Parity with the legacy profile at a roll).
Trade stateGLE-524 built three strategy-side trade-state helpers in the kit, with no engine change: kit.BaseTrade, re-entries and a switched exit inside a base trade (Re-entries inside a base trade); kit.PendingEntry, a stop entry that waits for its fill (Pending stop entries and resting exits); and kit.LotBook, one lot per signal with its own exit (Overlapping per-signal trades). Each is per-process state. After a live restart BaseTrade’s first decision adopts an open position as the base trade, so a plain held trade is recovered, but a cut state or a trade held through the base’s flip is not; a pending stop entry is forgotten, and its venue Day order has expired by then; and the lot book is empty, so a strategy adopts an inherited position as one lot or flattens it. An entry fill that arrives after the next decision is refused by the book, so a live strategy should compare the book’s position with the account’s. The report pairs lots FIFO, so opposite or out-of-order overlapping per-signal trades are attributed per signal only in the book’s ledger: an opt-in report pairing by the client id’s lot tag is not built, and one account cannot hold opposite per-signal trades at once.
ReportingMultiple benchmark curves in CSV/HTML and non-primary statistics under a portfolio subset filter. A live run’s fills carry no order name: the IBKR venue does not echo it and the live ledger does not record it, so a live run’s trades show the default names (Naming orders, GLE-666).
CachingFreshness fingerprints, TTL/eviction, cross-process single-flight, an in-memory sharing layer and as-of build caching.
ExecutionExchange-auction semantics beyond current MOC, liquidation on a margin call, and general partial-fill/disconnect/unknown-submit fault simulation.
Research orchestrationParallel run execution, walk-forward scheduling/IS-OOS stitching, multiple-testing correction and portfolio allocation. Per-fold snapshot primitives and reporting already exist.
Trade directorA live run has no source yet for the drawdown rules’ external cash flows (GLE-543), for volume and open interest (GLE-545), for marks or for FX rates (GLE-548), so those rules refuse its openings or its configuration; an adopted working order cannot be cancelled through lifetime v2 (GLE-544); the live venue stamps no attempt on fills and cancels (GLE-549); shared accounts are GLE-360. Across a split the director values marks and equity in the post-split unit (GLE-572), but the history rules (max-var, the risk caps) still read pre-split closes at the split’s own breach check (Corporate actions and expiries). The paper-account conformance check is the release prerequisite (Status and limits).
Protocols and compositionJSONL, Unix-domain sockets, composite data-source routing, Trade Director/filter processes and AI integration tooling remain design proposals.

The original architecture also proposed typed filter chains with individual and batch decisions, global versus per-run scope, deterministic bar barriers, and an audit trail; failure-injection scripts; multi-source warmup/live handoffs; and AI lint/explain/MCP surfaces. Those are not shipped APIs. Detailed prior design rationale is recoverable from the historical architecture document using the commands in documentation history. The next implementation should refresh those designs against the current SDK and engine before treating old interface sketches as contracts.

Scaling opportunities

These estimates come from code inspection, not timed whole-run benchmarks. Profile a run with persistent brackets, a many-run portfolio, and a large multi-series run before quoting throughput gains.

  • OCO matching. The bar and tick loops call groupMembers once per active group, and the helper scans every working order (engine/sim/advance.go). With 1,000 two-leg groups, that is about 2 million group-membership checks per bar or print. A submission-ordered group index would reduce this component to about 2,000 checks, roughly 1,000 times fewer. Whole-run gain depends on how many groups rest and how much time the run spends in matching.
  • Portfolio memory. alignedRuns allocates three float columns and one flag column for every run at every union timestamp, and Combine retains them even when the HTML filter is disabled above 12 runs or output is sampled daily (engine/report/combine.go, engine/report/html.go). Twelve runs at one million timestamps need at least 300 MB for these columns alone, before slice spare capacity, input curves, and the joint curve. Stream the joint curve and retain only sampled columns needed by the filter. At 390 one-minute bars per trading day, daily sampling could shrink this column component about 390 times; total process memory would fall by less because other data remains.
  • Multi-series bar merge. mergeBars concatenates already sorted per-series streams and stable-sorts all bars (engine/backtest.go). A stable k-way merge that preserves series-order ties changes its bound from O(N log N) to O(N log S) for N bars and S series; two series permit a linear merge. Single-series runs already bypass sorting. Profile the merge phase before forecasting a whole-run saving: if it consumes 10% of elapsed time, even removing that cost entirely saves at most 10% of time.