Reason codes a validator can read.
A Day-Zero scorecard arrives with a written reason for every weight. What that gives an underwriter and a validator.
A weight with a reason
A Day-Zero scorecard is closed-form: every column in use has a weight, and every weight arrives with a written reason and a confidence. The columns the card leaves out are listed too, each with the reason it was left out. Nothing about the card has to be inferred from its behaviour.
Points an underwriter can follow
One application becomes a score in points. The card states its own scale on the screen — a base score at stated odds, and how many points double them — and its grades are 20-point bands around the book's own odds. An underwriter sees which columns added points and which took them away, and the reason written beside each weight.
The card proposes, the policy decides
The lender's policy sits on top of the card: the columns it will not lend on, a floor under the probability of default, the grades in use. Every control is a lever a validator will ask about, and each one rescores the book on the spot, so the cost of a policy choice is visible before it is made.
A pack the validator can challenge
The validation screen sets the card against the standards a validator works to: what each rule asks, what the card gives, and what it does not. Every number on those screens comes with a source file and a hash, and the browser scorer is checked row by row against the research engine.