Add v2_a11 status_quo_displacement_ease axis to filter_score.js v2 rubric

filter rejected AXIS reversible: simple 4h proposed 21 May 2026

What is the proposed change?

After the existing v2 axis definitions (A1-A10), add a new scoring function score_v2_a11_status_quo_displacement_ease that scores 0-3. Score 0: hypothesis requires displacing an entrenched incumbent with regulatory lock-in, multi-year contracts, or deep workflow integration (e.g., audit/compliance tooling with SOC2 certifications). Score 1: switching costs exist but are moderate (annual SaaS contracts, data is exportable). Score 2: status quo is spreadsheets, email, or manual processes with no contractual lock-in. Score 3: no incumbent exists (new category) or incumbent is demonstrably broken and users are actively seeking alternatives. Wire into composite v2 score with weight 1.0 alongside existing v2 axes. The v2_a11 column already exists in the DB schema (s112 migration) — no migration required.

Target files

hypothesis_engine/moves/filter_score.js

Expected effect

The 3 commander-KILLed proposals in the last 7 days (AI control, ClaimGate, AI Tool Verification for Agencies) would score 0 on this axis due to entrenched audit/verification incumbents with regulatory switching costs. Retrospective on 43 S157 NBJ candidates should show statistically significant correlation (p<0.05, Mann-Whitney U) between axis score and ROBUST/MIXED/FRAGILE classification.

Falsifier — what would prove this wrong?

Run the 43 S157 candidates through the new axis function. If the score distribution does not produce a statistically significant split between ROBUST and FRAGILE candidates (p<0.05), or if ROBUST and FRAGILE candidates score identically on the axis, the axis is not capturing a signal that correlates with existing quality judgments and must be redesigned.

Evidence that triggered the proposal

Corpus D: brain/S161_LAYER_4_LENS_SET_SYNTHESIZED.md — lens #3 status_quo_displacement_ease identified as 'most likely missing dimension' by both lens reviewers; explicitly noted as absent from filter_score.js v2 axes
Corpus E: Commander overrides last 7d — 3 of 4 KILLs were audit/verification incumbents (AI control, ClaimGate, AI Tool Verification for Agencies) with regulatory switching costs not caught by any existing filter axis
Corpus D: brain/META_ENGINE_S158_ROUND2_SYNTHESIS.md — v2_a11 column created by s112 migration; scoring function never wired in filter_score.js production despite column existing

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	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-05-21 04:15	meta_filter_score
2026-05-21 04:15	meta_genesis