Layouts, and documents that nest
A route names one document. That document may be a chain, and the chain comes from the directory tree.
Two of this guide’s holes come from the document and two from the section layout, and the page’s declaration does not say which is which.
The error names the chain it looked through, so you can see which layout you meant.
In plain terms
A layout is the page around your page. app/layout.tsx is the document itself; a layout.tsx inside a directory wraps everything under it. Each one leaves named holes, and a route fills the ones it knows about.
A route names one document, and its <slot> holes are the boundaries the route fills. app/layout.tsx is that document by default; defineRoute({ layout: 'dash' }) picks app/layouts/dash.tsx instead, which is how a page with a different shape gets different holes.
A document may be a chain
A layout.tsx inside app/routes/ wraps every route at or under its directory, nested inside the application’s own document. This page is served by one: the site’s document is app/layout.tsx, and everything under /guide is wrapped in app/routes/guide/layout.tsx, which is where the contents column beside you comes from.
The chain is not compiled into one template. Every layer stays separately sealed and separately versioned, and the cuts each one leaves are spliced together when the document streams. So a slow region inside a nested layout streams exactly as one in the outer document does, with its own cache policy and its own budget.
app/layout.tsx <slot name="body">
app/routes/guide/layout.tsx fills body, leaves contents / body / outline
app/routes/guide/layouts.data.ts fills contents, body, outlineThe plan for this page has three slots, and nothing in its declaration says which layer left which hole. weft why /guide/layouts prints it.
The chain is one document
Its reads are the union of what every layer reads, so a nested layout that reads a cookie makes the whole page vary on it. Its identity is the layers in order, so two routes are the same document — swappable by a staged navigation, sharing regions — only when they were built from the same files in the same order.