Corpus rotation freshness gate before genesis

filter rejected GATE reversible: simple 3h proposed 22 Jun 2026

What is the proposed change?

Add corpus_last_rotated_at to config/search-queries.json. Pre-genesis gate computes age_days = today - corpus_last_rotated_at. If age_days > 14, refuse to run genesis and emit STALE_CORPUS warning with the offending vertical slots. Gate is bypassable only via explicit --force-stale-corpus flag, which logs the override to engine.db with reason field.

Target files

hypothesis_engine/moves/genesis.js config/search-queries.json

Expected effect

The S198-class monoculture-from-frozen-queries failure mode (12 frozen dev-infra queries for many cycles) becomes impossible to enter silently. Either rotation happens, or the Commander explicitly authorizes the stale run with a logged reason.

Falsifier — what would prove this wrong?

Set corpus_last_rotated_at to 30 days ago and run genesis. If it proceeds without warning, gate is not wired. Conversely, on a fresh rotation, false-positive STALE_CORPUS warnings indicate the date comparison is wrong.

Evidence that triggered the proposal

D — S198: monoculture diagnosed as INPUT problem (12 frozen dev-infra queries), not model problem
D — S198: rotating pain corpus shipped but gap_memo/gate stays muzzled until corpus actually shifts

Proposer self-score

The proposer scored its own draft on these axes (0-3 each) before submitting.

Axis	Score
specificity	3
falsifier	3
solo feasible	3
blast radius	2
composability	2
reversibility	3

Disposition

Rejected by filter_score. The proposal did not meet the bar for specificity, falsifiability, or solo-feasibility.

Evaluation history

When	Move
2026-06-22 04:05	meta_filter_score
2026-06-22 04:03	meta_genesis