Core Reading Path · Step 5 of 5
Intro
TL;DR
- Positions must continuously satisfy margin requirements to remain valid
- When those requirements are no longer met, the system automatically closes the position
At this point, a trade lifecycle is already clear: orders become positions, and positions continuously evolve as the system updates their state.
The remaining question is what happens when a position no longer fits within the system's constraints.
In traditional systems, this situation often involves delayed reactions, warnings, or manual intervention. In Hyperliquid, it follows directly from the same rules that govern everything else.
Margin is not a separate check or periodic process. It is a condition that must always hold for a position to remain valid.
Margin as a continuous condition
Margin determines whether a position can exist within the system.
As prices change, the system continuously recalculates the relationship between position size, collateral, and market value. This determines whether the position remains within valid limits.
This is not triggered by specific events or checks. It is part of the system's ongoing evaluation of state.
A position is either valid under current conditions or it is not.
When a position becomes unsafe
As market conditions move, a position can move toward the point where it no longer satisfies margin requirements.
This does not introduce a new type of process. It simply means that the current state is no longer valid under the system's rules.
At that point, the system does not wait for user input or external intervention. It continues applying its rules to move the system back into a valid state.
Liquidation as state transition
Liquidation is how the system restores a valid state.
It reduces or closes the position, depending on how far the position has moved beyond valid conditions. This process is not separate from trading, it follows the same logic as any other state change.
There is no manual trigger, no discretionary decision, and no alternative path once conditions are breached.
From the system's perspective, liquidation is not an exceptional event. It is a continuation of the lifecycle.
How the system responds
State conditions
Key idea
What this changes
Seeing liquidation this way removes the idea that it is something that happens to you.
It is not the result of the system deciding to act. It is the direct consequence of the position no longer meeting the conditions required to exist.
This means that risk is not something managed after the fact. It is embedded into the system's behavior at all times.
Reinforcement
A position exists only while it satisfies the system's constraints. From the moment it no longer does, the system continues the lifecycle by adjusting or closing it.
There are no warnings in the core mechanism, no intervention layers, and no possibility to pause or override the outcome.
The same rules that allow positions to exist are the ones that close them.
You can move on when
- You understand that margin is continuously enforced
- You can explain why liquidation happens automatically
- You recognize that liquidation is part of the same lifecycle
Final recap
At this point, the system can be understood as a whole:
- Actions directly change system state
- State continuously evolves over time
- Control sits entirely with the user
- Outcomes cannot be reversed
- The system enforces valid conditions automatically