Lending · Agent pack
Consumer lending disclosures
Cadre pack · Plainspeak
Prepares a plain-language draft, checks it against the configured checklist, and leaves final approval accountable.
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
Drafts the adverse-action notice or the cost-of-credit approval disclosures from a committed credit decision.
- Case arrives with
- Decision · Application · Decision · Product · Decision · Decision · Decision · Score band
- Allowed outcomes
- Adverse Action · Approval
- Where it fits
- Application to Decision
Operating logic
- 01Drafts a consumer-facing adverse-action notice or cost-of-credit disclosure from the supplied decision and disclosure profile for accountable review.
- 02Terms come from the supplied record — APR, amounts, and candidate reasons are not silently filled in when the decision is missing them.
- 03Checks the draft against a configured ECOA and FCRA checklist, including reason, notice, reporting-agency, applicant-rights, and score fields; that checklist does not establish legal compliance.
- 04A draft with missing fields keeps those gaps visible instead of being marked complete.
Decision logic
- 01Drafts a consumer-facing adverse-action notice or cost-of-credit disclosure from the supplied decision and disclosure profile for accountable review.
- 02Terms come from the supplied record — APR, amounts, and candidate reasons are not silently filled in when the decision is missing them.
- 03Checks the draft against a configured ECOA and FCRA checklist, including reason, notice, reporting-agency, applicant-rights, and score fields; that checklist does not establish legal compliance.
- 04A draft with missing fields keeps those gaps visible instead of being marked complete.
- Must not
- Use protected-basis fields in the decision path.
- Human owner
- Disclosure exceptions and unresolved gaps
- Evidence retained
- Structured outcome, observed path, and the source evidence used.
Case and record
One case, from supplied evidence to recorded decision
Supplied case
- Decision · Application
- L2
- Decision · Product
- auto
- Decision · Decision
- decline
- Decision · Score band
- below subprime
- Decision · Dti pct
- 35
- Decision · Ltv pct
- 126
- Decision · Policy basis
- score 561 below the auto minimum of 600, LTV 126% above the 125% maximum
- Decision · Factors
- credit score below the program minimum, a recent charge-off and a collection, very high revolving utilization (88%)
- Decision · Confidence
- 0.95
- Reasons
- credit score below the program minimum, a recent charge-off and a collection, very high revolving utilization (88%)
View the case data
Case key L2-adverse
{
"decision": {
"applicationId": "L2",
"product": "auto",
"decision": "decline",
"scoreBand": "below-subprime",
"dtiPct": 35,
"ltvPct": 126,
"policyBasis": [
"score 561 below the auto minimum of 600",
"LTV 126% above the 125% maximum"
],
"factors": [
"credit score below the program minimum",
"a recent charge-off and a collection",
"very high revolving utilization (88%)"
],
"confidence": 0.95
},
"reasons": [
"credit score below the program minimum",
"a recent charge-off and a collection",
"very high revolving utilization (88%)"
]
}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.
subprime auto decline
Reg B adverse-action notice with the reasons, ECOA, and FCRA; cites 1002.9
Case key
L2-adverseprime auto approve
TILA / Reg Z cost-of-credit disclosures with the APR; cites 1026
Case key
L1-approvalcard score below minimum
adverse-action notice
Case key
L8-card-adverse
Operating fit
Workflow placement and validation
Operating pattern
Draft, check, revise
Separate drafting from checking and stop when the work meets clear requirements—or when the agreed review limit is reached.
Decision sequence and workflow placement
- 01Draft from evidence
- 02Check named requirements
- 03Return specific gaps
- 04Revise
- 05Complete or refer
Wider workflows
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
- Decision · Application
- Decision · Product
- Decision · Decision
- Decision · Score band
- Decision · Dti pct
- Decision · Ltv pct
- Decision · Policy basis
- Decision · Factors
- Decision · Confidence
- Reasons
- Retrieve regretrieve_reg
- Get disclosure profileget_disclosure_profile
- Record disclosurecommitrecord_disclosure
- Adverse Action
- Approval
Related packs