Familiar Git collaboration, rebuilt for concurrency.
Switchyard behaves like a Git host in the simple case and reveals Agent-native machinery only when concurrent work, automation, review complexity or risk actually require it.
Start with ordinary Git
| You expect | Switchyard gives you |
|---|---|
| owner/repository identity | User and organisation namespaces, public/private repository metadata and familiar repository pages. |
| clone / fetch / push | Normal Git commands against the Cloudflare Artifacts remote shown under the repository Code menu. |
| source browsing | Branch selector, breadcrumbs, syntax highlighting, README rendering, images and line anchors. |
| history | Commits, branches, tags and compare/diff surfaces. |
| issues/tasks | Work items with body, status, assignee and comments. |
| Pull Requests | Conversation, commits, files, checks and progressive Switchyard details. |
| settings/access | User/org/repository settings, collaborators, teams and policy surfaces. |
Then add concurrency explicitly
Work: improve repository search
├─ Attempt A · human
├─ Attempt B · implementer Agent
└─ Attempt C · alternate approach
│
├─ checks + Review Findings
├─ preview against current canonical
└─ Integration Queue
└─ Cloudflare Artifacts main
Attempts are isolated candidate executions under one Work item. Humans can ignore them entirely for simple tasks; Agent-heavy teams can run multiple approaches without sharing a branch or racing to overwrite canonical.
The collaboration model
| Layer | Purpose | Authority |
|---|---|---|
| Work | Human-facing intent/task/issue. | Trestle coordination state. |
| Attempt | Isolated candidate execution and provenance. | Coordination in Trestle + real branch/ref state in Artifacts. |
| Pull Request | Familiar review/integration proposal. | Switchyard metadata around real Git source/base refs. |
| Integration Queue | Fresh, ordered, policy-gated canonical movement. | Control plane decides; Git/Artifacts performs the actual ref update. |
Why isolation is the point
Parallel without shared-branch races
Two Agents can attempt the same Work independently. Their differences become reviewable candidates, not an accidental last-writer-wins sequence.
Provenance around real Git
Work → Attempt → execution → PR → queue → ref update gives context around commits without replacing Git history.
Risk changes autonomy
Policy can deny files, cap workflow budgets or require approval for higher-risk integration while leaving low-risk repositories simple.
Human and Agent editing are deliberately different
A human in the browser editor can save a recoverable draft without touching Git, ask an Agent to propose a change against that draft revision, inspect the diff and explicitly commit. A formal autonomous Attempt may create commits on its own isolated branch. Both paths are stale-safe and neither grants an Agent canonical-write authority.
Where the data lives
Cloudflare Artifacts Trestle
-------------------- -------
Git objects Work / Attempts
commits + branches PR coordination
canonical refs workflow steps
clone / fetch / push findings / queue / policy / audit
Switchyard control plane
connects the two under auth + policy