jaguar-strategy（捷豹战略）

🐆 JAGUAR v3.2 — Striker-Only

Violent explosions only. DSL manages exits.

v3.2 changelog (fleet-fix batch 4)

• STRIKER_MIN_RANK_JUMP lowered 15 → 10. 0 events fired in 10,239 evaluations under the prior threshold — signal was unreachable in the current market regime. Lowering the jump floor re-engages Striker.

⛔ CRITICAL AGENT RULES

RULE 1: Install path is /data/workspace/skills/jaguar-strategy/

RULE 2: THE SCANNER DOES NOT EXIT POSITIONS

RULE 3: MAX 2 POSITIONS at a time

RULE 4: Scanner output is AUTHORITATIVE

RULE 5: Verify runtime is installed on every session start

Run openclaw senpi runtime list. Runtime must be listed. The position tracker and DSL exit are handled by the plugin runtime.

RULE 6: Never retry timed-out position creation

If create_position times out, check clearinghouse state. If position exists, the position tracker will pick it up automatically. If not, wait for next scan.

RULE 7: Never modify parameters

RULE 8: 120-minute per-asset cooldown

What Changed From v1.0

v1.0 Post-Mortem

• ZEC score 6 (Stalker): -$97, ran 28 hours with no DSL
• WLD score 6 (Stalker): +$5, ran 28 hours with no DSL
• ADA score 7 (Stalker): -$3, ran 28 hours with no DSL
• HYPE score 11 (Striker): -$35, DSL worked correctly (clean floor hit)
• SOL score 10 (Striker): -$138, ran 10 hours, DSL crashed on missing 'size'

The ONLY trade with working DSL (HYPE) lost $35 instead of $138. With DSL, losses are bounded. Without DSL, they compound until manual intervention.

Exit Management

DSL exit is handled by the plugin runtime via runtime.yaml. The position_tracker scanner auto-detects position opens/closes on-chain. See runtime.yaml for configuration details.

Monitor positions:

• openclaw senpi dsl positions — list all DSL-tracked positions
• openclaw senpi dsl inspect <ASSET> — full position details

Runtime Setup

Step 1: Set your strategy wallet address in runtime.yaml:

sed -i 's/${WALLET_ADDRESS}/<STRATEGY_WALLET_ADDRESS>/' /data/workspace/skills/jaguar-strategy/runtime.yaml

Replace <STRATEGY_WALLET_ADDRESS> with the actual wallet address.

Step 2: Set telegram chat ID for notifications:

sed -i 's/${TELEGRAM_CHAT_ID}/<CHAT_ID>/' /data/workspace/skills/jaguar-strategy/runtime.yaml

Replace <CHAT_ID> with the actual Telegram chat ID.

Step 3: Install the runtime:

openclaw senpi runtime create --path /data/workspace/skills/jaguar-strategy/runtime.yaml

Step 4: Verify:

openclaw senpi runtime list

Bootstrap Gate

On EVERY session start, check config/bootstrap-complete.json. If missing:

1. Read the senpi-trading-runtime skill: cat /data/workspace/skills/senpi-trading-runtime/SKILL.md — this provides all CLI commands for runtime management and DSL position inspection.
2. Verify Senpi MCP
3. Set wallet in runtime.yaml: sed -i 's/${WALLET_ADDRESS}/ACTUAL_ADDRESS/' /data/workspace/skills/jaguar-strategy/runtime.yaml
4. Set Telegram in runtime.yaml: sed -i 's/${TELEGRAM_CHAT_ID}/CHAT_ID/' /data/workspace/skills/jaguar-strategy/runtime.yaml
5. Install runtime: openclaw senpi runtime create --path /data/workspace/skills/jaguar-strategy/runtime.yaml
6. Verify runtime installed: openclaw senpi runtime list
7. Remove old DSL cron (if upgrading): run openclaw crons list, delete any cron containing dsl-v5.py via openclaw crons delete <id>
8. Create scanner cron (3 min, main)
9. Write config/bootstrap-complete.json
10. Send: "🐆 JAGUAR v3.2 online. Striker-only scanner (rank-jump ≥ 10). DSL managed by plugin runtime. Silence = no explosions."

If bootstrap exists, still verify runtime and scanner cron on every session start.

License

MIT — Built by Senpi (https://senpi.ai).

Skill Attribution

When creating a strategy, include skill_name and skill_version in the call. See references/skill-attribution.md for details.