# Launch brief format

Use when a team needs one launch page for scope, timing, owners, rollout, and risks.

## Great instance

- Makes the launch decision and date visible immediately.
- Shows rollout flow as a Mermaid diagram.
- Uses an owner table with one accountable person per row.
- Separates launch blockers from post-launch watch items.

## Cut

- Marketing copy, internal history, and generic checklists.
- Owners named as teams only.
- Diagrams that duplicate the owner table.

## Skeleton

````markdown
# Launch brief: <thing>

## What ships
<scope, audience, and non-goals>

## When
<date, freeze, rollout windows, rollback point>

## Who owns what
| Area | Owner | Backup | Decision |
| --- | --- | --- | --- |

## Rollout
```mermaid
flowchart LR
  Prep --> Pilot --> Ramp --> GA
```

## Risks
- <risk, signal, mitigation>
````

## Section prompts

- State the launch/no-launch condition.
- Give every row one named owner.
- Put timing in absolute dates when known.
- Keep rollout nodes few and operational.

## Renderer moves

Catalog: ../building-artifacts.md#what-each-file-type-becomes - md doc reader sections; mermaid rollout; table cell anchors.