REV-026 / Northstar Community Bank
Consumer underwriting Q1–Q2 2026
Unsecured consumer installment · Nimbus v4.1 → v4.2 · Jan 1 – Jun 30, 2026
- Draft
- Data qualification
- Testing
- Challenge
- Management response
- Retest
- Complete
Review scope
Can a qualified reviewer reconstruct the decision, challenge its evidence and preserve the response and retest?
FL-024’s screen persists after the analysis-specification change. AA-009’s corrected mapper replay is supported; the original inconsistent notice remains inspectable.
Findings and next actions
| Finding / observation | Materiality | Owner | Status | Next action |
|---|---|---|---|---|
| AA-009 · Reason provenance inconsistent in original noticeOriginal notice cites credit history, which is absent from the supplied principal-factor record. Corrected mapping replay is supported by the same record; production deployment has not been assessed. | Moderate | Maya Chen | Closed | Closure applies to the synthetic mapper replay only. Production notice remediation would require separate evidence. |
| FL-024 · Covered-population outcome differenceThe configured descriptive screen is triggered within qualified bureau strata. It is not a finding about applicants without supplied proxies or a legal conclusion. | Moderate | Maya Chen | Retest required | Remediation did not resolve the descriptive screen. Request a new action plan; retain the original result. |
Unified review chronology
Generated synthetic extract; no bank ingestion.
Inspect previous and new state
{
"before": null,
"after": {
"hash": "fnv1a32-1157db84",
"rows": 12481
}
}Synthetic reviewer choice: descriptive AIR < 0.80 prompts investigation, not a legal verdict. At least 30 independent applicant records per cohort per stratum is an illustrative stability gate, not a power analysis. Use the covered population only; no inference to missing proxy records.
Inspect previous and new state
{
"before": null,
"after": {
"id": "CFG-01",
"methodVersion": "Stratified Screen v2.0",
"channel": "Partner Marketplace",
"version": "v4.2",
"from": "2026-01-01",
"to": "2026-06-30",
"threshold": 0.8,
"minimum": 30,
"reference": "Cohort B",
"stratify": true,
"population": "covered-only",
"maxMissing": 0.2,
"rationale": "Synthetic reviewer choice: descriptive AIR < 0.80 prompts investigation, not a legal verdict. At least 30 independent applicant records per cohort per stratum is an illustrative stability gate, not a power analysis. Use the covered population only; no inference to missing proxy records.",
"approvedBy": "Ellis Morgan",
"createdAt": "2026-09-10T14:00:00Z"
}
}Partner covered-population screen
Inspect previous and new state
{
"before": null,
"after": {
"configId": "CFG-01",
"result": "Triggered configured screening rule"
}
}Aggregate versus segmented sensitivity
Inspect previous and new state
{
"before": null,
"after": {
"configId": "CFG-02",
"result": "No screen trigger"
}
}Branch null-result check
Inspect previous and new state
{
"before": null,
"after": {
"configId": "CFG-03",
"result": "No screen trigger"
}
}Small-population qualification
Inspect previous and new state
{
"before": null,
"after": {
"configId": "CFG-04",
"result": "Interpretation withheld"
}
}Full-population coverage qualification
Inspect previous and new state
{
"before": null,
"after": {
"configId": "CFG-05",
"result": "Interpretation withheld"
}
}Pre-change Nimbus v4.1 sensitivity
Inspect previous and new state
{
"before": null,
"after": {
"configId": "CFG-07",
"result": "No screen trigger"
}
}Covered population screen requires explanation; missingness bounds interpretation.
Inspect previous and new state
{
"before": null,
"after": {
"status": "Open"
}
}Original reason contradicts the supplied principal-factor record.
Inspect previous and new state
{
"before": null,
"after": {
"status": "Open",
"evidence": [
"EV-002",
"EV-003"
]
}
}Request supporting evidence
Inspect previous and new state
{
"before": null,
"after": {
"originId": "FL-024",
"question": "Provide the channel specification and document the change; second-line analysis is retained separately."
}
}Model-owner explanation requested.
Inspect previous and new state
{
"before": {
"status": "Open"
},
"after": {
"status": "Under challenge",
"challengeId": "CH-018"
}
}Request supporting evidence
Inspect previous and new state
{
"before": null,
"after": {
"originId": "AA-009",
"question": "Reconcile notice reason M-17 with the supplied principal factors."
}
}We disagree that a difference alone warrants a model change. The original specification omitted channel sensitivity. We have supplied specification B; no decision-policy or model outputs changed.
Inspect previous and new state
{
"before": {
"status": "Awaiting response"
},
"after": {
"status": "Response received",
"responseId": "RESP-018-1",
"artifactIds": [
"EV-008",
"EV-010"
]
}
}Responses and changed specifications received; preserve original findings.
Inspect previous and new state
{
"before": {
"stage": "Management response"
},
"after": {
"stage": "Retest"
}
}FL-024 sensitivity retest; no changed decision outcomes
Inspect previous and new state
{
"before": null,
"after": {
"configId": "CFG-06",
"result": "Triggered configured screening rule"
}
}Screen persists. Updated analysis specification did not establish remediation.
Inspect previous and new state
{
"before": {
"status": "Under challenge"
},
"after": {
"status": "Retest required",
"retestId": "RT-024"
}
}The scope explanation is supported, but changing the analysis does not remediate the persisting outcome screen. Request policy rationale and a new action plan.
Inspect previous and new state
{
"before": {
"status": "Response received"
},
"after": {
"status": "Additional evidence required",
"responseId": "RESP-018-1"
}
}M-17 incorrectly mapped utilization to credit-history wording. MAP-3.5-TEST maps utilization to the corresponding stated factor. The original notice remains preserved. Replay only, not a production release.
Inspect previous and new state
{
"before": {
"status": "Awaiting response"
},
"after": {
"status": "Response received",
"responseId": "RESP-019-1",
"artifactIds": [
"EV-003",
"EV-014"
]
}
}Corrected mapper replay supplied; independent review still required.
Inspect previous and new state
{
"before": {
"status": "Open"
},
"after": {
"status": "Retest required",
"retestId": "RT-009"
}
}Compared original notice, principal factors and corrected replay. Both replay reasons are supported. Closure scope is the synthetic mapping defect only.
Inspect previous and new state
{
"before": {
"status": "Response received"
},
"after": {
"status": "Supported",
"responseId": "RESP-019-1"
}
}EV-014 replay is supported. Closure limited to sandbox mapping; no production remediation claim.
Inspect previous and new state
{
"before": {
"status": "Retest required"
},
"after": {
"status": "Closed",
"retestId": "RT-009"
}
}