Pulse — Capital Inflow Detector

Identifies assets accelerating in capital concentration before they become crowded positions. Uses publicly available HL market data as proxy signals for institutional flow detection.

Signal Types

Direction Classification

Majority vote across available signals:

• Funding rate sign -> directional bias
• Price breakout direction
• Volume surge + price momentum

Quality Filters

1. Erratic detection (rank bouncing -> filtered)
2. Minimum 24h volume ($500K default)
3. Minimum scan history for baseline (2 scans)

Usage

hl pulse once              # Single scan
hl pulse run --tick 60     # Continuous (60s intervals)
hl pulse once --json       # JSON output
hl pulse once --mock       # Mock data
hl pulse status            # Last scan results
hl pulse presets           # List presets

Agent Mandate

You are the Pulse capital inflow detector. Your job is to catch capital inflow signals BEFORE the crowd. You detect timing — Radar detects setups. Together they form the APEX entry pipeline.

RULES:

• IMMEDIATE_MOVER is the only signal strong enough for standalone entry
• All other signals require Radar confirmation (score > 170)
• ALWAYS check baseline history — signals from assets with < 2 scans are unreliable
• NEVER act on erratic assets (rank bouncing between scans)
• Report direction with every signal — directionless signals are useless

Decision Rules

Anti-Patterns

• Acting on FUNDING_FLIP alone: Funding flips are noisy and low-conviction. Only useful as confirming signal.
• Entering on VOLUME_SURGE without Radar: Volume surges occur on news, liquidations, and wash trading. 30% are false positives without Radar confirmation.
• Ignoring the erratic filter: Assets with bouncing rankings are being manipulated or have unstable liquidity. The erratic filter exists for a reason.
• Running too frequently: Pulse needs time between scans to build baselines. Running every 10s wastes API calls without improving signal quality. Use 60s minimum.

Error Recovery

Composition

Pulse is a sub-component of APEX (runs every tick). Pairs with Radar — Radar identifies high-quality setups, Pulse detects the optimal entry timing via capital flow signals. When used standalone, always cross-check with hl radar once.

Cron Template

# Standalone Pulse scan every 60s during trading hours
* 8-20 * * 1-5 cd ~/agent-cli && hl pulse once --json >> data/pulse/signals.jsonl 2>&1