Add v2_a11 resolver_specificity axis to filter_score

filter rejected AXIS reversible: simple 3h proposed 4 Jun 2026

What is the proposed change?

Add eleventh axis `v2_a11_resolver_specificity` after the existing 10-axis block (filter_score.js line ~240). Scoring rubric 0-3: 0 = no resolver named; 1 = vague ('will be observable'); 2 = specific public event named but no time window; 3 = specific event AND concrete date/window. Composite score formula updates from sum/30 to sum/33; weight = 1.0 (parity with existing axes). Add axis to filter_score JSON output schema.

Target files

hypothesis_engine/moves/filter_score.js

Expected effect

On the S183 graduated-candidate set (n=43), pre-pivot speculation-shaped hypotheses score 0-1 (mean ≈ 0.7); post-pivot forecaster-shaped hypotheses score 2-3 (mean ≈ 2.4). Composite-score spread of ≥1.5 points between cohorts.

Falsifier — what would prove this wrong?

Score the S183 set. If mean v2_a11 score for the 14 forecaster-pivot-era hypotheses does not exceed the mean for the 29 pre-pivot hypotheses by ≥1.0 points, OR if v2_a11 correlates r<0.4 with forecaster v1 grader's resolvability rating, the axis is misdesigned.

Evidence that triggered the proposal

D — brain/V2_FILTER_DESIGN_v2.3.md (10-axis schema)
E — S184 forecaster v1 calibration record

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