EGAML → GATS Implementation: How the State Matrix Becomes a Trade Filter
- January 4, 2026
- Posted by: DrGlenBrown2
- Category: Market Structure & Risk Doctrine
(EGAML Expansion Series — Post 10)
This post completes the EGAML Expansion Series by translating doctrine into execution. The objective is precise: to show how the ETF Gravity & Asset Mass Law (EGAML) becomes an enforceable trade filter within the Global Algorithmic Trading Software (GATS).
If you have not read the canonical doctrine, begin here:
1) From Doctrine to Enforcement
EGAML is not an interpretive lens alone. It is a constraint system.
In GATS, doctrines only matter if they:
- Gate participation
- Restrict degrees of freedom
- Override discretionary impulse
- Survive automation
The EGAML State Matrix satisfies all four.
2) The State Detector (Input Layer)
The first implementation layer is the State Detector. Its sole responsibility is to classify the environment into one—and only one—state:
- State A: Supportive Absorption
- State B: Flow-Driven Extension
- State C: Vacuum / De-Risking
Inputs may include (conceptually):
- Higher-timeframe price acceptance
- Volatility expansion vs compression (TWVF-weighted)
- Macro correlation thresholds (CRTL)
- Flow persistence proxies
Importantly, price alone is insufficient. The detector evaluates context, not candles.
3) The State Matrix (Decision Layer)
Once classified, the State Matrix maps state → permissions. This mapping is fixed by doctrine.
| State | Entries | Risk Behavior | BE Logic | Objective |
|---|---|---|---|---|
| State A (Absorption) | Selective / HTF only | Wide, survival-first | Prohibited | Endure |
| State B (Extension) | Enabled | Structured scaling | Conditional | Participate |
| State C (Vacuum) | Disabled | Capital defense | Irrelevant | Protect |
This table is not guidance. It is law.
4) Risk Layer Integration (Non-Negotiable)
EGAML risk rules override strategy preferences:
- Death-Stop: 16 × ATR(256), anchored ≥ M240
- Minimum Trade Lifetime: enforced unless Death-Stop is hit
- Position Sizing: volatility-weighted, not signal-weighted
- Shock Override: macro correlation spikes force suppression
If a strategy conflicts with survival, the strategy loses.
5) Break-Even as a State-Gated Function
Within GATS, break-even logic is no longer a default safety mechanism. It becomes a state-gated function:
- Disabled in State A
- Conditionally enabled in State B after acceptance
- Bypassed in State C
This enforces the ADBED principle automatically.
6) Timeframe Authority Enforcement
EGAML mandates timeframe hierarchy inside GATS:
- M1440: Identity
- M240: Execution anchor
- < M240: Timing only
Any signal contradicting higher-timeframe identity is suppressed. This removes regime confusion at the system level.
7) Volatility Budget Governance
GATS enforces EGAML via volatility budgeting:
- Volatility consumption tracked across time (PLBND)
- Overconsumption reduces participation
- Re-expansion resets opportunity set
This ensures the system does not exhaust itself during absorption.
8) What EGAML Eliminates
Once implemented, EGAML removes:
- Impulse trades
- Setup-chasing without regime alignment
- Premature exits driven by noise
- False confidence during probes
The result is not fewer trades. It is fewer errors.
9) The Final Seal
In the ETF era, systems that do not gate by state are not trading systems.
They are exposure engines.
EGAML completes the transition from discretionary reaction to institutional execution.
Series Completion Note
This post concludes the EGAML Expansion Series. The canonical law remains permanently published as a Page, while these posts serve as explanatory and operational expansions.
About the Author
Dr. Glen Brown is President & CEO of Global Accountancy Institute, Inc. and Global Financial Engineering, Inc. He is the architect of the Global Algorithmic Trading Software (GATS), the Nine-Laws Framework for Adaptive Volatility & Risk Management, and multiple institutional doctrines governing modern market structure, risk, and financial engineering.
Business Model Clarification
Global Financial Engineering, Inc. and its associated frameworks operate under a closed, proprietary business model. No external investment advice is offered. All research, doctrines, and systems are developed for internal capital deployment and intellectual contribution.
Risk Disclaimer
Trading and investing in financial markets—including cryptocurrencies— involves substantial risk. Past performance is not indicative of future results. This document is provided for educational and conceptual purposes only and does not constitute investment advice. You are responsible for your own decisions, risk controls, and due diligence.