Reference
Capability, provider, and broker matrix
Look up maturity and availability across core workflows, historical providers, Study/runtime paths, AI, Notebooks, package targets, and exact Paper/real broker matrices.
App path
- Owning workflow -> exact capability or readiness response
- Docs -> Reference -> Capability, provider, and broker matrix
Read capability as an exact request contract
Capability is never inferred from a page title, installed package, provider logo, saved object, or enabled-looking control. It is the intersection of:
workflow + subject/version + data shape + asset + provider/environment
+ topology + fidelity + method + evidence depth + runtime dependencies
+ platform + retained certification + current operating stateThis page summarizes the public capability registry at application revision
595c7b494a533df6a49d5387538d6f10a430474e. The request-specific readiness or
capability response in the owning surface remains authoritative for a concrete
operation.
Status vocabulary
The registry separates maturity from availability.
| Field | Value | Meaning |
|---|---|---|
| Maturity | Complete | The owning implementation is complete for its declared scope; release and fixture gates can still apply |
| Maturity | Functional | A meaningful implementation exists, but one or more workflow, contract, evidence, or polish gaps remain |
| Maturity | Scaffolded | A foundation or partial shell exists; the end-to-end public workflow is not complete |
| Maturity | Planned | The production owner is absent or materially incomplete; do not describe the workflow as usable |
| Availability | Beta | Exposed for the declared scope with explicit limitations; not equivalent to Stable or fully certified |
| Availability | Internal | Not a public production capability, even if source or UI scaffolding exists |
Request-level surfaces can also say Supported/Compatible, Blocked, Unknown, Experimental, Proof required, Limited, or Unavailable. A missing or unknown capability must fail closed. A narrower effective result keeps its narrower label.
Core data and Prepared capabilities
| Capability | Maturity / availability | Declared matrix | Important current boundary |
|---|---|---|---|
| Local import | Complete / Beta | SCID, CSV, Parquet, Databento, Massive, CME DataMine, Custom; registry includes Windows/macOS/Linux runtime matrices | Public packaged releases are still Windows x64/macOS arm64 targets; format support remains mapping/schema-specific |
| Dataset lifecycle | Complete / Beta | Instrument, Bar, Trade, Quote, OrderBookEvent | Activation, supersede and retire apply to immutable Dataset versions; they do not rewrite source history |
| Prepared build/reuse | Complete / Beta | PreparedBars, PreparedArrays, VolumetricSummary/Arrays, TickReplayData, DepthReplayData, PreparedFootprintLevels, FeatureOutput, SignalOutput | Exact requirement planning decides reuse/build; a listed kind is not proof every source route is certified |
| Prepared retention | Complete / Beta | Evictable and pinned | Pinning affects retention, not functional identity or downstream readiness |
| Event-fidelity Prepared layers | Planned / Internal | Bars through depth replay plus feature/signal outputs and planned L1/depth-as-L1 roles | L1 replay contract, state anchors, action-aware fold, forward-only Tick cutover, bounded storage and purchased-data certification remain open |
The local-import registry's Linux entry describes core/runtime portability; it does not override the release registry, which says Linux is source-development portability rather than a Stable packaged target.
Historical provider-import matrix
| Provider | Maturity / availability | Declared assets | Declared canonical schemas | Production status |
|---|---|---|---|---|
| Databento | Functional / Internal | Equities, futures | Instrument, Bar, Trade, Quote, OrderBookEvent | Blocked on current real-account certification for the exact registration and advertised matrix |
| Alpaca historical data | Functional / Internal | Equities, crypto spot | Instrument, Bar, Trade, Quote | Blocked on current real-account certification for every advertised context |
| Hyperliquid archive/capture | Planned / Internal | None certified | None certified | Provider bundle, capture service, mappings, assurance and account certification absent |
| Interactive Brokers history | Planned / Internal | Intended equities/futures bars | None certified | Gateway/session/rate-budget ownership, canonical factors/timestamps, legal distribution and connected proof unresolved |
| Charles Schwab history | Planned / Internal | Intended U.S. equities/ETFs bars | None certified | Eligible product/terms/specification, browser authorization lifecycle, provider bundle, mappings and assurance absent |
| Rithmic history | Planned / Internal | Intended exchange-listed futures | None certified | Product/license/API/entitlement matrix, exact event semantics, implementation, Rithmic Test and production certification absent |
| Binance Spot history | Planned / Internal | Intended spot Instruments, bars, individual trades | None certified | Legal entity/terms, bundle, catalog/acquisition/canonicalization and source-tail certification absent |
Provider Import is separate from broker support. A provider may supply history without market-data streaming or order routing. Conversely, a broker definition does not create an approved historical archive workflow.
For each request, additionally verify provider mode, entitlement, Instrument, schema, window, adjustment/correction policy, request/byte estimate, raw-evidence retention, canonical mapping, assurance state, and credential generation.
Signals, Strategies, and Library capabilities
| Capability | Maturity / availability | Declared matrix | Boundary |
|---|---|---|---|
| Signal Library | Functional / Beta | Bundled and operator Signals | Native code authoring/runtime lowering and exact derived-history ownership remain open; runtime readiness is per Signal/version |
| Strategy Composer | Complete / Beta | Composer authoring | Save/validation/compile/readiness are distinct; Composer does not own Study data or evidence |
| Python Strategy plugins | Functional / Internal | Trusted local Python | Single-source definitions, native compile/run admission, symmetric scaffolds/checks, certification and no-fallback proof remain open |
| Library packages | Functional / Internal | Current Composer Strategy IR and Signal Program v1 payloads | Production requires library_package_v2, exact closure/source/conflicts, atomic install, Portfolio/configuration roots and sync |
An Internal plugin or package path must not be described as a general extension marketplace or safe portable exchange.
Portfolio capabilities
| Capability | Maturity / availability | Declared matrix | Boundary |
|---|---|---|---|
| Portfolio authoring | Complete / Beta | Portfolio IR V4 | Current UI still has an additional-new-Portfolio action gap when a Portfolio is selected |
| Portfolio Studies | Functional / Beta | Grid, Random, categorical Optuna; current public execution is coordinated Bar | Candidate/evidence UI and shared grammar continue to have declared gaps; request validation is authoritative |
| Portfolio execution fidelity expansion | Planned / Internal | Target Vector, Bar, Tick, L1, L2 MBP, L3 MBO across Run/Optimization, Standard/Walk-forward, Summary/Robust | Current request/result/UI/runtime are Bar and research_bar_conservative; no fidelity-neutral multi-source Portfolio session exists |
| Portfolio Live deployment | Planned / Internal | None | portfolio_live_runtime_not_implemented |
Strategy Study and Result capabilities
| Capability | Maturity / availability | Declared matrix | Boundary |
|---|---|---|---|
| Strategy research | Functional / Beta | Grid, Random, Optuna, Vector Surface for Strategy subjects | Exact supported topology/fidelity/evidence matrix comes from validation; Full Suite remains unavailable and Summary/Robust closure is still declared |
| Study Result review | Functional / Beta | Strategy and Portfolio subjects | Shared shell, race-safe subject selection, complete Portfolio evidence and final two-depth contract remain open |
| Run Output review | Functional / Beta | Strategy and Portfolio subjects | Exact Parameters reuse and complete approved Summary/Robust evidence remain open |
| Execution validation | Complete / Internal | Vector, Bar, Tick, selected event/depth | Current public retained-candidate action is Bar validation; do not infer every listed fidelity is exposed as a complete UI promotion path |
| L3 Depth Strategy execution | Planned / Internal | Intended Solo, Grid, Random, Optuna, selected-trial validation; Summary/Robust | Prepared MBO handoff, queue model, reducer, candidate-local liquidity/queue state, forward-only results and real-data proof absent |
| Complete Optuna execution matrix | Planned / Internal | Target Vector through L3, Standard/Walk-forward, allowed single-objective pruners | Incremental comparable pruning protocol, event walk-forward/pruning, optional-host certification and Portfolio semantics remain incomplete |
Study family summary
| Family/method | Current public interpretation |
|---|---|
| Solo Run | One fixed Strategy candidate under an exact validated execution cell |
| Grid Matrix | Exhaustive deduplicated finite domain for a supported topology/fidelity |
| Random Matrix | Seeded unique subset of the same explicit domain |
| Optuna | Protocol-specific adaptive search; sampler, objective count, pruner, walk-forward, fidelity and resume support must all pass validation |
| Portfolio Run | One coordinated Bar Portfolio candidate |
| Portfolio Optimization | Explicit discrete Bar candidate domain using Grid, Random, or current categorical Optuna behavior |
Vector discovery does not become execution evidence because it has trades or metrics. Bar/Tick/Quote/Depth cells require their own supported runtime and data contracts. Evidence Depth and Chart Output are separate axes.
Live provider and broker matrix
| Provider / workflow | Maturity / availability | Declared environment and subject | Current production boundary |
|---|---|---|---|
| Arizmic Local Paper | Functional / Beta | arizmic_paper, Strategy | Capability registry lists Strategy support, but default composition lacks Sandbox runtime market data/session/Instrument directory and transport fills; current safe rehearsal is Shadow |
| Alpaca Paper broker | Functional / Internal | Alpaca Paper, Paper, Strategy | Complete current Paper certification pack and enforcement in Arm/Resume required |
| Interactive Brokers market data | Planned / Internal | None certified | Gateway/startup/feed identity, process lease, pacing/history budget, factor/bar semantics, legal route and connected certification absent |
| Interactive Brokers broker | Planned / Internal | Intended Paper and real | Shared auth/operational-state/message-action/idempotency contracts and lawful certified route absent |
| Schwab market data | Planned / Internal | None certified | Eligible product/spec/terms, browser authorization lifecycle, provider-neutral feed/cursor, composition and certification absent |
| Schwab broker | Planned / Internal | Intended real | Account/order/automation eligibility, OAuth owner, thinkorswim coexistence/external-order ownership, reconciliation and real certification absent; paperMoney is not proven Schwab API Paper |
| Rithmic market data | Planned / Internal | None certified | Product/license/API/FCM matrix, shared provider-neutral contracts, exact feed/gap semantics and external certification absent |
| Rithmic broker | Planned / Internal | Intended Test, Paper and real FCM | Command/identity/ambiguity/snapshot/stream/restart/risk/kill owners and external certifications absent |
| Binance Spot market data | Planned / Internal | Intended trades and top-of-book | Legal/entity/feed matrix, provider-neutral decimal/feed contracts, implementation and certification absent |
| Binance Spot broker | Planned / Internal | Intended sandbox and real | Product/account terms, decimal/fee/valuation shared contracts, signing/rate/filter/user-stream/reconciliation and certification absent |
| Hyperliquid real broker | Planned / Internal | None certified | Shared crypto contracts, provider implementation, testnet drills, composed runtime and separately authorized mainnet certification absent |
| Portfolio deployment | Planned / Internal | None | Runtime not implemented |
No built-in real-money provider is currently selected and certified. The generic Live mode is therefore unavailable for real capital. Provider definition, adapter composition, connection, account discovery, Instrument binding, evidence pack and current operator readiness are separate gates.
Live mode matrix
| Mode | Current supported use | Required proof | Does not prove |
|---|---|---|---|
| Shadow | Single-input Strategy managed evaluation without broker submission | Exact Configuration, runtime input, sizing/risk, current readiness and journal evidence | Broker acceptance, fills, account or reconciliation |
| Local Paper | Intended internal Strategy rehearsal | Complete composed local feed/session/Instrument/fill path and lifecycle fixtures | External provider compatibility or real fills |
| Provider Paper | Selected exact provider Paper matrix after certification | Current evidence pack enforced in actions, account/Instrument/session/risk/reconciliation | Real-money behavior, liquidity, queue position or unsupported order types |
| Live | Future exact real-provider matrix only | Separate provider/environment/account/Instrument/order/recovery certification and operator authorization | Any provider or feature outside the certified matrix |
AI and Notebook capabilities
| Capability | Maturity / availability | Declared matrix | Boundary |
|---|---|---|---|
| Contextual AI assistant | Functional / Beta | OpenAI-compatible, Anthropic, Google and local provider routes | Current global dock sends prompt plus page orientation; durable conversations and dedicated workspace are incomplete; selected Results/Notebooks are not attached |
| AI actions and receipts | Planned / Internal | None | Typed mutation permission and immutable action receipts are not implemented; current Companion is read-only advice |
| Marimo workspace | Scaffolded / Internal | Marimo, AI-namespaced scaffold ownership | Flat files/processes exist, but project ownership, environment, manifest/lock, recovery and complete product workflow are incomplete |
| Notebook research SDK | Planned / Internal | None | Independent SDK/permission boundary is absent; current generated client is a limited GET scaffold and canonical sandbox import is broken |
Operations, UI, and release capabilities
| Capability | Maturity / availability | Declared matrix | Boundary |
|---|---|---|---|
| Durable Jobs | Complete / Beta | Local worker process | Resume/retry behavior remains runner-specific; terminal publication identity must be verified |
| Workstation shell | Complete / Beta | Minimum 1024 px; day/night; design-system density variants | Production app uses compact density and exposes no global density selector |
| Accessibility v1 | Functional / Beta | 1024+ px, day/night, default/override color-vision tokens | Retained WCAG 2.2 AA workflow matrix is incomplete |
| Versioned navigation settings | Planned / Internal | None | Current layout/route memory is local presentation state, not versioned navigation configuration |
| SnapTrade Commercial connected accounts | Planned / Internal | None | Commercial/entitlement/hosted-secret/read-only institution/lifecycle/offboarding/billing/certification absent |
| Windows x64 release | Planned / Internal | None certified | Installer, signing, clean-host lifecycle, SBOM and provenance evidence absent |
| macOS arm64 release | Planned / Internal | None certified | Packaging, signing, hardened runtime, notarization and clean-host evidence absent |
| Linux portability | Functional / Internal | Ubuntu source-development portability | Not a Stable packaged target |
How to decide whether a request is usable
- Open the owning surface and select the exact object/version.
- Read the capability's maturity and availability; Internal or Planned is a stop for public production use.
- Match every requested dimension to the declared supported matrix.
- Run the request-specific validation/readiness/estimate.
- Resolve data, Prepared, dependency, credential, entitlement, account, Instrument, provider, evidence and resource blockers at their owners.
- Confirm no silent downgrade or fallback changed fidelity, method, evidence, source ownership, provider or environment.
- Queue/execute only if the exact normalized request is supported.
- In the Result or operation receipt, compare requested versus actual/effective capability and retain limitations.
If the registry summary and current owner response disagree, stop and preserve both identities. A stale snapshot, changed application revision, incomplete composition, or contract regression must be resolved before use.
Claim rules
- Beta is not Stable, certified, or generally available.
- Internal is not public production availability.
- A non-empty supported matrix does not erase its blockers.
- A capability ID does not prove the current UI exposes every backend path.
- Installed optional code does not make an unsupported cell valid.
- A connection test is not provider certification.
- Provider Paper evidence does not transfer to real operation.
Available,Supported, andCompatibleare scoped to the exact response.Blocked,Unknown,Proof required, and unavailable evidence fail closed.Limitedor discovery evidence keeps that label in public wording.- Reproducible, out-of-sample, compiled, no-look-ahead, same-fidelity, certified, and Live-ready claims require their named retained artifacts and scope.
Technical source of truth
The public surface snapshot records each capability ID, domain, workflow, release relevance, maturity, availability, supported matrices, and blockers. Documentation metadata references those IDs. Concrete owners then produce more specific compatibility/readiness responses for the selected request.
revisioned capability registry
-> page exposes eligible choices
-> exact owner validation resolves request and dependencies
-> queue/action revalidates current state
-> Result/receipt records effective capability and evidenceThe snapshot must be regenerated and reviewed with the application revision. Documentation must not freeze a changing provider matrix as timeless prose.
Next
Use Validation for request-specific capability and evidence checks, and Deployments for Live readiness and provider gates.