# Run AI evals from a clean starting state

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

---

## Run AI evals from a clean starting state

ID: MHC-D-RESEARCH-0722 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/run-ai-evals-from-a-clean-starting-state

A hidden file from yesterday can make today's agent look brilliant.

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

### Use when

- You compare prompts, skills, agents or models across repeated tasks.

### Avoid when

- If production intentionally carries memory across sessions, evaluate that stateful workflow separately rather than pretending every run is cold.

### Explanation

Reset the workspace, conversation and generated artifacts to the intended baseline before each comparable trial. Seed only the state the real workflow is supposed to have. Record versions of model, tools, prompt or skill and important dependencies. This prevents leftover outputs, caches or prior messages from leaking answers into the next run.

### Steps

1. Workspace matches the intended starting state.
2. Prior generated artifacts are removed unless production would keep them.
3. Conversation history is controlled.
4. Model, harness and skill versions are recorded.
5. Random or external dependencies are noted where relevant.

### Example

When testing a research skill, delete the previous report and memory files unless persistent memory is explicitly part of the product being evaluated.

### Check

A trial can be reproduced without depending on residue from a previous run.

### Limits

- If production intentionally carries memory across sessions, evaluate that stateful workflow separately rather than pretending every run is cold.

### Evidence and sources

- supports: AI Engineer skill-eval guidance recommends clean workspaces and repeated trials so hidden artifacts or prior messages do not contaminate comparisons. — RS-FD96DA85C7B10F5A. Perfect isolation may be unrealistic for production workflows; the eval should represent intended starting state. (Test cleanly and repeat)
- RS-FD96DA85C7B10F5A: Don't Ship Skills Without Evals — https://ai.engineer/talks/0vphxNt4wyk-dont-ship-skills-without-evals

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/ablate-a-skill-before-you-trust-it
