Skip to content

Integrate CutoffEnvironment into eval pipeline - #159

Draft
lukeinglis wants to merge 1 commit into
mainfrom
evolve/cutoff-integration
Draft

Integrate CutoffEnvironment into eval pipeline#159
lukeinglis wants to merge 1 commit into
mainfrom
evolve/cutoff-integration

Conversation

@lukeinglis

Copy link
Copy Markdown
Owner

Closes the cutoff integration task.

Changes

  • Import CutoffEnvironment in eval.py and add _apply_cutoff() helper that applies temporal framing using freeze_datetime (falling back to forecast_due_date)
  • Apply _apply_cutoff() to every question in run_eval before dispatching to the forecaster
  • Questions without any date are passed through unchanged
  • Add tests/test_cutoff_integration.py with 10 tests covering:
    • Unit tests for _apply_cutoff (freeze_datetime present/absent, empty background, field preservation, immutability, forecast_due_date fallback)
    • Integration tests verifying temporal framing flows through run_eval end-to-end
  • All 709 existing tests pass, ruff and mypy clean

Apply CutoffEnvironment.prepare_question() to each question before
forecasting, using freeze_datetime (or forecast_due_date as fallback)
to add temporal context framing to question backgrounds.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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