# Capability: Source readiness review

## Intent phrases

- source readiness
- review brief before create
- is this package ready
- intake case study assets
- check gaps before building
- review source package
- ready to build from document

## Requires capabilities

`pages` or `articles`

## Purpose

Decide whether an external package (document, Drive folder, Figma, production ref, or mix) is **good enough to build CMS structure from** — before any `create` / bulk `save`.

**cms-edit does not rewrite source copy.** Its job is a **faithful representation**: place and structure existing words and assets into the site’s components. Flag quality issues; do not “improve” prose, invent headlines, or invent pair layouts.

## Prerequisites

- Sources available (paste, Drive MCP, Figma link, zip, production URL, etc.)
- Read site `cms-edit://customer/articles` and/or `pages`, plus `components-index` / `routing` as relevant

## Source hierarchy (when sources disagree)

Prefer, in order, unless the user overrides:

1. **Sequence & layout** — Figma / approved comps
2. **Art files** — Drive / export package
3. **Words** — approved copy doc (as written)
4. **CMS patterns** — production page / site playbook (how to map, not what to invent)

If title, order, or hero asset **conflict** and the user has not decided → **NO-GO** until they choose.

## Steps

1. **Inventory sources** — list every doc, asset, and design ref; note missing items.
2. **Build inventory table** (required):

   | # | Role | Source file / ref | Status (ready / resize / missing) | Intended CMS mapping |
   |---|------|-------------------|-----------------------------------|----------------------|
   | 1 | … | … | … | … |

3. **Build beat sheet** — ordered narrative + visual beats mapped to **registered** component/collection types only (from `components-index` / site playbook). Prefer **source order** over CMS convenience.
4. **Score verdict** using the threshold below.
5. **Post one-screen soft-proof** — numbered final `content` (or page stack) order + gap list + verdict.
6. **Ask for a light human confirm** — accept **yes** / **go** / **proceed** (or equivalent). Do not build on silence if the package is non-trivial.
7. On **GO** or **GO-WITH-GAPS** + yes → hand off to `task-create-from-document` / `task-create-article` / `task-create-page` with the soft-proof as the plan.
8. On **NO-GO** → stop; list what is blocking (do not invent structure to unblock).

## Gap threshold

### NO-GO (any one is enough)

- **Sequence unknown** — no Figma/comps/ordered list; building would invent order
- **Narrative incomplete** — missing major beats the site playbook expects for that content type
- **Would invent structure** — pairing images the design does not pair; inventing section titles; inventing side-by-side layouts
- **Conflicting sources** with no owner decision (H1/title, order, hero asset)

### GO-WITH-GAPS

- Sequence **clear** and narrative **usable as written**
- Missing art slots **≤ 3** **or** **≤ ~25%** of planned visual beats — each **named** with a placeholder strategy
- Optional/spare assets missing is fine
- Meta description can be drafted **from existing copy only** (no invented claims); still include in soft-proof for human yes

### GO

- Same as GO-WITH-GAPS with art complete for the soft-proof (or explicit reuse of existing CMS assets identified by id/filename)

## Faithful structure rules

1. **Do not rewrite copy** — structure and place only; flag issues for the human.
2. **Design sequence beats CMS convenience** — do not invent pair/side-by-side collections unless the source is a true pair.
3. **Placeholders beat reordering** — keep the slot; label the gap (do not drop missing beats and renumber silently).
4. **Merge continuous prose** — do not split body-only blocks without a layout reason (art, quote, or design break between).
5. **Hero / template owns page H1** when the site template provides it — body headings only when the source has section titles.
6. **Lab / draft flags** — follow site playbook (`lab/…`, `hidden`, `indexed`) for experiments.

## Soft-proof format (minimum)

```text
Verdict: GO | GO-WITH-GAPS | NO-GO
Gaps: …
1. … (component/collection type) — source …
2. …
Copy: unchanged from source (list any human decisions only)
```

## Confirmation gates

1. Verdict + soft-proof posted
2. Human **yes** (or equivalent) before create when package is non-trivial
3. NO-GO never proceeds to create without new sources or explicit human override of the blocking item

## Out of scope

- Rewriting or “polishing” source copy
- Brand voice passes
- Publish
- Inventing assets or layout not in the package

## Related resources

- `cms-edit://customer/articles` / `pages` (site composition)
- `cms-edit://customer/components-index`
- `task-create-from-document`
- `task-create-article`
- `task-create-page`
- `task-media-reuse-and-upload`
- `task-preview-verify`