River Logiceode docs

Trust and checks

How eode checks a design before it's built, a model when it's built, a model as it changes, and any single result.

eode checks a model before it's built, when it's built, and whenever you ask about a result. Each check leaves something you can open.

WhenWhat's checkedWhere you see it
Before the buildThe design, read back against what you saidThe Check step on the model's record: Review the design
At the buildThe built model passes its own checks before it solves; the solved result is checked for anything that looks wrong; every figure keeps where it came fromSummary on the record: The model's evidence
On one resultThe number adds up, where every input came from, the model passes its own rules, and the answer came from the current versionVerify on a solved scenario, and the validation record behind it

Before the build

At the Check step, RIA reads the design back to you in the conversation. The record lists each place it didn't take your words as they were, tagged Changed, Assumed, Left out or Asked. You settle each one: Keep it as it is, Change, or Ask. Build appears only when nothing there waits on you. Afterwards, the Check part under Details keeps every row with where it came from and how you answered it, and reads Approved with the date (Read the check in Details).

At the build

The model RIA builds has to pass its own checks before it solves. If it doesn't, the build stops and the record says "The model RIA built did not pass its own checks. Nothing in your workbook caused this.", with Change it with RIA (When the build stops).

A build can also finish Ready, with n open points: limits you stated that the plan doesn't follow, each listed with why (Follow a build).

Once the model solves, the record's Summary holds the evidence:

  • Each figure with where it came from, such as "From the solved plan"; click its name to see (See where a figure came from).
  • Plausibility: what a check of the result flagged as looking wrong, when there is anything. If a line points at something to change, tell RIA in the conversation (Read the plausibility findings).

As the model changes

Every change is a turn in the record's History (Read the history). After a change, the parts it touched read Out of date and the result is labelled Last run until the model is built again. What-ifs solved before the change read Out of date until they run again (Keep results current). On a scenario solved against an older version, Verify's dot turns amber. The validation record marks checks from an older revision Stale, and after a change to the model's structure it offers Verify again (Verify again after a change).

On one number

Verify answers one question: can you trust this scenario's numbers? It traces the result back to its parts, says where each input came from, and ends in a confidence badge. Verified values were confirmed from the solved plan; Estimated ones were worked out another way and can be upgraded with a re-trace. When a validation rule fails, Verify opens the model's Validation record, which checks its Data, Functionality and Results separately. The whole Verify record exports as evidence you can file.

On a KPI tile, Prove this number traces one KPI the same way (Prove a number).

On this page