Programs

A theme's runnable implementation in one style — the preset a book is minted from.

When a desk decides to actually run a story, it writes the machinery down: which method, which markets, what rules, what size it's built for. That runnable form is the program — one theme can carry several, same story, different machinery.

In Quantreno a program binds one theme to one style: the exact rules the computer follows per market, the "Can run in" coverage, and the sizes it's built for. Its availability chip says what stands between you and a run — running, book can open, needs a connection, live mode only, or roadmap — and the first two name the workspace mode they speak for ("book can open · paper").

Pick a program and mint it: you get your own book — your copy of the machinery, born bare: the desk's view stays in the theme's brief until an adoption puts a thesis on the book. Programs are presets, not personal advice: nothing trades without your review.

An event program works one level down. Add a program… puts your own program in your forecast book, the one book that holds every event program's positions. Your program keeps its own settings, theses and research; the book sizes all its programs' lines together, and each lot names the program behind it.

The words on this page

Catalog program: A theme's runnable implementation in one style, which a book or a program copies. A preset, not personal advice.; One way the desk runs a theme: a single style, its exact rules per market, and the sizes it's built for. A theme can carry several catalog programs — same story, different machinery — and each keeps its own "Can run in" coverage and availability chip. Opening a book from a catalog program creates your own book. A catalog program of the event-driven style opens no book: Add a program… puts your own program in your forecast book.
Expression: The market a run chooses when it carries a program into an act — recorded where it's real: legs, orders, positions.; Desk vocabulary, mostly backstage: the market/instrument choice a run (or the agent) makes when pressing a program — never pre-bound on the program or the book. In the app it appears as derived facts: "Can run in" coverage chips, "expressed in" on a book, and run outcomes naming what they scanned.
Forecast book: Your one book of event forecasts: the event programs you add sit inside it, and it holds their positions.; Each mandate has one forecast book, created with the mandate. Every event program you add sits inside it, and no event program opens a book of its own. The book holds the positions, the orders, the trades and the record; each program holds its settings, its theses and its research. One position stands for each contract and side, and each lot names the program and the method version behind it. One solve sizes every program's lines together, and the book's page states the forecast strategy's version and its release date. With no program yet, the book trades nothing.
Program: An event program you added to the forecast book: its settings, theses and research. The book holds its positions.; Your own instance of a catalog program of the event-driven style, added to the forecast book with Add a program…. It holds its settings, its caps, its theses, its research and its standing, and no capital or position of its own. Pause stops its new lines and cancels no order; its lots stay in the book and count against every cap. Close its lots… sells that program's lots alone, and another program's lots on the same contract stay. Remove from the forecast book… waits until no lot, working order or order in unknown venue state names the program; a removed program does not come back, and its records stay. Two programs can come from one catalog program.