Roadmap

This page is not a promise of exact delivery order. It is a practical map of what the project is trying to finish next and what is intentionally left out.

Near-term priorities

1. Tighten the runtime core

The runtime should stay easy to reason about under both historical and paper workflows.

That means continuing to improve:

• sequencing clarity
• result assembly
• diagnostics coverage
• determinism around feed and broker behavior

2. Strengthen the futures-first workflow

The project story is currently centered on futures.

That likely means more work around:

• futures paper-broker semantics
• realistic slippage and commission assumptions
• better examples that reflect actual usage
• cleaner risk-sizing helpers where they genuinely help

3. Improve developer-facing docs

The docs should become a real manual, not just a landing page and a few examples.

That includes:

• clearer conceptual guides
• better API-reference coverage
• stronger example walkthroughs
• practical guidance for config-first experiment runs

Mid-term priorities

More provider and broker adapters

The core should stay vendor-neutral, but the project becomes more useful as adapters become more practical.

Better experiment workflow

The config-first CLI path is intentionally small now. It will likely need better ergonomics over time, but only if it stays readable and doesn’t turn into a framework of its own.

Broader asset support

The internal model is asset-aware, but the practical release story is still futures-first. Broader support should only expand once the core remains understandable.

Explicitly not the current goal

FBTF is not currently trying to become:

• a real-money execution platform
• a giant multi-market portfolio system
• a tick simulator
• a cloud product
• an everything-included quant platform

The project is better when it stays smaller and more explicit.