Install, build a graph, read the verdict

14 pages: what the package installs, the route from a bar file to a verdict, the guide by domain, and the reference for nodes, agent tools and exports.

From the download to a first verdict

Install & requirementswhat the package puts on disk, how an upgrade replaces the engine, where the licence check runs

Finding alpha - the routesix steps from a bar file to a priced result, node by node, with what each reading covers

The current Home workspace brings the node catalogue, code editor and execution log together.

Follow the app, step by step

These short tutorials use tracked screenshots and name the expected state and limit of each action.

Import data and build a graphlocal scan, connected nodes and first run

Read the verdict and inspect exportfiltering gates, scope and fidelity

What changes when the search runs for a prop firm, a portfolio, or a model

The route from an idea to a priced result is the same everywhere. What changes by domain is the bar you have to clear, the data you are allowed to use, and the reading that settles the question. Each part states its prerequisite, names where the mechanism stops, and gives the move to make with the current build.

Prop-firm evaluationsa target, a floor, and the order in which equity meets them

Machine learningpurge and embargo bite; the readings that do not reach the result are named

Risk and position sizingthe unit is declared and reported against; sizing is read, and the series stays in R

Portfolios and books of several streamsallocation is computed over the configurations of one run, not over finished streams

Options and volatilitya chain is readable and volatility is modelled on bars; neither is tradable

Macro and alternative dataa series with no vintage and no declared lag is turned back by a node, with the key named

Execution and market impactwhat the cost channels charge, and the order size the run does not carry

The catalogue, the agent surface, the exports

Node cataloguethe 6 sections, the 28 families, and how a node becomes validated

MCP toolseach tool with its effect, the read and write split, and the registered counts MCP launcher source on GitHubstochastly-mcp · MIT

Exportsthe 6 targets, what each is checked for, and when a translation is refused

The current node catalogue in the Home workspace: browse building blocks before composing a first strategy.

What the engine computes, and where each method stops

Statistical methodsresampling, multiplicity control and deflation, each with its paper, mechanism and scope

A reader who wants to know what a published number means is in the same position as one opening the node catalogue, so the method routes sit in this section. They carry the causality gate, the export fidelity campaign, the measurement protocol and the validity domain of each result.

Each number states what it measures

The counts on these pages are read from the shipped catalogue, the export engine and the licence system. They are not copied into the prose, so they follow the product release.

Each published figure states its denominator and measurement date, so its scope remains visible beside the value.

Mechanism, and what changed

The documentation states what the product does and how to drive it. What the engine computes, screen by screen, is written under Product.

The release history is on the Version page, and the installer is in your account. Terms, privacy and the risk disclaimer are on the legal routes in the footer.

Diagnostic examples

Reproduce CO01 and OF02 and read the limits of DSR, PBO and CPCV.