Trust and checks
How eode checks a model when it's built, keeps checking it as it changes, and lets you check any single number.
eode checks three times: when a model is built, whenever you ask about the model as a whole, and whenever you ask about one scenario's numbers. Each check leaves a record you can open.
| When | What's checked | Where you see it |
|---|---|---|
| At the build | The structure does what the design says, against the checks drawn from your description; a second, independent review reads the built model against your brief | Credentials: the proof ledger and Independent review |
| Any time | The model's data, its functionality and its results, as three pillars of checks | Validation: the badge on the model home and its drawer |
| On one result | The number adds up, where every input came from, the model passes its own rules, and the answer came from the current version | Verify on a solved scenario |
At the build
The design you signed off lists what the model must do. The build is checked against that list, and every check is kept in the Proof ledger. Then an independent review reads the finished model against your original description and lists anything it thinks is missing. You choose Add it or Leave it out for each.
On a model built on sample data, the independent review runs before you see the design. If it fails the model, or one of its checks fails, eode builds again with the findings applied, up to two more times, and keeps the best round. Anything still failing is listed above the design under What still fails in this design before you accept it, and a section a round changed asks you to confirm it again. Accepted, the model reads Ready, with what still fails rather than plainly ready.
A model built from a description that already carried all its numbers is built from those numbers directly. It records no build checks and no independent review; Validation and Verify still work on it.
As the model changes
Edits, applied proposals and reloaded data make a new version. Validation marks checks from an older version Stale, and the validation drawer opens on "This model has changed since it was last verified." with Verify again. Results solved on an older version are marked too, and what-ifs can be regenerated against the new one.
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 line. Verified values were confirmed by the optimization engine; Estimated ones were worked out another way and can be upgraded with a re-trace. The whole record exports as evidence you can file.