# How writes work

Changing your catalogue by asking is fast, so the connector makes sure you
always know what is about to happen.

## It never writes on the first call

When you ask for a change, the assistant first gets a **plan**: what would be
changed, product by product. Nothing is written until you say go. The
assistant then applies exactly that plan.

If the plan is not what you meant, say so instead of confirming: the assistant
builds a new one.

## It tells you what will and won't change

- A track that carries its own price or genre is a deliberate override: it is
  left alone and named in the plan, by title and ISRC.
- For credits, the plan shows which targets are active or already delivered,
  which values a full copy would remove, and what each target held before.

## It refuses ambiguous input

Give it `03/04/2026` and it asks for `2026-04-03` (YYYY-MM-DD) instead of
guessing between March and April.

## Bulk changes are capped

A single change applies to a limited number of items. A plan that reaches the
limit says so: split the request, for instance label by label.

## There is no undo (yet)

Start with two or three products, open them in Labelcamp and check the
result. The plan shows what the assistant intends to do; only Labelcamp
shows what actually happened. Once a small batch looks right, scale up.
