QOVARYX.
Downloads paused

The previous build was out of date, so we took it down rather than leave it up. Join the release list →

← Research index

Why a cluster of small specialists beats one big model

The default move is to throw a larger and larger general model at every problem. We went the other way: a cluster of small specialists, each narrow, each focused on one aspect of the decision, each one you can point at when the system refuses.

Topic
Architecture
Reading time
5 min
Performance figures
None published

Ch. 01 — Architecture

What the specialists do

Rather than one component being asked to hold every consideration at once, the work is split by question. Described by function rather than by internal name:

Division of labour each answers one question
Primary chart reader Reads price behaviour across stacked timeframes and votes on direction with a stated confidence. The component most people would call “the model” — and only one voice among several.
Broad-market character Reads short-horizon behaviour and spreads across the major index, rates, currency and sector instruments to judge what kind of market this currently is.
Volatility state Classifies the prevailing volatility environment and raises a hard objection in the conditions where directional reading is least trustworthy.
Scheduled events Tracks proximity to company earnings and scheduled economic releases, and objects when the system is about to act into known, dated uncertainty.
Options context Reads where option pricing sits relative to its own history, positioning pressure, and the shape of pricing across expiries.
Dedicated objector Evaluated in parallel with the rest. Has no opinion on direction — only on whether this situation is legible enough to judge at all.
Realised-versus-implied volatility Compares what the market actually did against what its pricing expected, and reduces exposure when the two disagree.
Pattern confirmation A narrow chart specialist used for confirmation, not for initiation.

Why many small beats one large, here

  • You can point at the refusal. When the system declines, we can tell you which specialist objected and why. A single monolithic model cannot give you that; the reason is smeared across the whole thing.
  • Targeted repair. When market character shifts, we rebuild the one specialist responsible for reading it. We do not have to disturb everything else to fix one thing.
  • Independent failure. If the events specialist has a bad day, the chart reader is unaffected. A monolith fails all at once, in every dimension simultaneously.
  • Ensembling that means something. Specialists trained against different objectives produce genuinely independent judgements. When independent judgements agree, the agreement carries information. When twenty variations of one idea agree, it carries none.

Twenty views of the same idea are not twenty confirmations. They are one idea wearing twenty hats.

On why independence is the point

The hard part is not the machine learning

It is the engineering. A cluster needs something to route work to the right specialist, something to keep stated confidence honest, something to enforce objections, per-specialist audit records, retry and back-off behaviour when one is unavailable, and a check that each specialist actually has the inputs it needs before its opinion is allowed to count. None of that is novel research. All of it is plumbing — and the plumbing is where the reliability lives.

Policy

We publish no performance figures. This page describes structure, not results. Any return, win-rate or accuracy number attributed to Qovaryx did not originate from us.

Smart specialists doing uncoordinated things together still produce a bad decision. The orchestration is the product.

On where the difficulty actually sits