> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kordless.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Update a Live Book

> Propose, preview, and authorize a change to a Live Book without writing directly to Live.

Change a Live Book through a proposed change, impact preview, and owner authorization. Natural-language instructions and observed corrections never write directly to Live — they produce a proposal that the owner reviews and publishes as a new immutable version.

## The change sequence

```text theme={null}
instruction or evidence
  → proposed change
  → validation
  → impact preview
  → owner authorization
  → new Live version
```

Every change to a Live Book follows this sequence. There is no shortcut.

## Before you start

* The Book is Live (a published version exists)
* You have administrator access to the workspace

## How to propose a change

You can start a change from any of the same starting methods used to create the Book:

* **Add a source** — Import a new price list, explain a change, or add a guided-setup model. The new source is ingested and produces proposed rules in an open workspace.
* **Correct a rule in Review draft** — Go to Review draft and correct a sentence, add a missing factor, or remove a rule that no longer applies.
* **Draft a pricing rule from economics** — Use the economics helper in Guided setup to calculate a new price and draft a proposed rule.
* **Answer new questions** — New clarification questions may appear when sources change or coverage gaps emerge.

Each method adds proposed changes to the same open workspace. None of them touches the Live version.

## What happens when a change is proposed

When you start a change, the Book overview state changes from **Live** to **Live · changes pending**. The next action on the Book overview becomes **Review changes**.

The proposed changes exist in a draft workspace alongside the Live version. They are:

* **Unverified** — Every new or modified rule carries its provenance chip and needs verification.
* **Validated** — The draft goes through the same review, answer questions, calibrate, and verify cycle as the first publication.
* **Previewed** — The Preview and publish page shows exactly what changed before you authorize it.

<Warning>
  Natural-language instructions never write directly to Live. Every instruction produces a proposed change that must be reviewed, verified, and published as a new version.
</Warning>

## Validation

Before a proposed change can be published, it goes through the same validation cycle:

1. **Review draft** — Inspect the proposed rules as sentences, correct meaning, and resolve unsupported shapes.
2. **Answer questions** — Resolve any new clarification questions that the change introduces.
3. **Calibrate** — Confirm or correct any new generated or historical calibration cases.
4. **Verify** — Verify every new or modified material rule.

The regression suite from the previous version replays automatically. If a confirmed case now produces a different result, it appears as **Needs attention** on the Calibrate page.

## Impact preview

Once the proposed changes are verified, the [Preview and publish](/product/book/preview-and-publish) page shows:

* **Changed rules** — Every Statement that changes, with before and after sentences, marked as added, removed, or changed.
* **Affected services** — Which services are impacted by the change.
* **Scenario replay** — Representative and historical cases replayed against the candidate version, showing only changed outcomes.
* **Existing-offer treatment** — How many outstanding offers remain pinned to the current Live version. New quotes will use the new version after publishing.

This preview lets you see the exact consequence of the change before it reaches customers.

## Owner authorization

When you are satisfied with the preview, publish a new immutable version. The new version becomes the Live version for all new quotes. Existing offers remain pinned to the version that produced them.

After publishing, the Book overview state returns to **Live** (or **Live · changes pending** if additional proposals are still open).

## What is preserved

Changing a Live Book does not delete or overwrite previous versions. Each published version remains immutable and addressable. Quotes pinned to a previous version can still be replayed against that version's exact inputs, derivation, and conditions.

See [Versions and replay](/product/reference/versions-and-replay) for how Book versions work and why Quotes can be replayed.

## If it does not work

<Accordion>
  <AccordionItem title="Cannot start a change">
    If the Book is paused, you must resume Live use before proposing changes. If you do not have administrator access, ask a workspace administrator to start or approve the change.
  </AccordionItem>

  <AccordionItem title="Regression case fails">
    If a confirmed regression case now produces a different result, it appears as Needs attention on the Calibrate page. Review the case — either the change is correct and the case should be updated, or the change is wrong and should be corrected before publishing.
  </AccordionItem>

  <AccordionItem title="Permission-limited member">
    Members can view the proposed changes but cannot publish a new version. Ask a workspace administrator to complete this step.
  </AccordionItem>
</Accordion>

## Next

<CardGroup cols={2}>
  <Card title="Preview and publish" icon="upload" href="/product/book/preview-and-publish">
    Review consequences and publish an immutable Book version.
  </Card>

  <Card title="Versions and replay" icon="layers" href="/product/reference/versions-and-replay">
    How Book versions work and why Quotes can be replayed.
  </Card>
</CardGroup>