Trade Frame Fields
Canonical trade-frame field design — entry_side, entry_price, quantity, sl, tp, trail_offset and when to use each.
Design Canonical Trade-Frame Fields Deliberately#
| Field | Use it when | Design advice |
|---|---|---|
entry_side | The row truly wants an entry. | Keep it sparse and explicit. Empty string is better than implied direction. |
entry_price | You know the intended entry basis. | Match it to actual strategy timing: open, close, trigger, or limit series. |
quantity | Units are known directly. | Do not also express the same intent through size_pct unless the runtime expects one to stay neutral. |
sl and tp | The strategy has bracket-style risk exits. | Think of them as part of the signal decision, not a mapping convenience. |
trail_offset | The strategy genuinely trails. | Only emit it when trailing is real, not because the field exists in the schema. |