Calibrate scenarios

Check representative and historical situations before a rule can reach customers. Calibrate confirms that the Book produces the right answer for cases that matter.

​

Before you start

• A workspace with an active Test environment
• A draft exists and can be evaluated (extraction has completed and the draft compiles)

​

What the Calibrate page shows

The page has three sections:

1. Generated tests — Kordless chooses boundary situations where a small detail may change the answer. You decide the expected outcome.
2. Historical cases — Decide whether a past quote is a rule to preserve or a one-off mistake that should not govern new work.
3. Regression suite — Confirmed cases that replay every time the Book is compiled or published.

​

Generated tests

Kordless generates boundary cases — situations where the details matter and a small change might produce a different result. Each generated case shows:

• A label describing the case
• The inputs — the specific values being tested
• The current result — what the Book currently produces for these inputs
• The statements the result was derived from

You decide the expected outcome for each case using four buttons: If a generated case has missing inputs or references an unsupported rule, you cannot confirm it yet. The page tells you to resolve the missing inputs or unsupported rule first.

​

Historical cases

When you import pricing from a source that includes past quotes, Kordless may import them as historical calibration cases. Each historical case shows:

• The label describing the case
• The inputs
• How it was imported — as a priced result or another outcome

You decide whether each historical case should be:

• Preserved — the result is correct and should govern new work. The case is added to the regression suite.
• Corrected — the result was a one-off or mistake and should not govern new work. You can enter the expected price.

This lets you separate rules you want to keep from exceptions you do not want to repeat.

​

Regression suite

Confirmed cases — both generated and historical — become part of the permanent regression suite. Every case in the suite replays each time the Book is compiled or published. Each regression case shows:

• The label
• The source (generated or historical)
• The offering it applies to
• A status chip: Passing, Needs attention, or Not run

A case marked Needs attention means the current Book draft produces a different result from what you confirmed. This is a signal that something changed and needs your review before publishing.

​

How calibration affects the Book state

The Book overview shows Needs calibration when cases are waiting for a decision. Once you confirm or correct every pending case, the Book state advances to the next stage — typically Needs verification. You can return to Calibrate at any time to review or add cases. New generated cases may appear when sources change or new rules are added.

​

If it does not work

​

Next