---
id: SC###
title: <title>
act: I
status: outlined        # outlined | drafted | revised | in-engine | tested
yarn_file: Assets/Dialogue/Scenes/SC###.yarn
location:
reenterable: no
---

# SC-### — <title>

> One scene, one file, ideally one screen of spec. If this brief does not fit on a page, the
> scene is doing too much — split it. That discipline is what lets one writer hold a sixty-scene
> game in their head.
>
> This is the **brief**, not the dialogue. The words live in the `.yarn` file.

## Purpose

One line: what has changed by the end.

## Cast

Speaking characters, and which voices are prominent. **Cap voice introductions at three.**

## Entry conditions

Flags required. "None" is a good answer.

## Critical outputs

Things every build must be able to obtain. Each needs ≥2 independent routes — and independent
means different trace channels, not two checks in the same conversation.

| Clue id | Routes |
|---|---|
|  |  |

## Optional outputs

Missable by design. One route is fine.

## Shape

`hub-and-spoke` | `short tree` | `divergent`. Default to the first.

## Opening frame

2–4 sentences of establishing prose. Sensory, specific, and including one concrete detail that
does not serve the plot.

## Beats

3–6. Each beat is one exchange or one discovery.

1.

## Checks

Write **both** outcomes as summaries before writing any prose. If the failure summary is "the
player doesn't get the thing", delete the check.

| # | Voice | Colour/Gate | DC band | Success → | Failure type | Failure → |
|---|---|---|---|---|---|---|
|  |  |  |  |  |  |  |

## Branch points

| id | The choice | Reconverges at | Persistent effect |
|---|---|---|---|
|  |  |  |  |

## Exit states

Keep to ≤3. More than three means this is a hub, not a scene.

## Flags

**Sets:**
**Reads:**

## Constraints specific to this scene

Anything a later editor must not "fix". Deliberate exceptions to a general rule go here, with
the reason, so they survive review.