Urgent.News

What's breaking now, across thousands of outlets.

Tech

Adaptive Stop-Loss Thresholds Instead of Hardcoded Percentages

A fixed -3% stop does not mean the same thing on every instrument. On a volatile altcoin, 3% is inside the normal noise band, so the stop fires on routine wiggles and the strategy never gets to express its edge. On a low-volatility index product, 3% is a wide move, so the stop sits far beyond where the strategy's own logic would have exited. The same number produces opposite behaviour depending…

Hardcoded stop-loss percentages can be misleading for various instruments. On volatile assets, a 3% stop may trigger frequently, while on less volatile products, it may sit far away from the strategy's exit point. The solution is not to manually tune the percentage for each instrument but to derive the safety floor from the strategy's own stop calculation.

The formula used is threshold = - max(3.0, abs(strategy_stop_pct) * 2.0). The abs(strategy_stop_pct) * 2.0 clause ensures that the system never forces a close before the strategy's stop has a chance to work, only intervening when the position has drifted roughly twice the intended stop distance. The max(3.0, ...) clause guarantees a minimum 3% floor, preventing a strategy with a tight stop from being forced to close at a much lower threshold due to spread and slippage.

The 2.0 multiplier is crucial. A strategy that stops at 2% should have a 4% floor, cutting the position only when the loss is beyond what the strategy intended. Meanwhile, the 3% minimum floor ensures that the force-close is a genuine backstop and not a second, tighter stop. This approach scales with the instrument's volatility as the strategy perceives it, inheriting the strategy's view of normal movement instead of imposing an external one.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Why I Stopped Letting One Turn Give an Agent Two Orders

Why I Stopped Letting One Turn Give an Agent Two Orders I used to think duplicate delegation was a small prompting problem.

  • One turn should command only one action from an agent.
  • Guard records target agent and instruction per turn.
  • Follow-up flag corrects or extends instructions explicitly.

A Project Skill Can Change APX Behavior With One Name

A skill name is a boundary, not just a label. In APX, a project-local skill with the same slug as a user-global or built-in skill wins. That is useful when a repository needs its own operating rules.

  • Project-local skill overrides user-global or built-in skill in APX
  • Create SKILL.md file in .apc/skills/ directory to customize workflow
  • Project-specific skill replaces global version, not merging with it

More from Sunday 1 November →