Skip to content

Glossary of Aurono Terms

This glossary defines the key terms used throughout Aurono’s documentation and interface.

All definitions reflect how the terms are used within Aurono, not generic trading jargon.


See Starting Capital.

The term “allocated capital” is a synonym for the EUR amount a strategy is permitted to use. The Aurono interface now uses starting capital and available cash consistently across the Simulate and Evaluate tabs; both terms refer to the same underlying concept.

Aurono will:

  • Never exceed the strategy’s starting capital
  • Never borrow funds
  • Stop buying automatically once the allocation is fully used

A technical interface that allows software to communicate with an exchange.

In Aurono:

  • The API is used to request market data
  • Place buy and sell orders
  • Retrieve balances and order status

Aurono uses API credentials with restricted permissions and never has custody of funds.


A human-readable label summarizing how a strategy behaves based on its parameters — e.g., Patient & Selective, Responsive, Balanced, Cautious.

Archetypes are descriptive labels, not quality judgments. A patient strategy is not better than a responsive one; they suit different market conditions and different users.


A collapsed section at the bottom of the Evaluate tab. Expands to show five sub-tabs: Trades, Holdings, Versions, Events, and Parameters.

The audit trail is the historical record of everything a strategy has done. It’s closed by default so the main Evaluate view stays focused on what needs attention now.


The amount of quote currency (typically EUR) that a strategy can currently spend on new buys.

Available cash excludes:

  • Cash reserved for pending buy orders
  • The value of any position currently held

When available cash drops below 20% of the strategy’s starting capital, Aurono shows a danger zone warning on the Evaluate tab with a link to the Capital Rebalancer.

See also: Reserved Cash, Starting Capital.


The weighted average price at which the currently held asset was acquired for a strategy.

Aurono uses the ACB to enforce a core rule:

Aurono only sells when the sell price is above the ACB.

ACB is recalculated using actual executed prices, not limit prices.


The fixed amount of quote currency (for example EUR) spent on each executed BUY trigger.

The buy amount:

  • Is strategy-specific
  • Does not change with price
  • Directly determines capital pressure when multiple BUYs occur

A market condition where the BUY trigger threshold is met.

A buy signal:

  • May or may not result in an executed BUY
  • Is ignored if capital is unavailable

The minimum percentage drop between two consecutive candle closes required to allow a buy.

Example:

  • Buy trigger: −4%

Aurono evaluates this only at candle close.


One of the three insight cards on the Evaluate tab. Answers the question “are my triggers actually firing, and if not, why?”

Reads like: “Buy line crossed 8× → 2 bought, 2 cancelled at exchange, 4 blocked (not enough cash). Sell line crossed 16× → 0 sold, 16 blocked (11 price below cost basis, 5 no inventory).”

It distinguishes three buckets per side:

  • Bought / sold — signals that resulted in a completed trade
  • Cancelled at exchange — signals that became orders but didn’t fill
  • Blocked — signals that were stopped before submission, with human-readable reasons (not enough cash, price below cost basis, no inventory, cooldown active, minimum position guard)

An analysis performed by the Strategy Lab to determine whether a strategy can survive its worst-case BUY accumulation without running out of allocated capital.

The check evaluates:

  • Max net buys required
  • BUY amount
  • Allocated capital

A price representation containing:

  • Open
  • High
  • Low
  • Close

Aurono uses only fully closed candles for all decisions.


The price at which a candle starts for a given timeframe.

For example:

  • The Candle Open of a 4h candle is the price at the exact moment the 4-hour period begins.

In Aurono:

  • The candle open price is used as the reference price for calculating limit order prices
  • It provides a stable, deterministic reference point that does not change after the candle closes

A candle whose time period has fully ended.

Aurono never evaluates:

  • Partial candles
  • Live candles
  • In-progress price data

Multiple BUY triggers that occur close together in time, before any SELL reduces inventory.

High concurrency increases short-term EUR usage but is not the same as net accumulation.


A waiting period between same-side trades. Prevents rapid-fire buying or selling when triggers fire repeatedly in quick succession.

For example, a 2-day cooldown means: after a BUY executes, the strategy waits 2 days before it can buy again. The same applies to SELLs independently.


The quantity of an asset currently held by a strategy.

In the context of “I already own this coin”:

  • The current position represents assets you already own before Aurono starts trading

You manually provide:

  • The amount of the asset
  • The average acquisition price

Aurono records this as an administrative registration so that:

  • Holdings are known
  • Average Cost Base (ACB) is correctly initialized
  • Future sell decisions respect the ACB rule

No order is placed on the exchange — it’s purely bookkeeping.


A warning state shown on the Evaluate tab when a strategy’s available cash drops below 20% of its starting capital and the strategy has a buy side configured.

When active, Evaluate displays a warning banner between the metrics strip and the main chart with an Open Rebalancer button. The same 20% threshold is reflected visually on the Holdings tab’s cash chart as a warm terracotta gradient at the bottom — the “danger band.”

The warning does not appear for strategies with no buy side (e.g., hold-only strategies), because they don’t need free cash to function.


A core design principle of Aurono.

Given:

  • The same strategy configuration
  • The same market data

Aurono will:

  • Make the same decisions
  • Produce the same outcomes
  • Generate explainable logs

An immutable fact recorded by Aurono. Events are append-only and never edited.

Examples: StrategyCreated, OrderSubmitted, OrderFullyFilled, CapitalCredited.

Events are the authoritative record. All other data (projections, P&L, snapshots) is derived from events.


The third tab of the Strategy Lab. It diagnoses a running strategy using real trade data: a verdict sentence, a metrics strip, a dual-panel chart (same component Simulate uses, but with real trades), three insight cards (Benchmark, Calibration, Position), and an audit trail drawer.

Evaluate is silent by default — a well-calibrated strategy shows no warnings. When something needs attention (danger zone, calibration gaps, etc.), Evaluate surfaces it as an inline banner with a clear next action.

See: Evaluating Strategies.


The process where Aurono checks a strategy’s trigger conditions against the latest closed candle. Evaluations happen automatically at scheduled times — every hour for 1h strategies, every 4 hours for 4h, daily at midnight UTC for 1d, and Monday midnight for 1w.

Each evaluation produces one of: BUY triggered, SELL triggered, or no signal (hold).


A record of every evaluation outcome — when it ran, which strategy, what the result was (evaluated, skipped, error), and why. Visible in Settings. Useful for diagnosing why a strategy hasn’t traded.


The trading platform where funds are held and orders are executed.

Aurono currently supports:

  • Bitvavo
  • Kraken
  • Coinbase

Aurono never holds funds itself.


The actual EUR and crypto balances on your exchange account. Aurono compares these with what your strategies expect to detect shortfalls. Visible in Settings → Exchange Balances.


Aurono executes predefined rules but does not:

  • Generate signals
  • Predict price movement
  • Make discretionary decisions

A sub-tab inside the Evaluate tab’s Audit Trail Drawer. Contains two charts stacked:

  • Available cash over time — step-area chart showing free EUR across the strategy’s lifetime, with a dashed reference line at starting capital and a warm terracotta band at the bottom marking the danger zone
  • Asset position over time — step-area chart showing how many units of the base asset were held at each evaluation

These are the same chart components used in the Simulate tab, rendered with real strategy data instead of backtest data.


A visual state on the dual-panel chart indicating a trade that was submitted to the exchange but cancelled or rejected — it never landed.

Rendered as a hollow ring in the buy side’s teal or the sell side’s amber, the same size as an executed trade. Distinct from:

  • Solid dot — executed (filled)
  • Faded small dot — ignored (blocked before submission)

The ACB line does not step at a hollow marker because no fill occurred.


A BUY signal that does not result in an executed BUY.

This can occur when:

  • Allocated capital is temporarily unavailable
  • Multiple BUY signals cluster closely together

Ignored BUY triggers do not necessarily indicate insufficient capital.


A SELL signal that does not result in an executed SELL.

This can occur when:

  • The price is below the Average Cost Base
  • There is insufficient inventory to sell

The total amount of an asset currently held by a strategy.

Inventory changes only when:

  • A BUY is executed (inventory increases)
  • A SELL is executed (inventory decreases)

A comparison between what your strategies need (EUR and crypto) and what’s actually available on the exchange. If there’s a shortfall, Aurono shows a warning with the exact deficit and guidance on what to deposit. Visible on the Dashboard and in Settings.


The execution mode where Aurono places real orders on the exchange. Contrast with Shadow Mode.


An order that specifies the exact price at which Aurono is willing to buy or sell.

Aurono uses limit orders only.


The most recent traded price reported by the exchange.

Aurono uses the ticker price only to calculate order amounts, not to decide whether to trade.


A notable achievement in a strategy’s lifecycle. Aurono detects milestones automatically:

  • First trade — first completed sell
  • Trade count — 10, 25, 50, 100 completed trades
  • All-time high — portfolio value and asset units both exceed the previous peak (requires at least one completed trade)

The minimum amount of an asset a strategy must hold before it’s allowed to sell. Useful to ensure the strategy accumulates a meaningful position before it starts selling. Also called “min position”.


An order that instructs the exchange to execute immediately at the best available price.

Market orders:

  • Do not guarantee an execution price
  • May result in slippage during volatile conditions

Aurono does not use market orders. Aurono uses limit orders only to ensure predictable execution.


The maximum number of consecutive BUY signals that occur without any SELL signal in between.

This measures short-term signal clustering, not total capital pressure.


The maximum number of consecutive SELL signals that occur without any BUY signal in between.

High sell streaks can indicate inventory exhaustion risk.


The maximum net number of executed BUYs minus SELLs observed during the analysis period.

This represents the worst-case accumulation pressure and is the primary driver of capital requirements.


An informational banner on the Evaluate tab (or a section in an email report) that surfaces something needing the user’s attention — regime shift, danger zone, stale strategy, losing against benchmarks — with a navigation button to the tool that can address it.

Nudges inform and link; they never execute actions on your behalf. The only exception is directives that you explicitly opt into at strategy creation (e.g., auto-sell when a goal is reached). Those are pre-committed user instructions, not reactive nudges.

See also: Danger Zone.


The running difference between executed BUYs and executed SELLs.

  • BUY increases the saldo by +1
  • SELL decreases the saldo by −1

The maximum value reached defines Max Net Buys Required.


See Buy Amount and Sell Amount.


A derived read model rebuilt from events. Projections are not authoritative — they can be regenerated at any time by replaying the event store.

Examples: strategy state, portfolio snapshots, capital balances.


The maximum observed EUR drawdown during the analyzed period.

This reflects historical behavior but cannot be relied upon for capital safety.


The number of decimal places allowed by an exchange for:

  • Prices
  • Amounts

Aurono strictly enforces exchange precision rules.


Restrictions imposed by exchanges on how many API requests may be made within a time window.

Aurono is designed to operate well within these limits.


The profit or loss from a completed sell trade. Calculated as: proceeds (what you received) minus cost basis (what you paid for those units, based on ACB at the time of sale).

Only sell trades produce realized P&L. Buy trades don’t — they change your position and ACB.


The act of moving capital between strategies to optimize allocation. Done through Lab → Rebalance. Capital can only move between strategies on the same exchange.

See also: Capital Safety Check, Utilization.


An execution mode where Aurono evaluates strategies against real market data but does not place orders on the exchange. Used to observe behavior before switching to live mode.


The fixed amount of quote currency (for example EUR) received for each executed SELL trigger.

The sell amount:

  • Is strategy-specific
  • Determines how quickly inventory is reduced

The minimum percentage rise between two consecutive candle closes required to allow a sell.

A sell is executed only if:

  • The rise trigger is met and
  • The price is above the Average Cost Base

A multiplier applied to historical price volatility to determine how extreme a price move must be before a trigger fires.

Higher sigma:

  • Fewer triggers
  • More patience
  • Lower capital pressure

Lower sigma:

  • More frequent triggers
  • Higher clustering
  • Increased capital stress

BUY and SELL sigmas are independent.


Slippage is the difference between the expected price of a trade and the actual execution price.

Slippage typically occurs when:

  • Markets are volatile
  • Liquidity is low
  • Orders are executed using market or stop-market orders

In Aurono:

  • Slippage is minimized by using limit orders only
  • Aurono defines strict price boundaries before execution
  • Trades will never execute outside the specified limit price

Slippage is therefore treated as a risk to be avoided, not managed reactively.


The amount of quote currency a strategy started with — the sum of all cash deposited into that strategy, minus withdrawals, plus the EUR value of any position bootstrapped at creation.

Starting capital is used as the reference line in the Evaluate tab’s charts and as the base for the Benchmark insight card’s comparisons against Buy & Hold and monthly DCA. When the strategy’s available cash drops below 20% of starting capital, the danger zone warning appears.

Synonyms: allocated capital (legacy term, still seen in some places).

See also: Available Cash, Reserved Cash.


A strict set of rules defining:

  • When Aurono may buy
  • When Aurono may sell
  • How much capital may be used

A strategy is enforced exactly as defined.


An immutable snapshot of a strategy’s parameters. Any change to strategy settings creates a new version. Previous versions are preserved in history.


The current total worth of a strategy: available cash + reserved cash + current market value of any position held.

This is the number the Evaluate tab shows in the first card of its metrics strip. It updates at each evaluation tick (candle close).


The authoritative capital requirement calculated as:

Max net buys required × BUY amount

If allocated capital covers this amount, the strategy is capital-safe by design.


See Live Price.


The fee charged by the exchange when your order fills immediately by matching an existing order on the book. Aurono uses the taker fee rate for sizing calculations, because limit orders at trigger threshold prices typically fill as taker orders.

See also: Limit Order.


The interval at which candles are evaluated.

Aurono supports:

  • 1h (hourly)
  • 4h (4-hour)
  • 1d (daily)
  • 1w (weekly)

Aurono evaluates strategies once per timeframe, at candle close.


The Trades tab on the Activity page. Shows every completed trade with a human-readable subtitle explaining why the trade happened — for example “Price dropped 5.3% — bought €10.00 worth.” The primary view for reviewing what Aurono has done.


The exact price at which Aurono places a limit order. Calculated from the previous candle’s close price and the strategy’s trigger percentage.

  • BUY: prev_close × (1 − buy_drop_pct / 100)
  • SELL: prev_close × (1 + sell_rise_pct / 100)

The trigger threshold guarantees that fills respect the original signal boundary.


The paper profit or loss on a strategy’s current position. Calculated as: (mark_price − ACB) × position_units. This changes with every price movement. It becomes realized P&L only when a sell executes.


The percentage of a strategy’s total capital that is deployed (in crypto positions or reserved for pending orders). High utilization means little free capital for new buys. Visible in the Capital Rebalancer.

Formula: (position_value + reserved) / (free + reserved + position_value) × 100


The one-paragraph summary shown near the top of the Evaluate tab. It covers days running, overall P&L, comparison against Buy & Hold and monthly DCA, and a trade count.

Example: “Patient XDC-EUR Trader has been running for 19 days. You’re at −€4.48 overall, −€3.54 vs buy & hold and −€4.67 vs monthly DCA. No trades yet.”

The verdict sentence is prose, not a dashboard — it’s designed to be read naturally by someone checking in on their strategy without parsing numbers.


An API permission that allows funds to be withdrawn from an exchange account.

Aurono requires:

  • Withdraw permissions to be disabled
  • API keys to be execution-only

Aurono’s terminology reflects its design goals:

  • Determinism
  • Capital preservation
  • Execution-only behavior
  • Transparency

If a term appears unclear elsewhere in the documentation, this glossary defines its exact meaning within Aurono.


  • Strategy Lab — Overview
  • Capital Safety Check Explained
  • BUY and SELL Sigma Explained
  • Why BUY or SELL Triggers Are Ignored
  • Trading Engine — How Aurono Executes Trades
  • Why Aurono Uses Limit Orders Only
  • Security & Fund Safety