Predict then reveal: removing anchoring bias
Why a reviewer records an estimate before the system shows its own number.
This page introduces the idea and shows where it appears in a verification. The full reference lives in your workspace documentation; this is the canonical overview.
In short
Why a reviewer records an estimate before the system shows its own number.
How it works in Merlise
Inside Merlise this runs as part of the pipeline that turns a document into a ledger. Each claim carries its own state, and the result is always traceable to the records that produced it rather than to a summary you cannot open.
The reasoning step is kept separate from the probability the system reports, so a persuasive explanation never moves a number on its own. Every adjustment is written to the update log in order.
Worked example
Key points
- The reading traces to a primary record, not a summary.
- Evidence is weighted by provenance before it counts.
- Every step is written to an audit trail you can reopen.
Was this page useful? Yes · No