> ## 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.

# Preview and publish

> Review exactly what changes, which scenarios move, and what happens to existing offers before publishing an immutable Book version.

See exactly what changes, which situations move, and what happens to existing offers. Publishing creates an immutable Book version that every permitted surface uses to quote.

## Before you start

* All material Statements have been [verified](/product/book/verify)
* No required clarifications remain open
* Calibration cases have been resolved
* The draft compiles without blocking issues

The page shows **Ready to publish** when these conditions are met, or **Not ready** with the specific blockers listed.

## What the Preview and publish page shows

The page has three sections:

1. **Version** — the next version number, readiness status, existing-offer treatment, and the publish button.
2. **Changed rules** — every material Statement that changes, with before and after sentences.
3. **Scenario replay** — representative and historical cases replayed against the candidate version, showing only changed outcomes.

## Version

The version section shows:

* The next version number (for example, **Version 1** for a first publication, or **Version 2** when replacing a Live version)
* A **Ready to publish** or **Not ready** chip
* Whether this is the first published version or replaces a previous Live version for new quotes
* How existing offers are treated

### Existing-offer treatment

When you publish a new version, existing offers (Quotes already sent or in progress) remain pinned to the version that produced them. The page tells you how many outstanding offers remain pinned to the current version. New quotes use the newly published version.

### Readiness failures

If the Book is not ready to publish, each blocking issue appears with a **Blocked** chip and an explanation. You must resolve each blocker before the publish button appears.

## Changed rules

Every material Statement that changes appears here. For each change:

* A chip shows the kind: **added**, **removed**, or **changed**
* The stable key identifies the rule
* If the rule existed before, the previous sentence appears with strikethrough
* The new sentence appears below it

The section also lists affected services by name.

If this is the first publication, all rules appear as **added**.

<Note>
  Changed rules show the sentence-level difference. For the full source and provenance of each rule, use [Review draft](/product/book/review-draft).
</Note>

## Scenario replay

Representative cases and recent historical scenarios replay against the candidate version. The section shows:

* The total number of scenarios replayed
* Only changed outcomes — scenarios where the result differs between the current version and the candidate

For each changed scenario:

* The label and source (representative case or recent historical quote)
* The before result and the after result, separated by an arrow

If no outcomes changed, the section reads: "No tested outcome changes. The cases still replayed and passed against the candidate artifact."

## Publishing

When the Book is ready, a **Publish version N** button appears. Publishing:

1. Creates an immutable Book version
2. Makes it the Live version for new quotes
3. Preserves existing offers pinned to their original version
4. Returns a link to the published Book

<Warning>
  Publishing makes this version Live and customer-visible. Existing offers remain pinned to the version that produced them. New quotes will use this version.
</Warning>

After publishing, the page shows "Version N is Live" with a link to open the published Book. The Book overview state changes to **Live**.

## Immutable versions

A published Book version is immutable. It cannot be edited, patched, or selectively modified. To change a Live Book, you propose a change, preview its impact, and publish a new version. See [Update a Live Book](/product/book/update-live-book).

## Role requirements

Publishing requires administrator access. If you do not have the required role, the page shows a permission message. Ask a workspace administrator to complete this step.

## If it does not work

<Accordion>
  <AccordionItem title="Not ready to publish">
    If the page shows "Not ready," each blocking issue is listed with a Blocked chip. Resolve each blocker — typically by verifying remaining rules, answering required questions, or resolving calibration cases — then return to this page.
  </AccordionItem>

  <AccordionItem title="Permission-limited member">
    If you see a permission message, you do not have the role required to publish. Ask a workspace administrator to complete this step.
  </AccordionItem>

  <AccordionItem title="Publish fails">
    If publishing fails, the error message appears below the button. This may happen if a backend validation fails between the preview and the publish action. Refresh the page to get the latest preview, then try again.
  </AccordionItem>
</Accordion>

## Next

<CardGroup cols={2}>
  <Card title="Update a Live Book" icon="refresh-cw" href="/product/book/update-live-book">
    Propose, preview, and authorize a change to a Live Book.
  </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>