# Give parallel agents independent tests and merge boundaries

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

---

## Give parallel agents independent tests and merge boundaries

ID: MHC-D-RESEARCH-0717 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/give-parallel-agents-independent-tests-and-merge-boundaries

Parallel workers need an oracle and a border, not just separate chat windows.

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

### Use when

- Several agents will edit one codebase or shared project concurrently.

### Avoid when

- Architectural changes that cross every slice may require centralized design before parallel implementation.

### Explanation

Give each agent an isolated workspace, a defined ownership slice or merge contract and a test that can be run without asking another agent what happened. Integrate through versioned artifacts or commits, then run cross-slice tests after merge. Use shared state for coordination, not as permission for every worker to rewrite everything.

### Steps

1. Each worker has an isolated change surface or explicit ownership.
2. Each slice has an independent acceptance test.
3. Results are committed or versioned before integration.
4. Cross-slice tests run after merge.
5. Conflicts route to a deliberate integration step.

### Example

Three agents improve separate adapters in isolated branches, each with adapter tests; a fourth integration step runs the shared end-to-end suite.

### Check

One worker's failure or rollback does not erase another worker's validated progress.

### Limits

- Architectural changes that cross every slice may require centralized design before parallel implementation.

### Evidence and sources

- supports: The same experiment used isolated workspaces, tests and an upstream repository to let agents work concurrently while reducing accidental overwrite and giving progress an external oracle. — RS-7CFA09733D80048C. Isolation does not remove semantic merge conflicts; overlapping architecture changes still need coordination. (Parallel workspaces, pushes and test harness)
- RS-7CFA09733D80048C: Building a C compiler with a team of parallel Claudes — https://www.anthropic.com/engineering/building-c-compiler

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/let-subagents-write-durable-artifacts-instead-of-relaying-everything-through-the-coordinator
