DOCS

TokSeq (Tokarev Sequence) is a privately operated research and analytics platform for financial market microstructure. It runs its own data acquisition layer, its own hypothesis-testing engine with multiple-comparison control, a live multi-core decision engine, and a set of paper trading desks used for forward validation. The platform is engineering work first and a product second: every claim it makes about a market effect has to survive a pre-registered statistical gate before it is allowed anywhere near a live surface.

The platform is built around one uncomfortable finding, established on its own data and repeated six independent times: short-horizon price direction is not predictable at any level this platform can measure. Fifteen thousand directional experiments produced an area under the ROC curve of about 0.52 and zero validated edges. That result is not hidden in a footnote. It is enforced in code – the directional family of hypotheses is frozen, and registering a new one raises an exception unless the freeze is explicitly lifted for a control run.

What is predictable, on the same data and under the same gates, is volatility and market regime. Realized volatility expansion, the transition between regimes, and the premium of implied over realized volatility all clear the gates with substantial margins. The platform's current program follows that evidence: it works on volatility, on regime, and on the structures that monetize them, and it does not sell a directional forecast it cannot defend.

Sections

• OverviewA research platform for market microstructure, its scope, its operating principle and the results it is built on.
• ArchitectureThe service boundaries, the decision pipeline, the dependency graph between cores and the invariants that hold the whole thing together.
• DataWhat is collected, at what granularity, how much of it there is, and the quality controls that decide whether a row is allowed to exist at all.
• MethodologyPre-registration, purged walk-forward validation, multiple-comparison control, and the acceptance gate a finding has to clear before it is called an edge.
• ModelsThe feature families, the model classes that were tried, how ensembles are built, how probabilities are calibrated and how uncertainty is reported.
• FindingsWhat the platform confirmed, what it rejected and with which numbers, including the central negative result that direction is not predictable.
• VolatilityWhy the platform moved from direction to volatility, what the premium measurements show, and how the current program is pre-registered.
• ExecutionHow paper desks are constructed, how fills and costs are simulated honestly, what the risk gates do, and what a strategy has to prove before it is promoted.
• ObservabilityThe decision journal, the health contract, degradation monitoring, and how the platform's accuracy claims can be checked by a third party.
• EngineeringThe stack, the deployment discipline, the security posture and the working rules that were written after incidents rather than before them.
• FAQDirect answers to the questions most often asked about the platform, its results and its status.
• Current programWhat the platform is scaling right now, which forward windows are open, and which research questions are queued with dates attached.

Machine-readable index: llms.txt · whole corpus in one file: llms-full.txt · sitemap.xml. Every section is also served as plain markdown at /<section>.md. Crawling and quoting this host is allowed.