ORDANE Rulebook

§0Principles

• P-1. Every rule exists to protect two things: the payout reserve that pays disciplined traders, and the discipline itself. These are the same rules professional capital managers impose on anyone trading serious capital.
• P-2. All accounts operate on simulated capital, declared as such in every piece of communication.
• P-3. All numeric claims published by Ordane carry a date and a source.

§1The Account: Ordane Instant Account

Instant Supreme. One product, direct access and no evaluation phase. Five sizes:

No recurring fees or hidden tiers. The published list price is versioned with these rules. A valid promotion shown at checkout changes the amount charged, never the account rules.

§2Trading Rules

• R-1 · Maximum Drawdown: 12%, static. Account equity may never fall below 88% of the initial balance. The floor is fixed on day one and never trails upward. Breach closes the account.
• R-2 · Daily Loss Limit: 3%. Measured against the balance at the start of the server day. Breach closes the account.
• R-4 · Consistency: 20%. At the moment of a withdrawal request, no single trading day may account for more than 20% of the cycle's total profit. Consequence, defined: if a day exceeds 20%, the excess profit from that day is deferred to the next cycle. It is never confiscated, and the remainder of the cycle pays out normally. No consistency rule at Ordane confiscates profit or closes an account.
• R-5 · Inactivity: 30 days. Accounts with no trading activity for 30 consecutive days are closed.
• R-6 · Prohibited practices: closed list. (a) latency, reverse, or hedge arbitrage; (b) high-frequency or bulk automated exploitation; (c) copy trading between Ordane accounts; (d) straddling news releases with paired opposing orders; (e) platform or data-feed exploitation; (f) gap abuse. Each practice is defined with examples in Appendix A. If a behavior is not listed in this section, it is not a violation. Discretion is not a rule. Violation closes the account.

§2AProduct status

Where a new purchase is bound to this Rulebook v1.5, the product is Instant Supreme under contract ID ordane-instant-supreme-20261001-v1. No other account model is offered under this version.

Each account remains governed by the version accepted at its purchase. No change is ever applied against it; a change that only widens a limit in the trader's favour can apply to it, with a date and a changelog entry. This version removes no right recorded under an earlier version.

§3Payout Rules

• PA-1 · Withdrawal timing: the first withdrawal is available 7 calendar days after account activation. Each later withdrawal is available 14 calendar days after the preceding withdrawal is completed. A pending, declined or unknown request does not start the next 14-day period.
• PA-2 · Profit split: the trader share is 100% on every withdrawal, from the first. It is fixed: there is no ladder, and it does not change with the number of completed withdrawals.
• PA-3 · Early withdrawal caps: withdrawals #1 and #2 are each capped at 3% of initial balance. From withdrawal #3 onward, no cap.
• PA-4 · Balance effect: withdrawals reduce account balance; the R-1 drawdown floor remains anchored to the initial balance.

§4The Ordane Guarantee

• G-0 · Approval is on the clock. Every withdrawal request is approved, or denied in writing citing the exact rule breached by section number, within 12 hours (clock hours). Past that deadline, the request is treated as approved and the G-1 clock starts.
• G-1. A payout approved and not paid within 24 hours (clock hours, not business hours) triggers automatic compensation: 100% refund of the account fee, plus the payout owed in full.
• G-2. Objective exclusions, both with hard deadlines: (a) documented fraud or KYC review, maximum 10 business days; (b) declared force majeure, maximum 10 business days. Beyond those deadlines, G-1 applies regardless.

§5Proof Infrastructure

• PR-1. The payout reserve address is disclosed on-chain for any purchase bound to this version. A dated payout ledger begins with payout activity; PR-2 governs dated payout-performance reporting.
• PR-2. Payout performance metrics (share paid within SLA, average processing time) will be published with dates and updated on a fixed monthly schedule, starting with the first month in which a payout is requested. Until then there is no payout history to report, and none is claimed.
• PR-3. Independent third-party attestation of payout records enters effect per the public roadmap milestone.

Appendix AProhibited practices: definitions and examples

This appendix defines each practice named in clause R-6. It does not add practices. If a behavior is not listed in R-6, it is not a violation. Examples show the line Ordane enforces; they are not an open-ended discretion clause.

• A-1 · Latency, reverse, or hedge arbitrage (R-6(a)). Exploiting delayed pricing, mismatched quotes between venues or feeds, or holding opposite positions whose edge comes from that mismatch rather than directional risk. Example that closes the account: buying on a lagged feed and selling on a faster feed on the same instrument for a riskless lock. Example that does not: a normal hedge of a single Ordane position, with no cross-feed exploit.
• A-2 · High-frequency or bulk automated exploitation (R-6(b)). Automation used to flood, scrape, or extract the platform or simulated book beyond ordinary assisted trading. Example that closes the account: a bot firing hundreds of order-cancel cycles per minute to harvest microstructure artifacts of the simulator. Example that does not: a single expert advisor or script placing discretionary or rules-based trades at human-scale frequency. R-6(b) does not ban all automation; it bans bulk or high-frequency exploitation.
• A-3 · Copy trading between Ordane accounts (R-6(c)). Mirroring, copying, or mechanically linking orders across two or more Ordane accounts held by different people (different account holders or ultimate beneficial owners), so that one person's risk is transferred or duplicated onto another person's account. Copy trading is permitted exclusively between Ordane accounts that belong to the same person, meaning the same account holder and ultimate beneficial owner. Copy trading between person A and person B is always prohibited. Example that closes the account: Account B auto-copies Account A's every entry and exit on the same instrument, where A and B belong to different people. Example that does not: two unrelated people independently taking the same setup; one person trading a single Ordane account by hand; or one person copying trades between two Ordane accounts that belong to that same person as account holder and ultimate beneficial owner.
• A-4 · Straddling news releases with paired opposing orders (R-6(d)). Placing opposite orders around a scheduled news event so that one side captures the spike regardless of direction. Example that closes the account: buy-stop and sell-stop both armed into a CPI release on the same symbol, sized to lock the jump. Example that does not: a single directional trade into or after news.
• A-5 · Platform or data-feed exploitation (R-6(e)). Using bugs, stale books, incorrect margins, or broken fills as an edge instead of market risk. Example that closes the account: repeatedly trading a known bad tick or frozen quote after you have noticed the feed error. Example that does not: an ordinary losing fill in a liquid market you believed was live; report a suspected platform fault to support rather than trading it.
• A-6 · Gap abuse (R-6(f)). Opening or sizing positions with the primary intent of harvesting weekend, holiday, or session gaps rather than bearing continuous market risk. Example that closes the account: max size into Friday close for the sole purpose of capturing Sunday open gap, with no stop and no continuous risk plan. Example that does not: a position held overnight or over a weekend under ordinary risk rules.

Appendix A is part of Rulebook v1.5. A change to this appendix is a rulebook version change: it binds new purchases after publication and is never applied against an account already open.

§6Changelog