Skip to main content
Every time you edit your agent’s strategy parameters or evaluation config, Halyrd creates a new version and starts a fresh track record for it. The previous version is retired — archived with its complete history of trades, drawdowns, and outcomes. Over time, you build an auditable trail of exactly which configurations were tried, what happened to each one, and which one is currently running. You are not guessing at what changed; the record is right there.

​
What a strategy version is

A strategy version is a distinct bundle containing:
  • Strategy parameters — indicators, thresholds, position size percentage, watchlist, and any other tunable values
  • EvaluationConfig — the preset or custom risk thresholds (max drawdown, daily drawdown, trade floor, evaluation window, consecutive loss limit) that go with this parameter set
  • A version ID — a unique identifier assigned automatically when the version is created
These three things are versioned together because they are meaningless in isolation. A strategy’s performance only makes sense relative to the risk constraints under which it was evaluated.

​
What each version tracks

While a version is running, it accumulates its own independent track record:

Trades and equity curve

Every trade executed under this version is attributed to it. The equity curve for the version shows exactly how the account performed from the moment this version started to when it was retired or is still running.

Drawdowns and breaches

Max and daily drawdown levels are tracked per version. If this version hit a max-drawdown breach, that breach is recorded in its history — you can see exactly when it happened and by how much.

Eligibility outcome

Whether this version reached ELIGIBLE, is still evaluating, or was retired before reaching the criteria. If it was promoted to live, that outcome is recorded here.

Run period

The exact dates this version was active — from creation to retirement or the current moment if it is still running.

​
When a new version is created

A new version is created whenever you edit strategy parameters or evaluation config in Settings. The moment you confirm the change:
  1. The current version is retired — its run period closes and its final state is recorded
  2. A new version starts with the new parameters and a fresh track record
  3. The agent continues running without interruption — no restart, no gap in operation
The version history grows one entry at a time. You always have exactly one version running.

​
The version history on /config

Open the Config screen (/config) to see the full version timeline for your agent. Each entry in the timeline shows:
FieldWhat it tells you
Version ID / labelThe unique identifier for this configuration
Parameters summaryA compact description of the key strategy values in this version
Run periodWhen this version started and when it was retired (or “running” if current)
OutcomeRunning / Retired / Promoted — what happened to this version
The currently active version is highlighted. Retired versions stay in the list permanently so you have a complete record of everything that ran.

​
Reading the history like a story

The version history is designed to be read chronologically as a selection-by-evidence trail. A typical history might look like:
  • Version 1 — retired after 3 days; hit max drawdown at 18%. Parameters were too aggressive.
  • Version 2 — retired after 12 days; reached the trade floor with negative expectancy. Position sizing was too small relative to gas costs.
  • Version 3 — currently running; positive expectancy after 10 closed trades; ELIGIBLE.
Each line tells you what was tried, what happened, and why the next version was a deliberate adjustment — not a random tweak. This is the record you review when deciding whether to promote, whether to adjust further, or whether the current configuration is genuinely ready.
Halyrd runs only one version at a time. The version history is a sequential record — not a parallel comparison. Running two configurations simultaneously and comparing their live performance is not supported. If you want to test a new set of parameters, you create a new version, which retires the current one. Parallel comparison is a future feature.

​
Making configuration changes

Go to Settings and edit any strategy parameter or evaluation config field. When you confirm the change, Halyrd retires the current version, creates the new one, and writes an audit entry in the journal recording what changed and when.
Editing your configuration retires the current version and resets the evaluation track record. If your agent was close to ELIGIBLE, the new version starts a fresh evaluation window with its own trade floor and drawdown counters. Make configuration changes deliberately — not as routine adjustments while the agent is evaluating.

​
Why this matters

Without version history, you would have no reliable way to know whether a configuration change improved or worsened your agent’s performance. One continuous track record that mixes multiple parameter sets is misleading — the numbers could be good because of version 1’s parameters, bad because of version 2’s, and you would not know which. Versioning gives every configuration its own honest score. You can see that version 3 was retired because it hit max drawdown, that version 4 is running with tighter position sizing, and that version 4 is currently on track for ELIGIBLE. That is a selection by evidence — not by feel.