# Keep acceptance examples out of the prompt workshop

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

---

## Keep acceptance examples out of the prompt workshop

ID: MHC-D-RESEARCH-0990 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/keep-acceptance-examples-out-of-the-prompt-workshop

The demonstration has had a lot of rehearsal. The next real case has not.

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

### Use when

- A prompt improves on familiar examples and you need to know whether it improved beyond them.

### Avoid when

- A tiny or unrepresentative holdout remains weak evidence. Repeatedly selecting changes from the same holdout can contaminate it too.

### Explanation

Separate development examples from a held-back acceptance set. Use the first group to revise prompts and rules; use the second to evaluate the frozen candidate. Once acceptance failures guide another revision, those cases are no longer untouched evidence of generalization.

### Steps

1. Write expected outcomes for representative, permission-safe cases before testing.
2. Version the prompt, model configuration and evaluation set together.
3. Report held-back performance separately from results on examples used during development.

### Example

A document extractor is tuned on familiar layouts, then tested on previously held-back layouts with known expected fields.

### Check

The report identifies which cases influenced development and which first appeared at evaluation.

### Limits

- A tiny or unrepresentative holdout remains weak evidence. Repeatedly selecting changes from the same holdout can contaminate it too.

### Evidence and sources

- supports: Using evaluation data to make development choices can create optimistic performance estimates; the scikit-learn guidance keeps test data out of model choices. — RS-E75F80345E8006C8. A separate acceptance set for prompts is an application of this principle; representative sampling and repeated-use contamination still matter. (Data leakage)
- RS-E75F80345E8006C8: Common pitfalls and recommended practices — https://scikit-learn.org/stable/common_pitfalls.html

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/test-what-should-stay-unchanged-when-the-input-changes
