Market engineering and research · Oxarus Quant Oxarus Quant builds L.I.T., a market terminal, alongside custom trading robots, published research and institutional market infrastructure. Breadcrumbs: Oxarus home › Oxarus Quant NOTICES - Interface data marked as representative is illustrative; it is not a real client, result or measurement. - Not investment advice. Trading in financial markets carries a risk of losing capital. SECTIONS - engineering for markets. - four areas, one discipline. - each area feeds the others. - we have skin in the game. - let's talk markets. ENGINEERING FOR MARKETS. OXARUS QUANT We build systems that run on our own capital. We also build the tools, research and infrastructure behind them for clients. https://oxarus.com/en/quant - Get in touch → open_page(path="/quant", anchor="cta-heading") - What we do → open_page(path="/quant", anchor="areas") - Measure first, then decide - Publish the ideas that fail, too - Build the halt controls from day one 1. Terminal 2. Robots 3. Research 4. Engineering - L.I.T. - Custom robots - Research - Engineering Representative screen. Not investment advice. Interface labels: Explore FOUR AREAS, ONE DISCIPLINE. AREAS https://oxarus.com/en/quant#areas - L.I.T. · Early access A terminal that brings news, the economic calendar and market data onto one screen. - L.I.T. - Custom trading robots · Service Describe your rules, and we'll write a MetaTrader 5 robot built for you alone. - Custom trading robots - Research · Published Measurements on levels, gaps and price behavior. - Research - Engineering · Institutional Data pipelines, testing infrastructure and risk controls. - Engineering Representative screens. Not investment advice. Interface labels: Explore EACH AREA FEEDS THE OTHERS. LOOP The four areas may look like separate products, but they run on shared infrastructure. What research measures becomes a robot rule; a control built in engineering carries over unchanged to the terminal and the robots. https://oxarus.com/en/quant#flow-heading - Research - Robots - Engineering - L.I.T. Representative interface data - level_study.ipynb - Robot.ex5 - pipeline · breakers - terminal Handoff 1. A finding becomes a rule If a level's name doesn't change the odds of a break, no robot gets a rule that says 'open a trade at this level.' Only behavior that holds up against a control group makes it into a rule. - Proof: Level families ~41%, control ~40%: no difference. - Representative interface data - artifact: level_study.ipynb → rules.md 2. A measurement becomes context We measured how long gaps take to close. The terminal shows this next to the news as context, never as a trade recommendation. - Proof: 65% of gaps closed in the opening session, 95% within five trading days and 98% within 60 days. - Representative interface data - artifact: gap_study → L.I.T. context panel 3. Controls go inside the robot Daily loss limit, stale data and spread checks are added to every robot from the same module. Before a robot starts, the conditions under which it stops are already written down. - Proof: The stop rule is written before the start rule. - Representative interface data - artifact: breakers.yaml → Robot.mq5 4. Clean data, honest measurement Minute prices from two sources are compared, and gaps and synthetic ticks are filtered out. Research runs on this cleaned data. - Proof: Minute data, 2020–2026, two pairs. - Representative interface data - artifact: feed_diff → M1 dataset 5. Live logs feed back into tests The robot's live logs are compared with a replay of the same day in the test environment. If the two diverge, the test infrastructure gets fixed first. - Proof: Live and test must produce the same sequence of events. - Representative interface data - artifact: Experts journal → test suite 6. The pipeline feeds the terminal News, calendar and price feeds pass through the same normalization pipeline. In the terminal, time, source and impact tag read consistently on every card. - Proof: One pipeline, one time reference. - Representative interface data - artifact: news_pipeline → Intelligence Wire Interface labels: Pick a handoff, or click an area in the diagram. WE HAVE SKIN IN THE GAME. STANCE https://oxarus.com/en/quant#stance-heading We run the systems we build on our own capital first. Before we use an idea, we measure it and compare the result with a control group under the same conditions. We don't publish result figures; this page describes the method. - No control group, no finding · CONTROL Every measurement is compared against matched samples drawn at random under the same conditions. No difference means no finding. 01 - An idea that fails on two pairs is shelved · REPLICATION A result on a single pair can be chance. It has to replicate on at least two independent pairs, across different years. 02 - Tail-event days get their own inventory · INVENTORY Sudden gaps, liquidity pullbacks and surprise decisions are logged separately, so they don't disappear into the average. 03 - The stop rule is written before the start rule · HALT Before a system goes live, the conditions under which it stops are defined in code and in documentation. 04 Gates an idea has to clear LET'S TALK MARKETS. QUANT Terminal, custom robot, research or infrastructure: tell us what you're working on, and we'll route you to the right team. https://oxarus.com/en/quant#cta - Get in touch → start_project_brief(topic="quant") ACTIONS - Get in touch → open_page(path="/quant", anchor="cta-heading") - What we do → open_page(path="/quant", anchor="areas") - Get in touch → start_project_brief(topic="quant") - Türkçe → switch_locale(locale="tr", path="/quant") RELATED PAGES - Oxarus home - L.I.T. - Custom Robots - Research - Engineering