Add commander_override_reason to evidence loop in genesis

filter rejected CORPUS reversible: simple 5h proposed 6 Jun 2026

What is the proposed change?

Extend digest_ingest.js to read the last 14 days of commander overrides (engine.db: meta_proposals WHERE commander_override IS NOT NULL) and emit each as a Corpus-E row tagged source='commander_override' with fields {proposal_title, original_verdict, override_verdict, override_reason}. Modify genesis.js system prompt to include these rows under a new heading 'Prior commander overrides (the human disagreed with the engine here)' BEFORE corpus T. No prompt template variable changes elsewhere.

Target files

meta_engine/moves/digest_ingest.js meta_engine/moves/genesis.js

Expected effect

Over the next 7 cycles, proposals citing source_corpus='commander_override' rows in their evidence field appear in >=20% of generated candidates, AND commander_override rate on graduated proposals drops from current 4/21 (~19%) to <=10% — i.e. the engine learns from its disagreements.

Falsifier — what would prove this wrong?

If commander_override rate on graduated proposals does not drop OR stays statistically indistinguishable over 14 cycles, the feedback loop is not closing and the corpus injection is decorative.

Evidence that triggered the proposal

E — commander_overrides_7d: 3 KILL, 1 DEFER
D — brain/S177_FOUNDRY_SENTINEL_DOCTRINE.md (calibration feedback)

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