edit-manifestlisted

# edit-manifest — Predict-Verify Loop for Harness Edits > Implements two mechanisms from frontier harness research: > - **Change Manifest** (AHE, arXiv:2604.25850): every edit declares a falsifiable prediction; > the next iteration verifies it against actual outcomes. > - **Validation Gate** (SkillOpt, arXiv:2605.23904): candidate edits are accepted only when > the selection-split score strictly improves. Rejected edits are retained as negative > feedback for future proposals — not silently discarded. FH's regression_guard.sh catches backward regressions. edit-manifest closes the forward loop: did the edit actually improve what it claimed to improve? **Boundary vs. verify-bidirectional**: verify-bidirectional is *reactive* — it updates the baseline when the user raises a counter-argument to an AI recommendation. edit-manifest is *predictive* — it records a forward prediction at edit time and verifies it against outcomes later, with no user counter-argument required. Different axes: one responds to challenge, the other tests a self-declared hypothesis. ## Manifest File Location ``` tracks/_meta/edit_manifest.yaml ``` Single append-only file. Entries are never deleted — they accumulate as the harness's edit history and negative-feedback buffer. ## Manifest Entry Format ```yaml - id: em-{YYYY-MM-DD}-{slug} date: YYYY-MM-DD file: plugins/fh-meta/skills/{skill}/SKILL.md # relative to repo root edit_summary: "added 'trigger phrase X' to natural language trigge