# Chapter <N>: <Full Chapter Title>

<!--
Budget (Step 7):            reference        study
        BOOK_TYPE=text      800–1,200        1,000–1,800
        BOOK_TYPE=technical 1,200–1,800      2,000–3,000

Targets, not caps. Density beats length — never pad to hit a number.
Delete every section that does not apply; an empty heading costs tokens
on every load and tells the agent nothing.
-->

## Core Idea

<One or two sentences: the single most important thing this chapter teaches. If you cannot
state it plainly, re-read the chapter — you have copied it, not extracted it. If the chapter
is genuinely thin, say so here rather than padding the sections below.>

## Frameworks Introduced

- **<Framework Name — the author's exact naming>**: <exact formulation>
  - When to use: <the specific situation that triggers it>
  - How: <steps or criteria — explicit for study depth, a line for reference depth>
  - Why it works / fails: <study depth only, for the top 1–2 frameworks>

## Key Concepts

<5–10 terms, no more. Past ten you are transcribing a glossary rather than chunking.>

- **<Term>**: <precise one-sentence definition>

## Mental Models

<2–4 thinking tools. Write them as instruments, not descriptions:
 "Use X when Y" / "Think of X as Y" / "Prefer X over Y because Z".>

## Anti-patterns

- **<What to avoid>**: <why it fails, in the author's terms>

## Code Examples

<!-- Technical sources only. Delete for prose. Copy the single most instructive snippet;
     preserve indentation exactly. One good example beats three partial ones. -->

```<language>
<key code example>
```

- **What it demonstrates**: <one line>

## Reference Tables

<!-- Technical sources only. Reproduce a comparison matrix, parameter table, or decision
     table as Markdown. Tables do not compress — this is what the wider technical budget
     is for. -->

## Worked Example

<!-- DEPTH=study only. Reconstruct ONE concrete thing the author works through: a sample
     document, a dialogue, a filled-in template, a before/after, a decision walked end to
     end. This is the single biggest reason a study chapter is worth its budget, and the
     main thing a learner returns for.

     Reconstruct compactly in your own words. Do not reproduce the author's example
     verbatim at length — see references/rights_and_provenance.md. -->

## Key Takeaways

<3–7 items. Each one actionable — something a practitioner does differently tomorrow,
 not something they now know.>

1. <Actionable insight>
2. <Actionable insight>
3. <Actionable insight>

## Connects To

<!-- The links are the navigation. A chapter with no Connects To is an island, and the
     agent will only ever reach it through the topic index. -->

- **Ch <N>**: <why this chapter relates to that one>
- **<External concept or standard>**: <what it connects with outside this source>
