Skip to content

Hardcode freshness config for aajtak.in#76

Merged
prasjaiswal merged 1 commit intomainfrom
feat/hardcode-aajtak-freshness
Feb 18, 2026
Merged

Hardcode freshness config for aajtak.in#76
prasjaiswal merged 1 commit intomainfrom
feat/hardcode-aajtak-freshness

Conversation

@prasjaiswal
Copy link
Collaborator

Summary

  • Add optional recency_config parameter to Ranking.rank() so callers can pass freshness config directly, bypassing Cosmos DB site_config lookup
  • Aajtak handler now uses hardcoded AAJTAK_RECENCY_CONFIG with freshness always enabled (recency_weight=1.0)
  • Other callers (DefaultAskHandler, etc.) are unaffected — they don't pass the parameter, so ranking falls back to the existing Cosmos DB lookup

Test plan

  • make check passes (ruff, pyright 0 errors, 295 tests)
  • Verify aajtak.in queries still return freshness-boosted scores

🤖 Generated with Claude Code

Add optional recency_config parameter to Ranking.rank() so callers can
pass freshness config directly instead of relying on Cosmos DB site_config
lookup. The aajtak handler now uses hardcoded AAJTAK_RECENCY_CONFIG with
freshness always enabled (recency_weight=1.0), removing the dependency on
the Cosmos DB site_configs entry.

Other callers (DefaultAskHandler, etc.) are unaffected — they don't pass
the parameter, so ranking falls back to the existing Cosmos DB lookup.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@prasjaiswal prasjaiswal merged commit 26d431c into main Feb 18, 2026
5 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