Skip to content

Separate 24h-volume floor for shadow forecasts (R209) - #6

Merged
markb-1 merged 1 commit into
mainfrom
claude/shadow-forecast-floor
Nov 1, 2026
Merged

markb-1 merged 1 commit into
mainfrom
claude/shadow-forecast-floor

Conversation

@markb-1

@markb-1 markb-1 commented Nov 1, 2026

Copy link
Copy Markdown
Owner

Why

With the default mandate (economics / weather / non-US politics allowed) and the $5k 24h-volume floor, almost no market can be forecast: a real agent session on 2026-11-01 had all four forecasts refused, and the Mac test found the same. No (category, horizon) bucket can then reach the 30 scored forecasts it needs to earn trading rights. Lowering min_liquidity_usd would fix forecasting but also loosen the floor for live orders.

What

  • mandate.yaml markets.min_forecast_volume_usd: optional, must be ≤ min_liquidity_usd. When set, submit_forecast needs only that much 24h volume. Orders are unchanged: the risk engine still requires the trading floor (the larger of the mandate's and limits.yaml per_market.min_liquidity_usd). Unset = exactly today's behaviour. Opt-in: the default and example mandate.yaml carry it commented out. Config-change effect is neutral (it doesn't raise trading risk).
  • Agent search flags (search_markets): markets between the floors are flagged forecast only (orders need min_liquidity_usd); below the forecast floor no forecast either. inMandateOnly still drops both.
  • Forecast Executor: skips markets whose 24h volume (ctx.polymarket.getMarket) is below ctx.risk.getMandateSummary().minLiquidityUsd, and cancels its bids there. Without this it would keep quoting forecast-only markets, collect liquidity rejections and trip the rejection cooldown (R193), blocking its good quotes too. Unknown volume is still left to the risk engine; backtests (no such calls) are unchanged.
  • Agent: system prompt v6 and guide §3 explain forecast-only markets. Ledger page help text, docs/guide/operations.md and strategies.md, PROGRESS decision R209 and log entry.

Behaviour change to note

The executor skip also applies to existing forecasts whose market volume has fallen below the trading floor since they were made: the executor now cancels its resting bids there instead of leaving them. Template source changed, so (as with every template change) running executor bots go back to paper on upgrade.

Tests

  • New: config (optional key, ≤ min_liquidity_usd), ledger gate with and without the key, search flags with and without it, executor skip / cancel plus the unchanged cases (volume at the floor, unknown volume, no mandate summary).
  • Locally: npm run typecheck clean; full suite SKIP_NETWORK_TESTS=1 npx vitest run 1241 passed; ESLint 0 errors (excluding a leftover local worktree under .claude/).

To use it

Risk → Mandate → markets.min_forecast_volume_usd: 1000 (for example), and add the categories you want shadow-forecast to categories.later.

🤖 Generated with Claude Code

With an economics-only mandate and the $5k 24h-volume floor nearly nothing
can be forecast, so no bucket can reach the 30 scored forecasts it needs.
Lowering min_liquidity_usd would also loosen live orders.

- mandate.yaml markets.min_forecast_volume_usd (optional, at most
  min_liquidity_usd; unset keeps today's single floor): submit_forecast
  needs only that 24h volume. Orders keep the trading floor; the risk
  engine is unchanged. Opt-in: commented out in the default and example
  files; config change effect neutral.
- search_markets flags markets between the floors "forecast only" and
  below the forecast floor "no forecast either".
- Forecast Executor skips markets whose 24h volume is below the trading
  floor (ctx.risk.getMandateSummary + ctx.polymarket.getMarket) and
  cancels its bids there, instead of collecting liquidity rejections that
  would trip the rejection cooldown. Unknown volume and backtests
  (no calls) behave as before.
- Agent system prompt v6 and guide §3, Ledger page help text, guides,
  PROGRESS R209 and log.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@markb-1
markb-1 merged commit 80ec7f3 into main Nov 1, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant