Institutional Execution & Profit Realization Architecture

QuadraTrades Production Reference — Terminal Blow-off Harvest & Single-Lot Realization Engine

● 493/493 TESTS PASSED AWS EC2 DEPLOYED v2.5 INSTITUTIONAL
01

Executive Summary & Core Directives

Following our rigorous profit audit (confirming ₹0.00 discrepancy to the paisa) and an in-depth analysis of institutional order flow mechanics versus retail trading habits, two critical enhancements have been designed, coded, rigorously tested, and successfully deployed to the AWS EC2 production server:

Trade Entry Timing Intra-Candle Sub-second tick execution at liquidity pools without waiting for candle close.
Parabolic Blow-off Harvest +8R to +12R Full 100% position offload at extreme expansion before late retrace giveback.
Single-Lot Realization Target Harvest Harvests 100% at Milestone 2/3 for 1-lot positions unable to fractionally scale.
Production Stability 100% Green 493/493 local unit tests passed; 23/23 remote tests passed on EC2; service active.
Key Takeaway: Institutions never enter on candle closes (which guarantees worse slippage, inflated stop distances, and delayed fills), nor do they leave 100% of runners unprotected during parabolic climaxes. Our enhanced system combines precision intra-candle limit/market executions with algorithmic terminal profit targets and lot-size-aware profit harvesting.
02

Trade Execution Timing: Intra-Candle vs. Candle Close

A core question asked was: "Is the system waiting for candle close or taking trades in between? Which one is better? How do institutions work?"

Parameter Retail (Candle Close) Institutional / Our System (Intra-Candle) Advantage to Our Traders
Entry Price At 5m Close (e.g., 24,145) At Structural Touch (e.g., 24,120) +25.0 NIFTY Points Better Fill
Initial Stop Distance 35.0 Points (Under entire candle) 12.0 Points (Under structural FVG/OB) 65.7% Smaller Dollar Risk
Position Sizing Fewer lots due to wide stop Optimal lot allocation per risk ceiling Higher Capital Efficiency
Profit Cushion at 5m Close 0.0R (Just entered) +2.08R (Already in profit) Stop moved to Breakeven instantly
03

Enhancement 1: Terminal Blow-Off Expansion Harvest (Mega-R Profit Take)

In high-velocity option buying, option delta and gamma surge parabolically during the climax of a directional expansion (e.g., a breakout into deep out-of-the-money or an intraday trend squeeze). While our trailing stop engine previously used an 80%–85% peak profit retention ratchet, a runner that achieved +8.0R or +10.0R could still give back 15%–20% of its peak before the trailing stop triggered.

The Institutional Fix: When price hits a statistical expansion ceiling (where institutional liquidity is liquidating into FOMO buyers), the system executes a Terminal Blow-off Harvest, booking 100% of the remaining runner at maximum extension.

Scaling Profile Regime / Strategy Terminal R Objective Harvest Rationale
STANDARD_BALANCED Trend Continuation, BOS, 5m Structural Expansions +8.0R Liquidity expansion objective fulfilled; closes 100% of runner.
TREND_RUNNER TrendDayRunner, FirstPullback (ADX ≥ 28) +10.0R Mega-trend exhaustion target; full harvest into parabolic climax.
EXPIRY_GAMMA ExpiryGammaBlast (0DTE Tuesday / Thursday) +12.0R Gamma explosion ceiling (12x risk); liquidates into late-day spike.
QUICK_HARVEST FailedBreakout, LiquiditySweepReversal (Range/Chop) +4.5R Mean-reversion limit; harvests before range re-accumulation.
# runner_engine.py — Step 0: Terminal Blow-off Expansion Harvest
risk_per_unit = trade.option_entry - trade.initial_stop
current_r = (current_option_price - trade.option_entry) / risk_per_unit if risk_per_unit > 1e-4 else 0.0

profile = getattr(trade, "scaling_profile", ScalingProfile.STANDARD_BALANCED)
if profile == ScalingProfile.EXPIRY_GAMMA:
    terminal_r = self.terminal_target_r_gamma
elif profile == ScalingProfile.TREND_RUNNER:
    terminal_r = self.terminal_target_r_trend
elif profile == ScalingProfile.QUICK_HARVEST:
    terminal_r = self.terminal_target_r_quick
else:
    terminal_r = self.terminal_target_r_standard

if terminal_r > 0.0 and current_r >= terminal_r:
    return RunnerEvaluationResult(
        should_exit=True,
        exit_reason=ExitReason.TARGET_REACHED,
        new_option_stop=current_option_price,
        new_underlying_stop=None,
        stop_updated=False,
        rationale=(
            f"Terminal blow-off target reached (+{current_r:.1f}R >= +{terminal_r:.1f}R objective "
            f"for {profile.value} profile); 100% position harvested at maximum expansion"
        ),
    )
04

Enhancement 2: Single-Lot Profit Realization Policy

In Indian equity derivatives (NSE F&O), option contracts must be transacted in discrete lot sizes (e.g. 1 lot = 25 or 65 shares). Fractional lot exits (such as booking 40% of 1 lot = 10 shares) are prohibited by exchange mechanics.

Previously, when a user traded a 1-lot position, _calculate_partial_qty returned 0 at Milestone 1 (+1.5R) and Milestone 2 (+2.5R/+3.0R) to protect the position from being illegally fragmented. While the stop loss was moved to breakeven, in choppy or range-bound markets, the entire 1-lot position would eventually retrace back to breakeven or trailing stop, booking 0 partial profits.

The Institutional Fix: We introduced a lot-aware profit realization policy:

# trade_manager.py — _process_milestone_2 (Single-Lot Policy for Quick Harvest)
is_single_lot = self.enforce_exchange_lots and (trade.lots <= 1 or trade.current_quantity <= self.lot_size)

if is_single_lot and self.enable_single_lot_target_exit and m3_pct <= 0.0:
    up = underlying_price or trade.nifty_entry
    rat = (
        f"Single-lot position reached target objective (+{m2_r:.1f}R) in {profile.value} profile; "
        f"100% position harvested at target"
    )
    closed_events = self.close_trade(
        exit_price=option_ltp,
        underlying_price=up,
        exit_reason=ExitReason.TARGET_REACHED,
        timestamp=timestamp,
        rationale=rat,
    )
    events.extend(closed_events)
    return events
05

Mathematical & P&L Impact Simulation

Below is a direct comparison between the old system behavior and the enhanced institutional architecture across two standard market days:

Scenario Position Old System Result Enhanced System Result P&L Delta / Value Added
Choppy Day: FailedBreakout Reversal
Option entry ₹100, Stop ₹80 (1R=20). Hits ₹150 (+2.5R), then collapses to ₹95.
1 Lot (65 qty) Stopped out at Breakeven (₹101.00).
Realized P&L: +₹65.00 (+0.05R)
Exits 100% at +2.5R (₹150.00).
Realized P&L: +₹3,250.00 (+2.50R)
+₹3,185.00 Pure Profit Saved
Trend Expansion: TrendDayRunner
Option entry ₹100, Stop ₹80 (1R=20). Spikes to ₹300 (+10.0R blow-off), then retraces to ₹240.
5 Lots (125 qty) Runner Retraced to 80% lock (₹260.00) on trailing stop.
Realized: +8.0R
Instant Terminal Harvest at ₹300 (+10.0R).
Realized: +10.0R Full Climax
+₹1,000.00 / lot Extra Gain Captured
06

Verification, Testing & AWS EC2 Deployment Telemetry

Every code modification was backed by comprehensive unit tests and verified both locally and on the production cloud infrastructure:

Environment Test Scope Result Status
Local Windows (Python 3.12.9) tests/unit/test_trade_manager.py (15 tests)
tests/unit/test_runner_engine.py (8 tests)
23 Passed (0.46s) 100% PASSED
Local Windows (Full Suite) All 38 test suites across strategies, risk, indicators, and copier 493 Passed (28.41s) 100% PASSED
AWS EC2 Ubuntu (13.207.146.76) Remote test runner in virtualenv 23 Passed (0.29s) 100% PASSED
AWS EC2 Systemd Service nifty-runner.service active status check Active (running), 0 errors, feed freshness 1.72s HEALTHY
# Deployment Commands Executed:
scp -i nifty-key.pem nifty_expansion_runner/trade_management/runner_engine.py ubuntu@13.207.146.76:/home/ubuntu/AntigravityTradeSetup/nifty_expansion_runner/trade_management/
scp -i nifty-key.pem nifty_expansion_runner/trade_management/trade_manager.py ubuntu@13.207.146.76:/home/ubuntu/AntigravityTradeSetup/nifty_expansion_runner/trade_management/
scp -i nifty-key.pem tests/unit/test_trade_manager.py ubuntu@13.207.146.76:/home/ubuntu/AntigravityTradeSetup/tests/unit/

# Systemd Restart & Verification:
sudo systemctl restart nifty-runner.service
curl -s http://localhost:8080/api/health
# Response:
# {"status": "HEALTHY", "is_feed_stale": false, "data_freshness_seconds": 1.72, "mode": "PAPER"}