SESSIONS AND DEGRADED STATES
| Condition | What it means inside Dexter |
|---|---|
| Session-closed | The underlying market is closed, so fresh trading references are not expected |
| Stale | The venue is no longer receiving acceptable fresh data |
| Degraded | Freshness, deviation, or fallback rules are no longer strong enough for normal trading |
| Halted | The market is no longer safe to treat as open for new execution |
#Session closure is not oracle failure
Crypto trades continuously, but metals, energy, and equities do not.
Dexter therefore treats session closure as its own market condition rather than folding it into a generic oracle error.
A closed market is not necessarily a broken market.
It is often just respecting the structure of the underlying venue.
#How degraded states are handled
A stale or inconsistent reference path is different.
If freshness windows, deviation checks, fallback rules, or spread controls fail, the market can move into close-only or halted modes depending on severity.
Recovery is also controlled.
A market does not reopen instantly just because one fresh tick reappears.
The venue can require a stabilization period before normal posture is restored so users are not trading into a false recovery.
session closes -> market shows session-closed
bad price path -> market tightens to close-only or halted
fresh data returns -> recovery lag must pass before normal trading resumes#Why visible degradation matters
The product should show whether a market is closed because of schedule, constrained because of venue posture, or halted because the price path is not trustworthy.
That distinction is critical for user trust.
It also matters for review.
A venue that cannot tell the difference between ordinary closure and broken pricing will eventually communicate both states badly.