The Timeframe-Weighted Volatility Framework (TWVF) becomes fully functional only when it is integrated into the Global Algorithmic Trading Software (GATS) as a set of precise, repeatable, and mathematically governed operational protocols. This chapter establishes the official rules that dictate how GATS must execute volatility, risk, trade management, and strategy coordination under the unified TWVF doctrine.
1. Protocol 1 — Universal Death-Stop Enforcement (DS = 16 × ATR256)
GATS must compute and enforce the Death-Stop (DS) for every instrument and every trade, regardless of timeframe, volatility regime, or strategy type. The enforcement rules are:
- DS is the structural boundary of trend life.
- All stop-loss levels must remain inside the DS boundary.
- No GATS strategy may set a stop beyond DS under any circumstance.
- DS must be recalculated every new bar of the anchor timeframe.
DS becomes the supreme risk boundary for the entire GATS universe.
Anchor timeframe for DS computation:
- For all intraday strategies (M1–M240): use M1440 DS.
- For all position strategies (M1440–M43200): use their own timeframe DS.
2. Protocol 2 — Fractal Risk Allocation (1% → 9%)
Every trade executed by GATS must adhere to the official fractal risk curve:
- M1 = 1%
- M5 = 2%
- M15 = 3%
- M30 = 4%
- M60 = 5%
- M240 = 6%
- M1440 = 7%
- M10080 = 8%
- M43200 = 9%
Risk percentages are computed on the DS value:
Risk Amount = DS × Risk%
GATS must:
- auto-adjust position size using DS × Risk%,
- reject any trade that violates the risk curve,
- aggregate risk across strategies using the same curve,
- prevent overlapping exposure beyond volatility tolerance.
3. Protocol 3 — Volatility Weighting Function (VWF) Integration
GATS must compute the Volatility Weighting Function (VWF) before executing any trade or adjusting any trailing stop. Formula:
VWF = (ATR₅₀ / ATR₂₅₆) × TFᵂ × R
GATS must apply VWF to:
- BE% calculation,
- Post-BE% determination,
- DAATS volatility scaling,
- position sizing strictness,
- trend-strength filtering.
High VWF → cautious. Low VWF → aggressive. Neutral VWF → structural.
VWF becomes the volatility “voice” that guides GATS decisions.
4. Protocol 4 — Break-Even (BE%) and Post-BE Rules
Break-even transitions must follow:
BE% = Risk% × VWF
Post-BE% = Risk% × VWF
GATS must use BE% to:
- move the stop-loss from DS toward the entry,
- lock in neutrality after the market moves in favor,
- trigger DAATS only after BE conditions are satisfied.
Post-BE ensures:
- minimum structural profit (MSP),
- maximum volatility justification (MVJ),
- alignment with long-term trend integrity.
5. Protocol 5 — DAATS Activation Sequence
DAATS must activate only after the following sequence:
- DS is established and locked.
- Risk is calculated using the correct fractal level.
- BE% has been structurally satisfied.
- Post-BE% has been fully achieved.
DAATS must never activate before the structural break-even point.
Once active:
- DAATS must expand during volatility spikes,
- DAATS must compress during volatility decay,
- DAATS must remain inside the DS boundary,
- DAATS must never trigger an exit independent of DS or BE.
6. Protocol 6 — Multi-Strategy Harmonization
When multiple GATS strategies operate simultaneously:
- each strategy must compute its own DS and VWF,
- total exposure cannot exceed volatility tolerance,
- cross-timeframe alignment must be checked before trade entry.
TWVF provides harmonization rules:
- Lower timeframes cannot contradict higher timeframe DS.
- Strategies sharing the same direction must aggregate risk.
- Reversal-based strategies must respect the macro trend.
GATS becomes a single multi-layer intelligence system rather than nine independent engines.
7. Protocol 7 — Cross-Asset Volatility Normalization
GATS must normalize volatility across all supported asset classes using DS and VWF:
- FX → smoothest volatility memory
- Equities → earnings-driven volatility
- ETFs → macro correlation cycles
- Crypto → high volatility expansions
- Commodities → cyclical structural volatility
- Indices → liquidity-weighted volatility
One doctrine for all asset classes — TWVF becomes the universal risk translator.
8. Protocol 8 — Execution Filters and Rejection Logic
GATS must reject:
- any trade where DS is invalid,
- any position where BE% is violated,
- any DAATS activation without Post-BE,
- any cross-timeframe contradiction beyond tolerance,
- any risk exceeding fractal curve allocation.
Accept only:
- signals aligned with macro structure,
- volatility-consistent trades,
- positions respecting DS and VWF,
- multi-timeframe-confirmed entries.
9. Protocol 9 — Institutional Monitoring
GATS must continuously monitor:
- DS movement,
- VWF shifts,
- ATR decay and expansion cycles,
- strategy overlap,
- portfolio volatility load.
This ensures that:
- no volatility cluster is ignored,
- no macro-shock escapes detection,
- no strategy violates structural doctrine.
10. Transition to Chapter 17
The operational protocols now complete the foundation for TWVF inside GATS. The next chapter focuses on portfolio-level execution — how institutions like GFE & GAI can integrate TWVF across multi-asset portfolios for global exposure.
Next:
Chapter 17 — Portfolio Execution Under TWVF: A Unified Model for Global Multi-Asset Management