AGENTS AT WORK · 10 A visual series

Same workflow, different runtime

Toggle the runtime below. The blueprint above never moves — only the harness running it changes.

THE BLUEPRINT — STAGES, GATES, ARTIFACTS
Harness

Instructions file

The problem this replaces

Two teams, two invented processes

TEAM A'S PROCESS TEAM B'S PROCESS ≠?

Same delivery work, redrawn twice — because nobody wrote it down as one shared process.

How it works

One blueprint, two machines

BLUEPRINT CLAUDE CODE GITHUB COPILOT
Both harnesses read the same stages and gates — they just speak a different instructions-file format.

If your team switches coding tools next year, the blueprint doesn't get redesigned — only the harness underneath it does.

See it in action

Same ticket, either runtime, same PR

Claude Code: context → plan → build → review → test → ship
GitHub Copilot: context → plan → build → review → test → ship

Same six stages, same gates, same PR shape — word for word identical.

So what

The pipeline is the asset — the tool under it can be swapped.