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

# Merchandising

> How the facts a storefront agent sells from are owned, versioned and activated.

**Merchandising** is everything a seller configures to shape how the storefront agent sells: products,
the playbook, library materials and AI Business Rules. Semicola keeps these as separate, owned facts
so that a change in one place never silently rewrites another.

## One fact, one owner

| Fact                               | Lives in          | Not in               |
| ---------------------------------- | ----------------- | -------------------- |
| What a product is and its floor    | Products          | The playbook text    |
| Anchor prices, discount caps, tone | Playbook          | Product descriptions |
| Selling points and their evidence  | Library           | The playbook text    |
| What is acceptable, who reviews    | AI Business Rules | The playbook text    |

If the playbook says "never sell display below $6" but the product's floor is $4, the product floor
is what the planner enforces, and the playbook's line becomes advice. Put each fact where it belongs.

## Versions and activation

The playbook and AI Business Rules are **versioned**. Each save creates a new, numbered, immutable
version; saving through Semi or `save_playbook` / `save_business_rules` activates it immediately.
Exactly one version is active. Older versions stay readable and can be reactivated from their page.

Products and library materials change in place, but every proposal records what it consulted when it
was composed, so a later edit never rewrites an earlier answer.

## What changes when you save

* **The next brief** is answered under the new versions.
* **Answers already sent** keep the versions they were composed with.
* **Revision turns** on an existing RFP use the versions active when the revision runs.
* **Readiness** re-checks immediately: for example, activating the first acceptance policy completes
  that step of the setup checklist.

## Reading the current configuration

Use `get` with `kind` set to `playbook` or `business_rules` to read the active version, or `search`
with the same kinds to list versions. The Playbook and AI Business Rules widgets show the same data
with history.