Skip to main content
Contents
12 min read

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:

CODE
workflow + subject/version + data shape + asset + provider/environment
  + topology + fidelity + method + evidence depth + runtime dependencies
  + platform + retained certification + current operating state

This 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.

FieldValueMeaning
MaturityCompleteThe owning implementation is complete for its declared scope; release and fixture gates can still apply
MaturityFunctionalA meaningful implementation exists, but one or more workflow, contract, evidence, or polish gaps remain
MaturityScaffoldedA foundation or partial shell exists; the end-to-end public workflow is not complete
MaturityPlannedThe production owner is absent or materially incomplete; do not describe the workflow as usable
AvailabilityBetaExposed for the declared scope with explicit limitations; not equivalent to Stable or fully certified
AvailabilityInternalNot 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

CapabilityMaturity / availabilityDeclared matrixImportant current boundary
Local importComplete / BetaSCID, CSV, Parquet, Databento, Massive, CME DataMine, Custom; registry includes Windows/macOS/Linux runtime matricesPublic packaged releases are still Windows x64/macOS arm64 targets; format support remains mapping/schema-specific
Dataset lifecycleComplete / BetaInstrument, Bar, Trade, Quote, OrderBookEventActivation, supersede and retire apply to immutable Dataset versions; they do not rewrite source history
Prepared build/reuseComplete / BetaPreparedBars, PreparedArrays, VolumetricSummary/Arrays, TickReplayData, DepthReplayData, PreparedFootprintLevels, FeatureOutput, SignalOutputExact requirement planning decides reuse/build; a listed kind is not proof every source route is certified
Prepared retentionComplete / BetaEvictable and pinnedPinning affects retention, not functional identity or downstream readiness
Event-fidelity Prepared layersPlanned / InternalBars through depth replay plus feature/signal outputs and planned L1/depth-as-L1 rolesL1 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

ProviderMaturity / availabilityDeclared assetsDeclared canonical schemasProduction status
DatabentoFunctional / InternalEquities, futuresInstrument, Bar, Trade, Quote, OrderBookEventBlocked on current real-account certification for the exact registration and advertised matrix
Alpaca historical dataFunctional / InternalEquities, crypto spotInstrument, Bar, Trade, QuoteBlocked on current real-account certification for every advertised context
Hyperliquid archive/capturePlanned / InternalNone certifiedNone certifiedProvider bundle, capture service, mappings, assurance and account certification absent
Interactive Brokers historyPlanned / InternalIntended equities/futures barsNone certifiedGateway/session/rate-budget ownership, canonical factors/timestamps, legal distribution and connected proof unresolved
Charles Schwab historyPlanned / InternalIntended U.S. equities/ETFs barsNone certifiedEligible product/terms/specification, browser authorization lifecycle, provider bundle, mappings and assurance absent
Rithmic historyPlanned / InternalIntended exchange-listed futuresNone certifiedProduct/license/API/entitlement matrix, exact event semantics, implementation, Rithmic Test and production certification absent
Binance Spot historyPlanned / InternalIntended spot Instruments, bars, individual tradesNone certifiedLegal 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

CapabilityMaturity / availabilityDeclared matrixBoundary
Signal LibraryFunctional / BetaBundled and operator SignalsNative code authoring/runtime lowering and exact derived-history ownership remain open; runtime readiness is per Signal/version
Strategy ComposerComplete / BetaComposer authoringSave/validation/compile/readiness are distinct; Composer does not own Study data or evidence
Python Strategy pluginsFunctional / InternalTrusted local PythonSingle-source definitions, native compile/run admission, symmetric scaffolds/checks, certification and no-fallback proof remain open
Library packagesFunctional / InternalCurrent Composer Strategy IR and Signal Program v1 payloadsProduction 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

CapabilityMaturity / availabilityDeclared matrixBoundary
Portfolio authoringComplete / BetaPortfolio IR V4Current UI still has an additional-new-Portfolio action gap when a Portfolio is selected
Portfolio StudiesFunctional / BetaGrid, Random, categorical Optuna; current public execution is coordinated BarCandidate/evidence UI and shared grammar continue to have declared gaps; request validation is authoritative
Portfolio execution fidelity expansionPlanned / InternalTarget Vector, Bar, Tick, L1, L2 MBP, L3 MBO across Run/Optimization, Standard/Walk-forward, Summary/RobustCurrent request/result/UI/runtime are Bar and research_bar_conservative; no fidelity-neutral multi-source Portfolio session exists
Portfolio Live deploymentPlanned / InternalNoneportfolio_live_runtime_not_implemented

Strategy Study and Result capabilities

CapabilityMaturity / availabilityDeclared matrixBoundary
Strategy researchFunctional / BetaGrid, Random, Optuna, Vector Surface for Strategy subjectsExact supported topology/fidelity/evidence matrix comes from validation; Full Suite remains unavailable and Summary/Robust closure is still declared
Study Result reviewFunctional / BetaStrategy and Portfolio subjectsShared shell, race-safe subject selection, complete Portfolio evidence and final two-depth contract remain open
Run Output reviewFunctional / BetaStrategy and Portfolio subjectsExact Parameters reuse and complete approved Summary/Robust evidence remain open
Execution validationComplete / InternalVector, Bar, Tick, selected event/depthCurrent public retained-candidate action is Bar validation; do not infer every listed fidelity is exposed as a complete UI promotion path
L3 Depth Strategy executionPlanned / InternalIntended Solo, Grid, Random, Optuna, selected-trial validation; Summary/RobustPrepared MBO handoff, queue model, reducer, candidate-local liquidity/queue state, forward-only results and real-data proof absent
Complete Optuna execution matrixPlanned / InternalTarget Vector through L3, Standard/Walk-forward, allowed single-objective prunersIncremental comparable pruning protocol, event walk-forward/pruning, optional-host certification and Portfolio semantics remain incomplete

Study family summary

Family/methodCurrent public interpretation
Solo RunOne fixed Strategy candidate under an exact validated execution cell
Grid MatrixExhaustive deduplicated finite domain for a supported topology/fidelity
Random MatrixSeeded unique subset of the same explicit domain
OptunaProtocol-specific adaptive search; sampler, objective count, pruner, walk-forward, fidelity and resume support must all pass validation
Portfolio RunOne coordinated Bar Portfolio candidate
Portfolio OptimizationExplicit 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 / workflowMaturity / availabilityDeclared environment and subjectCurrent production boundary
Arizmic Local PaperFunctional / Betaarizmic_paper, StrategyCapability 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 brokerFunctional / InternalAlpaca Paper, Paper, StrategyComplete current Paper certification pack and enforcement in Arm/Resume required
Interactive Brokers market dataPlanned / InternalNone certifiedGateway/startup/feed identity, process lease, pacing/history budget, factor/bar semantics, legal route and connected certification absent
Interactive Brokers brokerPlanned / InternalIntended Paper and realShared auth/operational-state/message-action/idempotency contracts and lawful certified route absent
Schwab market dataPlanned / InternalNone certifiedEligible product/spec/terms, browser authorization lifecycle, provider-neutral feed/cursor, composition and certification absent
Schwab brokerPlanned / InternalIntended realAccount/order/automation eligibility, OAuth owner, thinkorswim coexistence/external-order ownership, reconciliation and real certification absent; paperMoney is not proven Schwab API Paper
Rithmic market dataPlanned / InternalNone certifiedProduct/license/API/FCM matrix, shared provider-neutral contracts, exact feed/gap semantics and external certification absent
Rithmic brokerPlanned / InternalIntended Test, Paper and real FCMCommand/identity/ambiguity/snapshot/stream/restart/risk/kill owners and external certifications absent
Binance Spot market dataPlanned / InternalIntended trades and top-of-bookLegal/entity/feed matrix, provider-neutral decimal/feed contracts, implementation and certification absent
Binance Spot brokerPlanned / InternalIntended sandbox and realProduct/account terms, decimal/fee/valuation shared contracts, signing/rate/filter/user-stream/reconciliation and certification absent
Hyperliquid real brokerPlanned / InternalNone certifiedShared crypto contracts, provider implementation, testnet drills, composed runtime and separately authorized mainnet certification absent
Portfolio deploymentPlanned / InternalNoneRuntime 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

ModeCurrent supported useRequired proofDoes not prove
ShadowSingle-input Strategy managed evaluation without broker submissionExact Configuration, runtime input, sizing/risk, current readiness and journal evidenceBroker acceptance, fills, account or reconciliation
Local PaperIntended internal Strategy rehearsalComplete composed local feed/session/Instrument/fill path and lifecycle fixturesExternal provider compatibility or real fills
Provider PaperSelected exact provider Paper matrix after certificationCurrent evidence pack enforced in actions, account/Instrument/session/risk/reconciliationReal-money behavior, liquidity, queue position or unsupported order types
LiveFuture exact real-provider matrix onlySeparate provider/environment/account/Instrument/order/recovery certification and operator authorizationAny provider or feature outside the certified matrix

AI and Notebook capabilities

CapabilityMaturity / availabilityDeclared matrixBoundary
Contextual AI assistantFunctional / BetaOpenAI-compatible, Anthropic, Google and local provider routesCurrent global dock sends prompt plus page orientation; durable conversations and dedicated workspace are incomplete; selected Results/Notebooks are not attached
AI actions and receiptsPlanned / InternalNoneTyped mutation permission and immutable action receipts are not implemented; current Companion is read-only advice
Marimo workspaceScaffolded / InternalMarimo, AI-namespaced scaffold ownershipFlat files/processes exist, but project ownership, environment, manifest/lock, recovery and complete product workflow are incomplete
Notebook research SDKPlanned / InternalNoneIndependent SDK/permission boundary is absent; current generated client is a limited GET scaffold and canonical sandbox import is broken

Operations, UI, and release capabilities

CapabilityMaturity / availabilityDeclared matrixBoundary
Durable JobsComplete / BetaLocal worker processResume/retry behavior remains runner-specific; terminal publication identity must be verified
Workstation shellComplete / BetaMinimum 1024 px; day/night; design-system density variantsProduction app uses compact density and exposes no global density selector
Accessibility v1Functional / Beta1024+ px, day/night, default/override color-vision tokensRetained WCAG 2.2 AA workflow matrix is incomplete
Versioned navigation settingsPlanned / InternalNoneCurrent layout/route memory is local presentation state, not versioned navigation configuration
SnapTrade Commercial connected accountsPlanned / InternalNoneCommercial/entitlement/hosted-secret/read-only institution/lifecycle/offboarding/billing/certification absent
Windows x64 releasePlanned / InternalNone certifiedInstaller, signing, clean-host lifecycle, SBOM and provenance evidence absent
macOS arm64 releasePlanned / InternalNone certifiedPackaging, signing, hardened runtime, notarization and clean-host evidence absent
Linux portabilityFunctional / InternalUbuntu source-development portabilityNot a Stable packaged target

How to decide whether a request is usable

  1. Open the owning surface and select the exact object/version.
  2. Read the capability's maturity and availability; Internal or Planned is a stop for public production use.
  3. Match every requested dimension to the declared supported matrix.
  4. Run the request-specific validation/readiness/estimate.
  5. Resolve data, Prepared, dependency, credential, entitlement, account, Instrument, provider, evidence and resource blockers at their owners.
  6. Confirm no silent downgrade or fallback changed fidelity, method, evidence, source ownership, provider or environment.
  7. Queue/execute only if the exact normalized request is supported.
  8. 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, and Compatible are scoped to the exact response.
  • Blocked, Unknown, Proof required, and unavailable evidence fail closed.
  • Limited or 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.

CODE
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 evidence

The 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.