Environment

The work an agent produces is only as trustworthy as the harness it runs inside. Environment is that harness: the lint and test gates a change has to clear before it counts as done, the branch or worktree isolation that keeps two parallel runs from overwriting each other, the handoff points that force a checkpoint before work moves on. When those checks are built into the environment itself rather than left to whoever is paying attention, mistakes get caught where they happen instead of in a reviewer's lap. Your team stops finding out about a broken build or a colliding branch after the fact, and quality stops being something you pay for downstream: fewer surprises, less cleanup, parallel agents that stay out of each other's way.

What Environment owns is everything around the work, not the work itself: the gates, the isolation, the enforced checkpoints. What an agent is allowed to reach is Capability, and which calls it makes on its own is Delegation. Environment is where the lines those two draw get backed by the system instead of taken on trust. The question it leaves you with is how much of this harness lives in one engineer's local setup, and how much is set up once and shared, so the same checks meet every run.

Exploratory

Engineers run the agent bare: no wrapper, no checks on what comes out.

Enables

A fast start, and a clear look at where the bare run actually goes wrong. The failures you catch by hand are the gates a shared harness later gets built to enforce.

Deficiencies

No guardrails, bad output ships unchecked, behavior varies turn to turn, and parallel runs collide on shared files and branches.

Cost to maintain

Humans catching every failure downstream.

Expert-led

One engineer has built their own scripts, wrappers, and skills into a working setup.

Enables

A shaped space for that person, with repeatable runs and checks that catch the obvious failures.

Deficiencies

It lives on their machine and is not portable, everyone else runs raw, and their config drifts undocumented.

Cost to maintain

Their time building and tending it.

Documented

The useful scripts and config are written up and shared, but each person assembles their own harness from them.

Enables

A common toolkit. New people can stand up a working environment from the docs.

Deficiencies

Still hand-assembled. Versions drift between people, and guardrails depend on who set them up.

Cost to maintain

Documenting the setup, plus everyone keeping their own copy current.

Structural

One shared, versioned environment everyone operates inside, with validation and guardrails enforced and parallel agents isolated into their own worktrees with clear ownership.

Enables

Every run shaped the same way, gates that cannot be skipped, and a harness that survives turnover.

Deficiencies

Upfront engineering, rigidity if the harness is wrong, and changes that need coordination across everyone inside it.

Cost to maintain

Building and versioning the shared environment, plus tuning guardrails as the work changes.

Environment rarely stands alone. Where it overlaps a sibling discipline, an investment on one side quietly depends on the other. The Control domain page lays these out in full.

• Environment and Delegation

  Delegation draws the line on what the agent decides alone; Environment is the harness that catches the call when it goes wrong. How far you can safely move that line depends on what the system behind it catches: solid gates let you delegate more, because a bad decision meets a test failure instead of a customer.

  Widen the line with no harness and every handed-over call rides on the agent being right; harden the harness but never widen the line and the safety net goes unused.

• Environment and Capability

  Every tool you connect through Capability raises the stakes Environment has to hold. A wider reach is more the agent can break, and the harness of gates and isolation is what turns that reach into throughput instead of cleanup.

  Grow the surface faster than the guardrails and each new connection is one more unwatched way to cause damage; grow the guardrails with no new reach and you have hardened a cage around work the agent cannot do anyway.