It is worth being precise about what CortexQuant is and is not. It is not an
independent company, and the architecture does not treat it as a separate business
line. It is the framework that the Research and Technology pillars jointly operate:
the place where a research question becomes a runnable system, and where a running
system produces something a researcher can inspect. The engine-level detail of how
that framework hands work between stages is described separately; here the point is
structural.
Two people stand behind the framework, and their responsibilities map onto the
split the architecture depends on. Evan Valemont, founder and head, focuses on
market structure, financial mathematics and risk frameworks. Ryan Mercer translates
research requirements into data architecture, model deployment and engineering
systems.
Those are not two halves of the same job. One asks what can be known about a market
and under what conditions the answer would collapse. The other asks what can be
built, maintained and re-run so the question can be asked again, cheaply, on new
data. Their work converges at CortexQuant and is continuously tested through
real-world applications — which is where the Solutions pillar does its job.
This matters to anyone evaluating a research framework. Work that lives entirely
inside one person's judgment cannot be audited; work that lives entirely inside
code cannot be questioned. Keeping both disciplines in one framework is an attempt
to make each of them possible.
Founder and head
Evan Valemont
Market structure, financial mathematics and risk frameworks. The research side
of the framework: what a market is actually doing, what the mathematics
permits, and where the boundary of a defensible risk assumption sits.
Engineering
Ryan Mercer
Data architecture, model deployment and engineering systems. The translation
layer: turning a research requirement into infrastructure that can be run,
maintained and iterated without losing the reasoning behind it.