Before you start
- A workspace with an active Test environment
- At least one source has been submitted and extraction has completed
What the Review page shows
The Review page has two areas:- Coverage and readiness — A status chip showing whether the draft can compile and quote, unresolved required questions, compile issues, readiness blockers, and per-service coverage.
- Statements — Every rule in the draft as a plain-language sentence, each with its provenance chip and verification status.
Coverage and readiness
The readiness status chip shows one of three states:Compile issues
If the draft cannot compile, each issue appears with a Can’t compile chip and an explanation. These are structural problems — for example, a rule references a factor that does not exist. You must correct the rule before the draft can produce quotes.Readiness blockers
Blockers appear with a Not ready chip. These are conditions that prevent publication but do not stop compilation — for example, a required clarification is still open or a service has no coverage.Per-service coverage
Each service shows whether it has full or partial coverage:- Full coverage — every enumerable case for this service has a rule.
- Partial coverage — some cases for this service do not have a rule. The count shows how many are covered out of the total.
Statements
Each rule appears as a plain-language sentence — not JSON, not a formula, not a code snippet. The task here is correcting meaning, not editing data structures.Provenance chips
Every rule carries a provenance chip that tells you how it came to be:
Provenance is the origin story. It is separate from authority: a rule labeled From your file or You told us is not yet verified. Provenance stays neutral so a suggestion is never dressed as an authorized price.
Verification status
Each rule shows one of three statuses:
Verification happens on the Verify Statements page, not here. On Review, you correct meaning and resolve structure problems.
Source and provenance detail
Each rule can be expanded to show its source and provenance detail — the specific claims or inputs that produced it. This lets you trace a rule back to the source it came from. If a rule has no source recorded, the detail reads: “No source recorded. This rule must be corrected before publication.”What you do on this page
- Correct meaning — If a sentence does not match what you intended, correct it. The correction may be adding a missing factor, fixing a price, or removing a rule that does not apply.
- Resolve unsupported shapes — Rules marked Unsupported shape must be corrected before the draft can compile. Follow the correction path for each rule.
- Review source conflicts — When two sources disagree, Kordless surfaces the conflict for you to resolve.
- Check coverage — Identify services with partial coverage and decide whether to add rules or leave those cases unsupported.
If it does not work
Next
Answer questions
Resolve clarification questions grouped by consequence.
Calibrate scenarios
Test the Book against representative and boundary cases.