> ## 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.
# Verify Statements
> Approve material pricing rules through plain-language review before the Book can publish.
Verify Statements to authorize material pricing rules as plain sentences. Verification is the step where owner authority is recorded — no suggested or extracted value becomes an authorized rule without it.
## Before you start
* A workspace with an active Test environment
* A draft exists and has been reviewed (compile issues resolved, coverage checked)
* Calibration cases have been resolved (the Book is no longer in **Needs calibration** state)
You can verify Statements at any time — even before all calibration cases are resolved. But the Book cannot publish until every material rule is verified.
## What the Verify page shows
The page has two areas:
1. **Totals** — Three counts: total rules, verified rules, and remaining rules to verify.
2. **Statement groups** — Rules grouped by type, each shown as a plain-language sentence with its provenance chip and verification status.
## Totals
| Count | Meaning |
| --------- | ---------------------------------------------------------- |
| Rules | The total number of material Statements in the draft. |
| Verified | How many of those Statements you have explicitly verified. |
| Remaining | How many are still waiting for your verification. |
The Book cannot publish while any material rule remains unverified.
## Statement groups
Statements are grouped by type. Each group shows how many rules are verified and how many are waiting. Within each group, every rule appears as:
* A **plain-language sentence** — the rule in words you can understand, not JSON or a formula
* A **provenance chip** — how the rule came to be
* A **verification status chip** — whether the rule is verified, needs verification, or is unsupported
### Provenance chips on Verify
The same four provenance classes appear here:
| Chip | Origin |
| ----------------- | -------------------------------------------- |
| From your file | Read from a source you provided |
| You told us | Stated directly by you |
| From your numbers | Calculated from your figures and assumptions |
| Suggested | A Kordless suggestion |
Provenance is origin, not authority. A rule labeled **From your file** or **You told us** is not automatically verified. A rule labeled **Suggested** is explicitly not authorized until you verify it.
### Verification status
| Status | Chip | Meaning |
| ------------------ | ---------------------------- | -------------------------------------------------------------------------------------------------------- |
| Verified | Verified (success) | The owner has explicitly verified this rule. |
| Needs verification | Needs verification (warning) | The rule is rendered and functional but has not been verified. |
| Unsupported | Unsupported (danger) | The rule's structure could not be rendered. It must be corrected before it can be verified or published. |
### Source and provenance detail
Each rule can be expanded to show its source and provenance detail — the specific claims, inputs, or suggestions that produced it. If a rule has no source recorded, the detail reads: "No source recorded. This rule must be corrected before publication."
## How to verify
### Individual verification
Each group of pending rules has a **Verify** button. When a group can be verified as a whole (all its rules are rendered and functional), the button reads **Verify N rules** and verifies all pending rules in that group at once.
### Grouped verification
Verification is permitted in groups when the rules in a group mean the same kind of thing. This lets you verify related rules together — for example, all base prices for a service — rather than one at a time.
### When grouped verification is blocked
If a group contains an unsupported or rejected rule, the page reads: "Correct the unsupported or rejected rule before verifying this group." You must go to [Review draft](/product/book/review-draft) and correct the rule before the group can be verified.
## Why blind approval is not offered
Kordless does not offer a "verify all" button that approves every rule at once. Each rule must be reviewed and verified explicitly, either individually or within a homogeneous group. This is deliberate:
* A suggested value that looks correct may still be wrong.
* A rule extracted from your file may have been misread.
* A calculated value may rest on an assumption you did not intend.
Verification is the point where the owner takes responsibility for the rule. Blind approval would remove that responsibility.
## Role requirements
Verification requires authorization to record verification decisions. If you do not have the required role, the page shows a permission message. Ask a workspace administrator to complete this step or grant you the necessary role.
## After verification
When every material rule is verified, the Book state advances to **Verified draft** or **Ready to publish**. The next action on the Book overview becomes **Preview and publish**.
## If it does not work
If the page shows "Nothing to verify yet," review the extracted draft first. Material rules appear here as sentences once Kordless has a draft.
If a group shows "Correct the unsupported or rejected rule before verifying this group," go to Review draft and correct the problematic rule. The group can be verified once all its rules are rendered and functional.
If you see a permission message, you do not have the role required to verify rules. Ask a workspace administrator to complete this step or grant you the necessary role.
## Next
Review consequences and publish an immutable Book version.
How source, evidence, and suggestion are tracked and verified.