Principle

Use versioned artifacts as the meeting place for humans and agents

Shared chat is a poor substitute for shared state.

About 1 min read

Before you use it

Use when
  • Humans and several agents need to coordinate work without staying in one synchronous conversation.

Keep this limit in mind

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

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

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.

An 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 your result

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

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingUse versioned artifacts as the meeting place for humans and agents

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.

This pattern fits version-controlled work; other domains may need a different shared artifact.

Harness Engineering: How to Build Software When Humans Steer, Agents Execute · GitHub pull requests as broadcast domain

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details