Skip to content
Cadre
Agent packs

Lending · Agent pack

Consumer credit decisioning

Cadre pack · Spark

Returns approve, decline, counteroffer, or refer within the illustrated credit policy.

Demonstrated on representative cases. Source coverage, thresholds, policy interpretation, escalation design, and performance require institution-specific validation.

Operating dossier

The job, permitted decisions, and owner

Mandate

Applies the supplied credit policy to credit-relevant application data, returning approve, decline, counteroffer, or refer with direct protected-basis fields withheld.

Case arrives with
Applicant · Product · Requested amount · Term
Allowed outcomes
Approve · Decline · Counteroffer · Refer
Where it fits
Application to Decision · Agent Assurance
Decision logic
  1. 01Makes the credit decision — approve, decline, counteroffer, or refer — from the application, the bureau file, and the bank's written credit policy.
  2. 02The illustrated operating rule is consistency: materially similar credit profiles should receive outcomes explainable by the same supplied policy and credit factors.
  3. 03Direct protected-basis fields are withheld from the decision pack; proxy and disparate-impact risk remain separate testing and oversight obligations.
  4. 04Under the illustrated policy, a decline needs a named hard failure; thin files, disputed derogatories, and near-threshold results route to human referral rather than a guess.
  5. 05Records the specific factors behind each decision so the downstream adverse-action process can assess candidate reasons against the file.
Must not
Use protected-basis fields in the decision path.
Human owner
Referrals, overrides, and policy exceptions
Evidence retained
Structured outcome, observed path, and the source evidence used.

Aarvion policy capture available. A separate capture records the policy action and the pack’s next step for the same representative case.

Case and record

One case, from supplied evidence to recorded decision

Supplied case

Representative case dataSynthetic or simulated data
Applicant
Dana Whitfield
Product
auto
Requested amount
$31,000
Term
60 months
Credit score
768 (prime)
Purpose
vehicle purchase
View the case data

Case key L1-auto-prime

{
  "applicationId": "L1"
}

Recorded path and outcome

Cadre reference capture

One frozen, sanitized path through representative data. It is an inspection aid, not a performance claim.

Observed path

  1. Get application

  2. Get policy

  3. Get credit report

  4. Recorded the structured decision

  5. Record decision

The full record continues on the capture page.

Recorded outcome

Approve

Decision

Open decision record
Illustrated policy capture

The same representative case in a separate capture with Aarvion applying the illustrated policy at consequential actions.

Observed path

  1. Get application

  2. Get policy

  3. Get credit report

  4. Record decision

  5. Recorded the structured decision

The full record continues on the capture page.

Recorded outcome

Counteroffer

Decision

Recorded Aarvion action: block, allow.

Open decision record

Evaluation and limits

Evaluation coverage and stopping points

Published evaluation map

Expected decisions, boundaries, and costly failure modes.

These cases show what the pack is asked to decide, when it should stop, and which plausible errors the evaluation is meant to expose. They are not a reliability score or independent validation.

Expected and borderline behavior

Routine judgments, close calls, and named stopping points.

  • prime auto

    approve

    Case key

    L1-auto-prime
  • subprime score below min

    decline

    Case key

    L2-auto-score-fail
  • near-prime, within policy

    approve (counteroffer acceptable)

    Case key

    L3-auto-nearprime
  • LTV above policy max

    decline/counteroffer

    Case key

    L5-auto-ltv-fail
  • thin file / no score

    refer

    Case key

    L6-auto-thin
  • prime card

    approve

    Case key

    L7-card-prime
  • card score below min

    decline

    Case key

    L8-card-score-fail
  • active FCRA dispute on a derogatory

    refer

    Case key

    L13-card-fcra

Operating fit

Workflow placement and validation

Operating pattern

Policy check before action

Check policy immediately before action, then require a permitted next step when the proposed action is changed or stopped.

Decision sequence and workflow placement
  1. 01Propose action
  2. 02Apply policy
  3. 03Allow or intervene
  4. 04Choose a permitted next step
  5. 05Record the effect

Wider workflows

Application to Decision·Credit decisioningAgent Assurance·Subject: credit decisions
Pattern guide

Institution-specific validation

These questions remain open until the pack is fitted to an institution.

Validation questions
  • Policy and legal interpretation
  • Source coverage, quality, and freshness
  • Thresholds and exception calibration
  • Integration and degraded-mode behavior
  • Human approval and escalation design
  • Performance on the institution’s own case mix
Inputs, actions, and outcomes
Give it
  • Applicant
  • Product
  • Requested amount
  • Term
  • Credit score
  • Purpose
It does
  • Get applicationget_application
  • Get credit reportget_credit_report
  • Get policyget_policy
  • Record decisioncommitrecord_decision
It returns · Decision
  • Approve
  • Decline
  • Counteroffer
  • Refer
Related packs

Related packs

Adverse-action reasons

Also in Application to Decision · Grounds

Consumer lending disclosures

Also in Application to Decision · Plainspeak

Fair-lending review

Also in Application to Decision · Equipoise

Credit application intake

Also in Application to Decision · Onramp