Skip to main content
An RSL file states a rating plan the way its filing does: inputs, rate tables, rules, calculations and rounding, each tied to its source. The rslc compiler checks the file and packages it for Relativities to run locally.

What RSL is

RSL describes three things: A rater stands alone, and most work starts there. A guideline uses a rater, and a submission log records each answer and act on one submission. Raters and guidelines explains how the parts fit.

What you do with RSL

  1. Write the rating algorithm as a rater, with a citation for each filed number.
  2. Check it with rslc check, and fix each message.
  3. Test its premiums against independent rating examples.
  4. Package it as a bundle, then rate one policy or a whole book with Relativities.
  5. Add the questions an application asks, and the underwriting rules of a guideline.
Steps 1 to 4 make a working rater. Step 5 is for a program that collects answers from people.

What the compiler guarantees

A rater that passes rslc check gives a value for every request it accepts: each lookup finds a row, and each division has a nonzero divisor. Arithmetic is exact, and a value changes only at a round that the rater writes. Each table, constant, and rounding cites its source. The check describes the implementation, so a reviewer and independent examples still establish that the rater follows the filing. Language guarantees states these properties in full, with a program that breaks each one. Checks and guarantees lists each checked property and what still needs review.

Choose a starting point

To use existing rating programs, start with Rate a book with a program.

Read the docs in your terminal

The reference ships with the compiler, so it matches the installed version and works offline:
rslc explain takes the code of a check message. It prints what the check asks for, a rater that gets the message, and the fix:
rslc examples lists the example raters on the examples page, and rslc examples get dwelling saves one to a folder.