01
Consent and eCBSV clear first.
The identity gate is a precondition. It can control the verdict on verification failure, but it is not a corroboration axis and does not enter the index.
Formal methods
Kenshiki's public method is not a weighted sum of signals. It is a deterministic chain: consent gate, seven graded axis judgments, categorical contradiction guard, named coherence rules, versioned policy, validation artifacts, and a sealed record a lender can inspect.
Method summary
The core design is deliberately narrow: preserve what was asked, what evidence answered, where uncertainty remained, which rule fired, and why the resulting record is reviewable later.
01
The identity gate is a precondition. It can control the verdict on verification failure, but it is not a corroboration axis and does not enter the index.
02
Axis outputs carry band, coverage, support, hypothesis, evidence class, and source attestation instead of returning raw source data.
03
Named rules evaluate whether the file holds together, and the categorical guard blocks approval when any admitted axis is contradictory.
The verdict equation
The formal method is easiest to audit as a routing function. The gate is evaluated first; if it fails, it controls the verdict. If it clears or is not run for lack of consent, the policy layer reads the axis judgments and coherence rules.
Read this as: for application A, a failed gate G overrides the result; any contradictory axis blocks approval; otherwise product policy Π for product p evaluates the set of axis judgments J and product-specific coherence rules R.
The index boundary
The Corroboration Confidence Index summarizes the admitted evidence record so a reviewer can read the file quickly. It is not the approve, refer, or decline rule. The recommendation path uses gates, bands, coherence rules, and versioned policy thresholds.
The number makes the record easier to scan. The named rule chain makes the record defensible.
This separation matters for adverse-action and model-risk review. If a file is referred or stopped, the reason basis should trace to the specific gate, axis, missingness, or coherence rule that actually mattered — not to a generic failure to achieve a score.
Axis judgments
An axis asks whether admitted evidence corroborates a bounded claim — for example, that presence fits the claimed timeline, that income is verified at source, or that identity elements show continuity. Each axis returns a band, coverage, support, and a reason scaffold, never raw source data. The full set of corroboration axes, and the consented identity gate, are described on the approach page.
The source evidence supports the bounded claim strongly enough for the policy layer to count it as positive evidence.
The evidence leans positive but does not carry the same assurance as a corroborated result.
The source could not answer enough of the question. Missingness stays visible rather than being imputed into a midpoint.
The evidence conflicts with a required claim. The policy layer treats material contradiction as a named risk surface.
Validation layer
The 60-case seed corpus is useful as a methodology artifact: it regenerates the operating-point matrix, verifies that contradictory axes no longer survive into approval, and reports calibration and dependence metrics. It is not statistically powered production validation.
The current roadmap keeps the hard floor live while treating calibrated log-likelihood-ratio aggregation as a shadow-mode validation target. Before posterior-style evidence weights can influence recommendations, Kenshiki needs representative outcomes data, approved smoothing and calibration thresholds, a dependence-correction method, and model-risk review.
Regulatory posture
The method is designed around the practical bar that credit decision evidence must be explainable, reproducible, and reviewable. Kenshiki does not claim this alone decides legal classification; it creates the engineering posture a lender, model-risk team, and counsel can inspect.
That posture aligns with the same themes discussed in SR 26-2 and model validation: documented assumptions, versioned thresholds, third-party input review, and a record that can be replayed by people who did not build the system.
For conforming mortgage, the boundary is narrower still: Kenshiki evidence can sit beside GSE-validated decisions as lender-held context. It does not feed Desktop Underwriter or Loan Product Advisor and does not claim to upgrade conforming-loan eligibility. See the mortgage/GSE channel note.
FAQ
What the formal method claims, and what it deliberately does not claim.