> guide --status-vs-event
Status vs Event
SOG separates current or lifecycle status from historical events. This reduces overstatement and keeps recovered incidents distinct from failed outcomes.
| active | The record is treated as operating or available based on currently linked sources. |
|---|---|
| limited | The stablecoin appears to operate with important limits such as access, redemption, geography, or market availability. |
| discontinued | Issuance, support, or operation has ended or entered a wind-down state. |
| failed | The registry records a severe historical event or lifecycle outcome that supports failed status. |
| depeg | A market or redemption stress event where the stablecoin deviated materially from its target peg. |
|---|---|
| wind-down | An issuer, exchange, regulator, or protocol-supported process to end or phase out support. |
| collapse | A severe event where the stablecoin did not return as a functioning stablecoin. |
| regulatory action | A public notice, enforcement action, regulatory restriction, or official context source. |
| Recovered event | A recovered depeg can remain an event while the stablecoin status remains active. |
|---|---|
| Failed status | Failed status should not be assigned from a price chart alone. It needs lifecycle and source context. |
| Visible uncertainty | If the sources are not enough, SOG uses known unknowns instead of guessing. |