# Use versioned artifacts as the meeting place for humans and agents

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

---

## Use versioned artifacts as the meeting place for humans and agents

ID: MHC-D-RESEARCH-0723 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/use-versioned-artifacts-as-the-meeting-place-for-humans-and-agents

Shared chat is a poor substitute for shared state.

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

### Use when

- Humans and several agents need to coordinate work without staying in one synchronous conversation.

### Avoid when

- Not every task belongs in Git; choose an equivalent versioned or auditable artifact for documents, data or operations.

### Explanation

Coordinate through artifacts that can be inspected and versioned: pull requests, issues, decision records, test results or change sets. Let agents post work where humans and other agents can review it asynchronously. Keep the artifact self-contained enough that a reviewer does not need the originating chat to understand the change, rationale and checks.

### Example

An agent opens a pull request with the diff, test evidence and remaining risk; a second agent or human reviews that artifact rather than joining the first agent's context.

### Check

A new reviewer can take useful action from the shared artifact alone.

### Limits

- Not every task belongs in Git; choose an equivalent versioned or auditable artifact for documents, data or operations.

### Evidence and sources

- supports: AI Engineer harness guidance presents pull requests as an asynchronous shared interface where human and agent contributors can review and coordinate without sharing one live conversation. — RS-3DB1894302E64FC3. This pattern fits version-controlled work; other domains may need a different shared artifact. (GitHub pull requests as broadcast domain)
- RS-3DB1894302E64FC3: Harness Engineering: How to Build Software When Humans Steer, Agents Execute — https://ai.engineer/talks/am_oeAoUhew-harness-engineering

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