Live trader-sourced events
The default case. A live trader-sourced event is extracted from a source message posted at or near the time of the action. No special classification flag is needed.Retrospective events
retrospective means the source message described an action after it happened.
Retrospective events can still represent real trader activity, but the delay matters when interpreting entry context, price context, and “what happened live” workflows.
Product surfaces should not emphasize this flag by default. It becomes relevant when the user asks about timing, source chronology, or whether a post was made after the fact.
Assumed events
assumed means the system inferred the event from the surrounding position sequence.
A common case is a trader flipping from one side to another: the system may infer that the prior position must have closed before the new one became active.
Assumed events help maintain coherent position history, but normal user-facing event listings should skip them unless the user asks about inferred events or missing closes.
Auto-generated events
autoGenerated means the system created the event rather than extracting it from a trader source message.
Common cases include:
- stale open positions that need to be closed so current positioning is not distorted
- prior trade cycles that need to be closed when a new cycle begins on the same instrument
Why these flags exist
The flags let Centaur keep two views true at the same time:- source-backed trader activity stays visible and auditable
- position history stays coherent enough for open-position state and performance workflows