Source event
COPIERA receives a broker fill/update or an authenticated webhook event with source and account context.
Execution reference
What COPIERA measures, checks, and records.
Trade-copying speed is not one number. Internal signal-to-dispatch time, network transit, provider acknowledgement, and market fill time measure different stages. COPIERA reports its own stage without presenting it as a guaranteed broker fill time.
Normalize and validate
The engine validates action, quantity, symbol mapping, group membership, and stable event identity.
Risk decision
Configured position caps and active daily or weekly realized-P&L lockouts are evaluated before new opening exposure is routed.
Follower dispatch
Eligible follower requests are started independently so one slow provider does not create a sequential queue for every other follower.
Provider outcome
The broker or API provider accepts, rejects, or times out the request. That external response is distinct from COPIERA's internal dispatch time.
Audit and reconcile
Execution state is recorded, and position reconciliation can identify drift before a later instruction creates unwanted exposure.
Reliability controls
Stable event identity
Webhook and execution events use stable identifiers where the source exposes them. Database uniqueness and deterministic client-order identifiers reduce duplicate processing during retries.
Protective exit behavior
COPIERA does not blindly send an exit to a follower that is known to have no corresponding copied position. Protective skips are logged so the user can see why the instruction was not routed.
Connection backoff
Repeated authentication or transient failures use backoff and circuit-breaker behavior. A broken connection should not continuously create login traffic or throttle unrelated accounts.
Provider-reported state
When supported by the route, account, position, fill, and P&L state comes from provider responses or subscriptions. COPIERA does not treat an internal request as proof of a broker fill.
Latency definition
“Signal-to-dispatch” is measured from the engine's accepted source event to the point an eligible follower request is handed to its provider adapter. It excludes provider acknowledgement and exchange fill time. Network conditions, provider load, account permissions, risk checks, and market liquidity can change the end-to-end result.
Risk scope
COPIERA's lockouts are software controls for copied opening orders; they are not broker-side guarantees. Users remain responsible for broker and prop-firm rules, orders placed outside COPIERA, market gaps, and validating positions before live or funded use.