# Risk Boundaries & Explicit Non-Claims

Surge is designed to constrain infrastructure-induced execution distortion.

It is not designed to eliminate market risk.

Clear boundaries are essential to long-term credibility and systemic adoption.

### 1. Market Risk (Not Eliminated)

Surge does not eliminate price risk.

Market outcomes remain influenced by:

* Supply and demand
* Liquidity depth
* Macroeconomic events
* Information asymmetry
* Volatility and sentiment

These dynamics are intrinsic to open financial systems.

Surge addresses structural execution variance — not economic exposure.

The system is designed to reduce:

* Ordering distortion
* Post-submission reprioritization
* Execution variance caused by probabilistic sequencing

It does not guarantee profitable outcomes, stable pricing, or reduced volatility.

Participants remain exposed to market risk.

The objective is to ensure exposure reflects market conditions — not infrastructure behavior.

***

### 2. Trading Behavior (Not Governed)

Surge does not regulate trading strategy or participant behavior.

Participants may:

* Use leverage
* Trade under volatility
* Operate automated strategies
* Act on incomplete or incorrect information

These behaviors are properties of open markets.

Surge’s guarantees are limited to deterministic processing under defined system rules.

The protocol does not:

* Assess decision quality
* Enforce economic rationality
* Protect participants from strategic error

It ensures that valid intent, once accepted, is executed according to deterministic rules.

***

### 3. External Data & Oracle Inputs (Isolated, Not Guaranteed)

Surge does not control external data sources.

External inputs may:

* Be delayed
* Be unavailable
* Reflect incorrect or manipulated reporting

The system treats external data as bounded inputs.

Execution outcomes are derived from the referenced input state at the defined execution boundary.

Subsequent changes to external data do not retroactively alter resolved outcomes.

Surge enforces deterministic processing of supplied inputs.

It does not guarantee correctness of those inputs.

***

### 4. Scope of Guarantees

Surge guarantees:

* Deterministic ordering at admission
* Separation of execution and settlement authority
* Conditional finalization upon verification
* Bounded behavior under defined stress conditions

Surge does not guarantee:

* Price stability
* Liquidity sufficiency
* Oracle correctness
* Profitability
* Continuous liveness under extreme fault conditions

When integrity conditions are not satisfied, settlement halts.

When market volatility occurs, execution reflects prevailing conditions.

Determinism does not remove economic risk.

It removes infrastructure ambiguity.

***

### Why These Boundaries Matter

Overbroad guarantees undermine infrastructure credibility.

Surge defines narrow, enforceable invariants and isolates external uncertainty rather than absorbing it.

This approach:

* Clarifies responsibility boundaries
* Reduces interpretive ambiguity
* Aligns with institutional risk expectations
* Preserves architectural credibility

Risk remains.

Execution distortion is constrained.