What getsyou failed.
Last updated: 3 September 2026
Engine rules (daily loss, max loss, consistency) fail a book automatically. The conduct below is not an auto-detector. It is detected via manual review; breach is applied by an admin with a recorded reason.
7.1Cross-account hedging
Opening offsetting exposure across accounts you control (or accounts you trade with another person to cancel risk) is prohibited. The admin breach reason CROSS_ACCOUNT_HEDGING fails an ACTIVE account, writes an account risk event, a status transition, and an audit log. That path is not an automatic scanner.
7.2Account takeover and sharing
Using someone else’s login, selling access, or letting a third party trade your book is prohibited. We may fail or close the book after review.
7.3Latency and arbitrage abuse
Exploiting delayed or stale quotes, feed mismatches, or execution artifacts to extract risk-free book value is prohibited. The desk fail-closes when the snapshot is missing or stale; gaming the moments around that is still a conduct breach.
7.4News and insider abuse
No news blackout window is configured on published books. That is not permission to trade on inside information or to coordinate fills around known events to game the snapshot. If we restrict a window later, it will land on the versioned plan — not as a silent extra rule.
7.5Ban evasion
Opening a new email or payment identity to dodge a failed or closed book is prohibited. New purchases from an evading identity may be cancelled or failed after review.
7.6How enforcement actually works
Detected via manual review; breach applied by admin with recorded reason. Automatic FAIL on a book comes from the risk engine on that snapshot (for example daily loss or max loss), not from a hidden conduct scanner.
7.7Contact
Questions: support@primeprop.dev.