Harness Atlas

Two plates from one survey of an agent harness: how it routes a task across roles, and how it keeps whatever model you plug in inside safe bounds.

safe structure active thread rejected step not yet traced

I

Role Topology

A central dispatcher moves one task through five agent roles. Review and fixing are loops: they repeat until the change passes.

scenario

Happy path Fixer loop Reviewer sends back Full storm

transport

speed

0.5× 1× 2×

step 0 / 0

1ARCHdraft the plan—
2WORKERimplement the change—
3EXECUTORSbuild in parallel—
4Dispatchermerge the results—
5REVIEWERcheck against the plan—
6Outcomeapprove, or loop back—

II

Guarded Corridor

Every step is one model call. Two limits hold the run: a wall that keeps the agent in, a shield that keeps the workspace safe. A step that would cross either one is rejected before it runs.

scenario

Clean run Wall block Shield block Retries Model swap

speed

0.5× 1× 2×

step 0 / 0

attempt log

Harness Atlas — a conceptual model drawn from two hand sketches. It shows how the roles fit together and where the limits sit, not a wiring diagram of any one implementation.