# Campaign 1 Handoff v1

The command result contains exactly one bounded section. The public meeting page
does not render this transport block:

```text
## Campaign 1 Handoff
Schema version: sellable.kickoff.campaign1.v1
- **Client:** {public client name}
- **Page revision:** {exact visible revision}
- **Readiness:** draft | confirmed | handoff_ready | blocked
...the remaining fixed v1 labels emitted by admin_onboarding_call...
```

The canonical renderer and parser in `admin_onboarding_call` own the complete
fixed label list. Do not duplicate or reinterpret it in skill prose. The parser
fails closed on duplicate/missing headings, missing or extra fields,
unsupported schema, stale revision, identity mismatch, or readiness other than
`handoff_ready`. It never fills a missing value from surrounding agenda prose.

The returned Markdown is the transport to the later campaign workflow. Do not
scrape the public Notion URL, create a hidden strategy receipt, or treat the
three dream clients as provider/source seeds. Sufficient intake can skip repeated factual
discovery only; it cannot skip downstream brief, sourcing, import,
message/filter, sample, or launch approvals.

## Proposed onboard-client handoff

`Prepare the kickoff meeting document for {client} for the verified upcoming kickoff.`

That is the complete proposed handoff for Plan 102-04 to apply to
`onboard-client`. It is one invocation only and intentionally contains no
internal IDs, agenda object, or handoff grammar; the adaptive operator resolves
the exact deterministic engagement and resource binding from live state.