Advanced trigger orders (TP/SL) for API and SDK

[mintlify]

Summary

Adds a new documentation page covering advanced operational details for TP/SL trigger orders, targeted at SDK and API users.

Topics covered

• Off-chain storage: TP/SL orders live in the RFQ indexer until triggered, not onchain
• Silent settlement failures: no MM quotes, contract rejection, worst_price gap scenarios
• worst_price edge case in fast markets: detailed walkthrough of how fixed-at-creation worst_price can cause non-fills when the market gaps through the trigger level
• No retry mechanism in v1: failed triggers are flagged but not retried
• Position-less TP/SL creation: allowed by indexer, rejected by contract at execution time
• One active TP/SL per trigger type per lane: new order cancels prior one via lane_version
• SDK vs frontend comparison table: what the FE shields users from vs what SDK users must handle

Files changed

• trading/trigger-orders-advanced.md (new, renamed from trigger-order-caveats)
• docs.json — added to Trading nav group after trigger-orders

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
truecurrent	🟢 Ready	View Preview	Apr 23, 2026, 9:42 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[ckhbtc]

personally i wouldn't make a page called "caveats" i would just add it to the trigger orders page as part of the flow, like, "hey this is how TP/SL orders work, they're off chain, we have an executor, it listens to mark and sends a request to the rfq indexer if its hit" but technically this is correct so i will approve it and you can organize as you see fit

[bguiz]

personally i wouldn't make a page called "caveats"

OK. also considering the total page length + different user personas that would use each of these sections, that this should remain as 2 separate pages. But point taken, so going to reframe this as "Trigger Orders (TP/SL) Advanced Operational Use Cases"