Do 50%, 33% and 25% exits close 108% of the position?
Only if all three are defined against the initial position, which is invalid. Against the remaining quantity, a 100-unit example closes 50, then 16.5, then 8.375 units and leaves 25.125.
Free Pine v6 state-definition guide
The quantity-basis, tier-order, bar-timing and duplicate-event decisions needed before partial exits and TradingView alerts can be repaired or implemented safely.
State whether every percentage applies to the initial position or to the quantity remaining immediately before that tier.
List each trigger and percentage in execution order, including whether a later tier is allowed when an earlier one never fired.
Initial-position percentages must not exceed 100% in total. Remaining-quantity percentages must be evaluated as state transitions, not added together.
Document the instrument quantity step, minimum tradable amount and whether every tier rounds down, to nearest or fails when the remainder is too small.
Specify what happens if price crosses two or more tier levels within the same forming or completed bar.
Choose intrabar or confirmed-bar evaluation and state whether historical reload is expected to reproduce the realtime event sequence.
Give every tier a persistent fired state so price oscillation, recalculation or repeated alert evaluation cannot emit the same exit twice.
State exactly when tier state resets: a new entry, a complete close, a direction change or another explicit lifecycle event.
Freeze the intended quantity transition independently from webhook URLs, connector syntax, credentials and downstream broker behavior.
List the non-secret fields that identify symbol, side, tier, requested quantity basis, event ID and bar timestamp.
Provide one exact quantity walk-through plus cases where a tier must stay silent, duplicate events are rejected and invalid percentages fail explicitly.
Agree whether the first milestone ends with a frozen state table and defect report or includes a separately priced source change and retest.
Only if all three are defined against the initial position, which is invalid. Against the remaining quantity, a 100-unit example closes 50, then 16.5, then 8.375 units and leaves 25.125.
No. It removes one important intrabar ambiguity, but alert snapshots, higher-timeframe requests, data revisions and downstream transport still need their own acceptance evidence.
No. The audit freezes the state model, fixtures and repair boundary first. An authorized-source modification is quoted separately after the defect is reproducible.
Free diagnostic resource
See the public Pine v6 fixture, its 100 → 50 → 33.5 → 25.125 state walk-through and the limits of the current evidence.
Open the free toolReady for a feasibility check?