Add commander-override capture harness

filter rejected HARNESS reversible: simple 2h proposed 4 Jun 2026

What is the proposed change?

Wrap the existing commander override path with an append-only JSONL logger. On every override, append: {ts, candidate_id, original_kill_reason, override_reason_text, proposal_shape_tags[], filter_axes_at_override[]}. No behavior change to the override path itself — pure observability. Create override_log.jsonl if absent; never reads or rewrites prior entries.

Target files

hypothesis_engine/moves/commander_override.js hypothesis_engine/data/override_log.jsonl

Expected effect

After 14 days, the log enables a one-liner query that would have surfaced the observed 'audit-shaped' cluster (4 overrides clustered on audit-shaped products per S183 traces) in real time. Enables downstream axis-weight tuning informed by override patterns.

Falsifier — what would prove this wrong?

After 30 days of logging, if fewer than 5 overrides total are captured (insufficient signal for clustering), OR if shape-clusters in overrides show no correlation with subsequent graduation rate (r<0.3), the harness produces noise not signal.

Evidence that triggered the proposal

E — S183 trace: 4 commander overrides clustered on audit-shaped products

Proposer self-score

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

Axis	Score
specificity	3
falsifier	2
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:13	meta_filter_score
2026-06-04 04:03	meta_genesis