Add resolver clause requirement to genesis prompt

filter rejected PROMPT reversible: simple 1h proposed 4 Jun 2026

What is the proposed change?

Append a new section 'RESOLVER CLAUSE (REQUIRED)' to the genesis prompt instructing the model to terminate every hypothesis with a literal 'Resolver:' line naming the specific public event AND date/window that would validate or invalidate it. Include three in-prompt examples: a SEC filing event, a published benchmark score release, a product-launch press event. Keep diff confined to genesis.md; no code changes.

Target files

hypothesis_engine/prompts/genesis.md

Expected effect

Resolver-clause presence rate in raw genesis output rises from current baseline (~30-50% per S184 record) to ≥85% within first 50 post-change generations. Pairs with the gate proposal — prompt change reduces gate rejection rate.

Falsifier — what would prove this wrong?

Sample 50 hypotheses pre-change and 50 post-change. If resolver-clause presence rate does not rise by ≥30 percentage points, the prompt change is ineffective and should be reverted.

Evidence that triggered the proposal

E — S184 forecaster v1 calibration record: ~40-55% unscoreable for missing resolver
D — commit e2cde0f decage genesis: resolution gate already retained

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	3
composability	3
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-12 04:14	meta_filter_score
2026-06-04 04:03	meta_genesis