# Re-test old harness rules when the model changes

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Re-test old harness rules when the model changes

ID: MHC-D-RESEARCH-0713 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/re-test-old-harness-rules-when-the-model-changes

Yesterday's workaround can become tomorrow's tax.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A workflow has accumulated scaffolding, retries or context-reset tricks around an older model.

### Avoid when

- Change one component at a time where possible; removing several together can hide interactions and make regression diagnosis ambiguous.

### Explanation

After a material model or harness upgrade, rerun representative evals while removing or simplifying one workaround at a time. Keep a component only if it still improves quality, reliability, cost or recovery. Do not preserve elaborate context resets, prompt rituals or reviewer loops merely because an earlier model needed them.

### Steps

1. Choose a representative baseline suite.
2. Remove or simplify one harness component.
3. Run repeated comparable trials.
4. Inspect quality, cost and failure mode changes.
5. Keep, revise or retire the component.

### Example

A forced context reset that prevented drift on an older coding model may be unnecessary after a model upgrade with stronger long-context behavior.

### Check

Every expensive harness component has current evidence of value on the model you actually run.

### Limits

- Change one component at a time where possible; removing several together can hide interactions and make regression diagnosis ambiguous.

### Evidence and sources

- supports: Anthropic reports that context-reset scaffolding that helped one model could be removed for a stronger later model, illustrating that harness components should be re-tested as models change. — RS-4CF3167EB387E6BE. Do not infer that resets or compaction are broadly obsolete; test on the actual model and task. (Context resets and later simplification)
- RS-4CF3167EB387E6BE: Harness design for long-running application development — https://www.anthropic.com/engineering/harness-design-long-running-apps

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/re-benchmark-ai-when-the-model-or-task-changes
