A strong CAGR or Sharpe gets attention, but it is not the research conclusion. The saved result needs to show whether validation, frictions, and benchmark context still point in the same direction.
Saved Result Example
A saved result should read like a compact research memo, not like a screenshot of a flattering equity curve. This example shows the type of evidence Alphrex is built to keep attached to one run before it becomes a paper candidate.
Use this page when you want to see what a public-facing result page should actually communicate: why the run looked interesting, what the benchmark-relative read says, where validation weakens the story, and what the next action should be.
What this result is trying to prove
Outperforming one soft proxy is weaker evidence than surviving a harder fitted basket. A saved result becomes acquisition-grade only when the benchmark logic is legible.
A result page should end with a decision: compare it against peers, promote it into paper, or reject it as historically flattering but operationally weak.
Example evidence stack
What would fail this example
If the full-sample Sharpe stays high while walk-forward support turns negative or unstable, the result becomes a warning signal rather than an acquisition asset.
If a tougher constructed basket closes most of the active-return story, the saved result is no longer demonstrating a durable edge. It is demonstrating benchmark-selection risk.
A saved result without a compare step, paper step, or clear rejection rule is still just a static artifact. Alphrex matters when that memo pushes the workflow forward.