Built to protect capital first, grow it second
Every feature in Borgaardom exists to answer one question before any other: how much could this position lose, and is that loss acceptable. Here's how the system works in detail.
Six systems working together
None of these features operate in isolation. They're designed to inform each other continuously, so risk decisions are never made on a single data point.
Dynamic Stop-Loss Engine
Stop-loss thresholds recalculate continuously based on volatility and exposure, rather than sitting fixed at a single static number set once and forgotten.
Exposure Mapping
A live view of where capital is concentrated across positions, so overexposure to a single sector or instrument is visible before it becomes a problem.
AI Signal Scoring
Incoming market signals are scored for relevance and reliability, filtering out noise so decisions are based on patterns with actual weight behind them.
Drawdown Alerts
Threshold-based alerts flag when cumulative drawdown approaches limits you've set, giving you time to review and act before limits are breached.
Scenario Review Logs
Every risk adjustment is logged with the reasoning behind it, creating a reviewable trail for audits, retrospectives, and internal reporting.
Configurable Risk Bands
Set the boundaries that matter to your business — conservative, balanced, or aggressive — and the system operates strictly within them, not around them.
Why the stop-loss engine is dynamic, not fixed
Fixed stop-losses are set once and left alone, which means they're either too tight during calm periods or too loose during volatile ones. Neither serves capital protection well.
Borgaardom's engine recalculates thresholds against live volatility and exposure data, tightening protection when conditions shift and loosening it when conditions stabilise. The result is a risk boundary that moves with the market instead of ignoring it.
This isn't a replacement for your own judgment — it's a constant, disciplined layer underneath it, so capital decisions are never left to a single static assumption.
From setup to ongoing protection
Getting the system running takes three stages. After that, it operates continuously in the background.
Define your risk bands
Set the boundaries for acceptable exposure and drawdown that match your business's risk appetite, from conservative to aggressive.
Connect your positions
Exposure mapping and signal scoring begin working against your live data, surfacing concentration and relevance in one view.
Let the engine run
The dynamic stop-loss engine, alerts, and scenario logs operate continuously, adjusting as conditions change and recording every decision.
Fixed rules vs. a dynamic system
Static risk tools apply the same rule regardless of what's happening in the market. Borgaardom adjusts the rule itself as conditions move.
What this changes in practice
You're no longer choosing between "too cautious" and "too exposed" at the point of setup — the system recalibrates that balance as volatility and exposure data update.
| Capability | Fixed rules | Borgaardom |
|---|---|---|
| Stop-loss threshold | Set once, static | Recalculates continuously |
| Exposure visibility | Manual review | Live mapping |
| Signal handling | Unfiltered feeds | AI-scored relevance |
| Decision trail | Rarely recorded | Logged automatically |
| Risk boundaries | One-size-fits-all | Configurable bands |
Feature FAQs
A few common questions about how these capabilities work in day-to-day use.
Does the stop-loss engine override my own decisions?
No. It operates within the risk bands you configure and flags or adjusts thresholds accordingly, but the boundaries themselves are set by you.
How often do thresholds recalculate?
The engine evaluates volatility and exposure data continuously rather than on a fixed schedule, so thresholds can shift as conditions change.
Can I adjust risk bands after setup?
Yes. Risk bands are configurable at any time, and changes apply to future calculations without affecting the historical scenario logs.
What's recorded in the scenario logs?
Each adjustment is logged with the triggering data and reasoning, creating a reviewable trail for internal reporting or retrospective analysis.
See these features applied to your own numbers
Walk through how the dynamic stop-loss engine and exposure mapping would apply to your current setup.