⚠ INTERNAL — Operator UX mock · Design preview of V2 development path · demo-wired ≠ production-live · back to dev guide
Polygon · pUSD 10
📓 Developer Guide 📋 Reason Codes 📈 Shadow Mode
JD John Doe · Admin

PortfolioHedger

strat.portfoliohedger
Strategy planned Spec started frozen

PortfolioHedger monitors the user's Polymarket portfolio for correlated exposure flagged by the Risk guardrail and builds offsetting positions to redu

What it does

PortfolioHedger monitors the user's Polymarket portfolio for correlated exposure flagged by the Risk guardrail and builds offsetting positions to reduce net directional risk. When correlated market clusters exceed target_residual_corr and hedging cost is within max_hedge_cost_bps, the bot emits hedge OrderIntents to neutralise the correlation.

Pipeline placement

runs after: Observation bus / internal analytics PortfolioHedger runs before: Risk guardrail pipeline

Applies to: User Polymarket portfolios where correlated market clusters are identified by the Risk guardrail and residual correlatio

Why it matters

If this failsConsequence
Correlation model misjudges relationship between marketsIf two markets are assumed correlated but resolve independently, the hedge creates unintended net short exposure rather than neutralising risk.
Stale input dataActing on stale signals for PortfolioHedger produces trades based on outdated market conditions, generating adverse fills.
KillSwitch not respectedEmitting OrderIntents while KillSwitch is active bypasses risk controls.

Inputs

Polymarket inputs

InputSourceRequiredUse
CLOB book (mid, depth, spread)ws_marketrequiredRead current market price and available depth for order sizing.
Market status (open/closed/resolved)clob_publicrequiredSkip closed or resolved markets.

Internal inputs

InputSourceRequiredUse
KillSwitch active flagKillSwitchrequiredAbort all intent emission if KillSwitch active.
PortfolioHedger analytics signalinternal (analytics engine)requiredProvides the core PortfolioHedger signal that drives trade decisions.
Builder code bytes32internal configrequiredInjected into builder field on every signed V2 OrderIntent.

Authority

What this bot is permitted to do

Trade

State

Readiness

Spec started

Status

planned

Class

Alpha Strategy

Default mode

shadow_only

Developer owner

Polytraders core — Strategy pod

Capital impact

Direct

Reason codes emitted

CodeSeverityMeaningAction
PH_TRADEINFOAll gates passed. IOC OrderIntent emitted for PortfolioHedger.Emit IOC OrderIntent.
PH_MARGINALWARNEdge is within the warning threshold; size reduced 50%.Emit at 50% size; log warning.
PH_NO_EDGEINFOEdge below hard floor. Skipping.Skip; emit sampled DecisionReport.
PH_HARD_REJECTHARD_REJECTA critical gate condition blocked the trade (stale data, kill switch, or hard parameter breach).Skip; no OrderIntent.
KILL_SWITCH_ACTIVEHARD_REJECTGlobal kill switch is active.Skip all markets; no OrderIntents emitted.

Used by

Reverse index — strategies that currently reference strat.portfoliohedger. If you change this bot's authority or reason codes, these strategies must re-pass shadow.

StrategyStateActivity
NBA props — line-shopdemo-wiredlast triggered 16m ago
Crypto Q2 — basket rebalancefrozenlast triggered 23m ago
US Elect — book-builderdemo-wiredlast triggered 30m ago

Showing 3 of 3 · demo-wired ≠ production-live

Why this matters

Strategy bots does NOT sign, route, or directly submit orders to the chain. Understanding the authority boundary prevents misuse and makes promotion-gate reviews faster and more reliable. View raw spec JSON →
Polytraders Operator UX Mock · INTERNAL · demo-wired ≠ production-live · the plan · reason codes · shadow-mode pipeline
⚙ Page Configuration
Current page settings
Loading configuration…