# Keep a human baseline for important AI tasks

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 a human baseline for important AI tasks

ID: MHC-D-RESEARCH-0372 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/keep-a-human-baseline-for-important-ai-tasks

Without a baseline, 'better with AI' can mean 'faster than I remember.'

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

### Use when

- AI output looks impressive but you do not know whether it actually improves the work.

### Avoid when

- Small samples are directional and can be biased by case selection; do not convert them into universal productivity claims.

### Explanation

For a small representative sample, compare AI-assisted performance with the current human or non-AI method using the same acceptance criteria. Measure quality, time and review effort separately. Repeat only often enough to detect meaningful capability changes; this is a calibration tool, not permanent double work.

### Steps

1. The same task and acceptance criteria are used in both conditions.
2. Quality is judged independently from speed.
3. Review or correction time is included in the AI-assisted cost.
4. Cases include at least one known edge condition.
5. The comparison is saved with the model and workflow version.

### Example

Compare five real specification summaries produced with and without AI, including correction time and factual misses.

### Check

You can say what AI changed relative to the current method instead of comparing it with an imagined baseline.

### Limits

- Small samples are directional and can be biased by case selection; do not convert them into universal productivity claims.

### Evidence and sources

- supports: The 2026 Organization Science field experiment found strong AI-assisted gains on a set of tasks within the tested capability frontier but lower correctness on a selected complex task outside that frontier. — RS-22FF68CA0BFD77A0. The experiment used a particular model generation and consulting task set; current frontier location must be re-estimated for today's model and workflow. (Abstract and results)
- contextualizes: Across the recent field and lab studies, AI's effect on speed and quality varies by task and workflow, so a productivity claim should measure these outcomes separately rather than assume faster means better. — RS-22FF68CA0BFD77A0. This synthesis draws a practical measurement implication from heterogeneous studies; it is not a pooled meta-analysis. (Abstract and task-contingent results)
- RS-22FF68CA0BFD77A0: Navigating the Jagged Technological Frontier: Field Experimental Evidence of the Effects of Artificial Intelligence on Knowledge Worker Productivity and Quality — https://pubsonline.informs.org/doi/10.1287/orsc.2025.21838

No review details supplied.
