From 7ed12dee05e5facdd375caef99f51d286802e8eb Mon Sep 17 00:00:00 2001
From: seveibar <seveibar@gmail.com>
Date: Thu, 30 Jul 2026 22:26:30 -0700
Subject: [PATCH 1/3] Move breakout pours into routing scope

---
 docs/elements/breakout.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/elements/breakout.mdx b/docs/elements/breakout.mdx
index 4d35f5f4..307ad476 100644
--- a/docs/elements/breakout.mdx
+++ b/docs/elements/breakout.mdx
@@ -89,8 +89,6 @@ export default () => (
     minViaHoleDiameter="0.2mm"
     minViaPadDiameter="0.5mm"
   >
-    <copperpour layer="inner1" connectsTo="net.GND" />
-    <copperpour layer="inner2" connectsTo="net.VCC" />
     <breakout
       name="BGA_BREAKOUT"
       width="14mm"
@@ -103,6 +101,8 @@ export default () => (
         ADDRESS: "center_left",
       }}
     >
+      <copperpour layer="inner1" connectsTo="net.GND" />
+      <copperpour layer="inner2" connectsTo="net.VCC" />
       <chip
         name="U1"
         footprint="bga100_grid10x10_p0.8mm_pad0.35mm_circularpads"

From f24d91e7f1e3a498e08ea246f5cff59c3369fb33 Mon Sep 17 00:00:00 2001
From: Severin Ibarluzea <seve700@gmail.com>
Date: Fri, 31 Jul 2026 11:28:11 -0700
Subject: [PATCH 2/3] Document breakout as a transparent routing directive

---
 docs/elements/breakout.mdx | 24 +++++++++++++++---------
 1 file changed, 15 insertions(+), 9 deletions(-)

diff --git a/docs/elements/breakout.mdx b/docs/elements/breakout.mdx
index 307ad476..196393c4 100644
--- a/docs/elements/breakout.mdx
+++ b/docs/elements/breakout.mdx
@@ -6,11 +6,13 @@ description: >-
 
 ## Overview
 
-A `<breakout />` is similar to a [`<group />`](./group.mdx) but is meant for situations where you
-want to guide the autorouter on where connections should exit the group. Inside
-a breakout you can place [`<breakoutpoint />`](./breakoutpoint.mdx) elements to
-define explicit exit locations, or let tscircuit generate breakout points for
-connections that leave the breakout.
+A `<breakout />` is a transparent routing container similar to a
+[`<group />`](./group.mdx). It does not create a subcircuit, selector scope, or
+private net scope. Instead, its routing properties guide the autorouter on where
+connections should exit the region. Inside a breakout you can place
+[`<breakoutpoint />`](./breakoutpoint.mdx) elements to define explicit exit
+locations, or let tscircuit generate breakout points for connections that leave
+the breakout.
 
 import CircuitPreview from "@site/src/components/CircuitPreview"
 
@@ -89,6 +91,8 @@ export default () => (
     minViaHoleDiameter="0.2mm"
     minViaPadDiameter="0.5mm"
   >
+    <copperpour layer="inner1" connectsTo="net.GND" />
+    <copperpour layer="inner2" connectsTo="net.VCC" />
     <breakout
       name="BGA_BREAKOUT"
       width="14mm"
@@ -101,8 +105,6 @@ export default () => (
         ADDRESS: "center_left",
       }}
     >
-      <copperpour layer="inner1" connectsTo="net.GND" />
-      <copperpour layer="inner2" connectsTo="net.VCC" />
       <chip
         name="U1"
         footprint="bga100_grid10x10_p0.8mm_pad0.35mm_circularpads"
@@ -172,14 +174,18 @@ The breakout uses the fanout autorouter by default, so its fanout controls can
 be set directly on `<breakout />`. `busFanoutDirections` sends each named bus
 toward a specific side.
 
+Because `<breakout />` is transparent, its traces use the same GND and VCC nets
+as the board-level copper pours. The pours do not need to be children of the
+breakout, and no net exposure or separate `<autoroutingphase />` is required.
+
 `fanoutRoutingLayers={["top"]}` reserves the top layer for signal escape. The
 GND and VCC traces have only one component endpoint, so `fanoutPourNetMap`
 drops them to `inner1` and `inner2`. Those plane layers do not need to appear in
 `fanoutRoutingLayers`.
 
 When `fanoutPourNetMap` is omitted, tscircuit infers the plane destinations
-from matching `<copperpour />` elements. An explicit map is useful when a net
-has pours on multiple layers:
+from matching `<copperpour />` elements on the enclosing board. An explicit map
+is useful when a net has pours on multiple layers:
 
 ```tsx
 <breakout

From 34799ac6092279d115326854423246e241eb440b Mon Sep 17 00:00:00 2001
From: seveibar <seveibar@gmail.com>
Date: Fri, 31 Jul 2026 12:42:52 -0700
Subject: [PATCH 3/3] Stack breakout preview vertically

---
 docs/elements/breakout.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/elements/breakout.mdx b/docs/elements/breakout.mdx
index 196393c4..db3d62d2 100644
--- a/docs/elements/breakout.mdx
+++ b/docs/elements/breakout.mdx
@@ -20,7 +20,7 @@ This 100-pin BGA keeps two 8-bit buses on contiguous outer columns and assigns
 each bus an explicit fanout direction. Eight center-region balls connect to
 GND and VCC pours on separate inner layers.
 
-<CircuitPreview defaultView="pcb" code={`
+<CircuitPreview verticalStack defaultView="pcb" code={`
 const buses = [
   {
     name: "DATA",