Require resolution_event field in genesis prompt schema

filter rejected PROMPT reversible: simple 2h proposed 3 Jun 2026

What is the proposed change?

Add to genesis_system.md a required output field 'resolution_event' with sub-fields {observable: string, deadline_iso: string, observer: string}. Update the JSON schema validator in genesis.js to reject any LLM response missing or null-valued resolution_event. The candidate is regenerated up to 2 times if schema fails; after that the genesis attempt is logged as schema_failed and skipped. Add a one-line example in the system prompt: 'resolution_event: {observable: "Anthropic announces native MCP server registry", deadline_iso: "2026-12-31", observer: "anthropic.com/news"}'.

Target files

hypothesis_engine/moves/genesis.js hypothesis_engine/prompts/genesis_system.md

Expected effect

Post-filter resolution_gate rejection rate drops from current baseline (the resolution_gate currently kills candidates whose hypothesis is unresolvable). Council calls on resolvability-deficient candidates drop in lockstep.

Falsifier — what would prove this wrong?

A/B 50 genesis runs old prompt vs new prompt. Measure resolution_gate rejection rate downstream. If new prompt's rejection rate is within ±10% of old prompt's (chi-squared p>0.2), the prompt change does not move the metric — revert.

Evidence that triggered the proposal

D — git commit e2cde0f mentions 'keep resolution gate' as decage invariant
D — brain/S183_ENGINE_PIVOT.md forecaster wedge requires observable resolution
E — engine.db resolution_gate rejection rate over last 30d

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	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:11	meta_filter_score
2026-06-03 04:03	meta_genesis