---
title: "Bounds, brakes and the stop control"
description: "Each lane runs inside a scope you set, every new behavior has a kill switch, and you can brake one lane or the whole fleet."
url: "https://docs.octo.ad/agents/bounds-brakes-stop/"
id: "agents/bounds-brakes-stop"
type: "concept"
audience: "admin"
dateModified: "2026-11-06"
productArea: "agents at work"
keywords: ["bounds", "brakes", "kill switch"]
---

# Bounds, brakes and the stop control

> Each lane runs inside a scope you set, every new behavior has a kill switch, and you can brake one lane or the whole fleet.

## Bounds

Each lane runs inside the scope you set: which systems it may touch, what it may change, and which moves need a person.

## Brakes and the stop control

You name who may switch it off; on the first steps that is the decision owner and IT. Autonomy is set per lane, and new automation runs in shadow first: it records what it would have done and does nothing outside, with a decision date and a kill switch. You can brake one lane or the whole fleet. Every approval is logged, so you can see what it did.

## Autonomy control, by category

- **What the category typically offers:** Frameworks offer a human-in-the-loop hook; automation is on or off per flow.
- **What OCTOPUS does:** Autonomy is set per lane. New behavior runs in shadow first, with a decision date and a kill switch. Brake the whole fleet or one lane.
- **Question to ask any vendor:** Show the autonomy setting for one lane and the kill switch for one new behavior.